« Return to Thread: Caching of Seam Remoting Interface Components

Re: Caching of Seam Remoting Interface Components

by Dan Allen (mojavelinux) :: Rate this Message:

Reply to Author | View in Thread

On Thu, Jun 25, 2009 at 6:58 PM, Pete Muir <pmuir@...> wrote:

On 25 Jun 2009, at 22:29, Christian Bauer wrote:


On Jun 25, 2009, at 22:35 , Pete Muir wrote:

I would suggest /interface.js/component1;component2 etc.

I'd recommend /component1;component2/interface.js which leaves the URI design open for further sub-resources (of maybe different representation types) that describe component(s).

Much better :-)

+1

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

 « Return to Thread: Caching of Seam Remoting Interface Components