RE: Resources and concurrency

Hi Paul, You correctly described the intended behavior. If you can find the root cause of the bottleneck you observed, please let us know. Best regards, Jerome -Message d'origine- De : Paul Kaiser [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 octobre 2007 22:22 À : Discuss

Re: client side content negotiation

Hello Henry, this kind of properties is not set on the client (or instances of Client class), but on the request sent by the client. the following instruction set the preference for media type application/rdf+xml with the default quality (1 actually):

Re: HEAD not well supported?

Jerome Louvel contact at noelios.com writes: Hi all, Thanks for the quality of the feed-back. I feel like I'm now grasping all aspects of the problem and can propose a solution: 1) Split the Resource class into an abstract Handler class and a Resource subclass Hi Jerome, What is the

RE: EncodeRepresentation.write leaving blocked threads around?

Hi Tim, Thanks again for the suggestion about the queue. That makes total sense. I've just applied the changes to SVN. Best regards, Jerome -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Tim Peierls Envoyé : mercredi 17 octobre 2007 23:41 À :

RE: HEAD not well supported?

Hi Sean, What is the motivation of the Handler class? I have no problem with it, I just want to understand. Is it merely to be explicit about lower level API and higher level, or is there more to it? Exactly, the goal is to clarify the separation between the lower API and higher one. The

Re: HEAD not well supported?

Sean Landis sean.landis at gmail.com writes: Jerome Louvel contact at noelios.com writes: Hi all, Thanks for the quality of the feed-back. I feel like I'm now grasping all aspects of the problem and can propose a solution: 1) Split the Resource class into an abstract Handler class