Hi Wouter,
Yes, I should make a new TapirLink release ASAP and I'll surely advertise here. One thing I should also start doing is to associate the Subversion revision number to each release. This way TapirLink installations can be easily checked-out and then updated from the repository based on stable revisions.
By the way, if there's anyone interested in following up changes in TapirLink code, the Subversion repository has been configured to send automatic notifications to the digir-cvs mailing list:
https://lists.sourceforge.net/lists/listinfo/digir-cvs
Best Regards, -- Renato
On 17 Jul 2007 at 16:30, Wouter Addink wrote:
Hi Renato, Thanks for your help. I guess the Tapirlink classes I am working with are a little outdated already, but I am using the latest stable release (0.3.1 from April 07). I am happy that kvp examples are already working correctly in the newer versions, I will also follow the Tapir specs for this then. Will there be a new stable release soon? Then I can update my tapirlink classes. I rather not work with a development version as there will be pending issues in such a version. If QUERY_STRING is part of the CGI spec, I suppose that most webservers will supply it. I don't know of servers who don't, but one can't test them all... I think restricting content-type in POST requests as you suggest would indeed also solve this potential problem.
Wouter