Dev at weitling pisze:
Sounds cool, but doesn't this result in a scenario like this?:
- browser calls resource A
- resource A runs through a pipeline calling resource B
- resource A is a SAX-pipeline, serializes SAX-events to POST-parameters
for calling B
You are not limited to POSTing XML data
Hi Grek,
you asked us to give our two cents so after a day of reading your long,
long text I'll try to ;-)
I'll surely have to re-read it but here are some thoughts:
> I promised to give an overview on our Servlet Service Framework, its
> status and relation to the
> Resource-Oriented Architectur
Hi Cocooners,
I promised to give an overview on our Servlet Service Framework, its status and
relation to the
Resource-Oriented Architecture (ROA) and RESTful design principles. My
knowledge about REST comes
mainly from RESTful Web Services[1] by Leaonard Richardson and Sam Ruby. I'll refer and
