Vadim Gritsenko wrote:
Yes, I understood, I replied with the possibility of a source that builds on the Request inputstream.Nicola Ken Barozzi wrote:No, I've meant RequestFactory, from compontents.request package, not an input source.Vadim Gritsenko wrote:An InputStreamSource would be nice, so that any Generator can act on it.Nicola Ken Barozzi wrote:What do you think - is it possible to eliminate StreamGenerator by adding some functionality to the RequestFactory?
We have StreamGenerator. Which is in fact tied to Servlets!
src="inputstream://"
Same place where MIME is decrypted and file attachments are processed.I don't understand what you want to do with the request factory here
If the Request interface doesn't have inputstream, it simply doesn't, what would you like to do with the factory?
Good example. Web services are not done only on servlets. Messaging systems use asynch web services. Component systems are not based on servlets. SOAP can go almost everywhere.Bad example. It is servlet environment, again. It is not command line or other environment.Simple example: web services. the request contains the data that I must process.This is incredible, if I want to get a stream from a request I have to have Servlets!Is there any justification for getInputStream() for non-servlet environment?
We have a bunch of methods on the request, is there a reason that we cannot get the inputstream? I don't see the real need of having it this way, does anyone know if there was a reason for it?
Show me the code. I want to add a getInputStream() method to the Request interface. And make a cocoon source to get it in the sitemap.If no, I think it's better to try to encapsulate servlet-specific logic into the factory.
What's your take?
What do you propose?
BTW, this has in fact come out during the input pipelines discussion, from a conceptual POV. I wasn't sure, so I dealt in the code and this is what I found...
-- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]