Thierry Boileau <thboileau <at> gmail.com> writes: > > Hi, > > This "limitation" concerns the following representation classes (and > descendants included in the Restlet API and NRE) : >
Ok, for my clarification: the "limitation" is due to the implementation of the NRE library, not a limitation of the http model? In theory, an implementation could do something like cache the initial input source to make subsequent calls to getEntityAsFoo work. Is there a reason for this? Looking at the source I saw that it is possibly due to the fact data is read off a stream of unknown length and caching request data may be prohibitively expensive? By the time the server is processing the request is the client pipe closed? (I guess I'm thinking about something like continuations). I'm just curious, I have no plans to offer another implementation :) I suppose I'll need to rethink my implementation if I wish to make restlets behave in an filter/guard agnostic manner. By the way, this is a nice paradigm, I much prefer it over servlets. thanks.
