[seam-dev] HTTP optimization guide

[Dan Allen]

>
> We are duplicating lots of functionality in Seam that any JAX RS
> implementation has. We should probably drop SeamResourceServlet and maybe
> even SeamFilter in Seam3 and rebuild what we need on top of JAX-RS. The
> downside is that we'd create a dependency on a JAX-RS implementation. OTOH
> almost anyone might want one of these in the future anyway.


Yes, I think we should do this. JAX-RS has such a low footprint and is vital
to the future of Java EE web apps, so like many other specs that we
"recommend highly" I think this should certainly be one of them. We can
always back off and try to abstract an SPI if the community is uneasy about
the direction.

-Dan

-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20090715/1af07353/attachment.html