RE: toString shouldn't change the object's state

Hi all, 1) I have changed the signature of getValue() to declare that it can throw IOExceptions. This prevents the silent eating of those exceptions. 2) I've also added a warning in the Javadocs discouraging the usage of this method as it can lead to OutOfMemoryErrors for large content. 3)

RE: Handlers for search urls

Hi Vincent, Well, it turns out restlets only understand the base of the URLs. The choice of not exposing the query string and the fragment part of the target resource URI was deliberate. The reason is that the query string is often composed of a sequence of parameters (key=value) that can

Re: toString shouldn't change the object's state

Thanks Jerome. 4) Caching is an important requirement that we will address later, probably at a higher level (as a CacheFilter or CacheService?). There is a RFE for it already: http://restlet.tigris.org/issues/show_bug.cgi?id=25 Could you please shed some light on the threading question?

Re: Handlers for search urls

Hi Jerome, The choice of not exposing the query string and the fragment part of the target resource URI was deliberate. The question is: is the question mark part of the query string? The reason is that the query string is often composed of a sequence of parameters (key=value) that can

Re: Handlers for search urls

Just a thought: could it be because ? is a valid regexp meta- character ( No, it's not the issue. -Vincent.