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

[Vincent]

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? Piyush and John
indicated that  Request.getValue must be synchronized should we want to cache
teh stringg, but I don't understand why. I must have missed something in
Restlet's threading model.

Thanks,

-Vincent.

> > 
> > > The problem with cache invalidation for muttable objects in a
> > > multithreaded environment isn't straightforward
> > 
> > Why would two threads access the same request?
> > If it's the case, wouldn't we need to add proper 
> > synchronization to the
> > getStream method anyway? 
> > 
> >     public synchronized InputStream getStream() throws IOException
> >     {
> >             InputStream result = this.inputStream;
> >             this.inputStream = null;
> >             setAvailable(false);
> >             return result;
> >     }