Not to be a nit, but how come nearly every one of your email responses ends in a pitch for "Carrier"?
-----Original Message----- From: Jing Zhou [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 2:58 PM To: Struts Users Mailing List Subject: Re: url-pattern ----- Original Message ----- From: "Eric Jain" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Tuesday, June 24, 2003 8:47 AM Subject: Re: url-pattern > > Why don't you want to use "standard" .do servlet mapping ? > > I have the same issue with Struts. If you are maintaining a site that > has been running since many years and there are thousands of external > pages linking to it, naturally you want to avoid sprinkling technology > of the day into your URLs. > > As a note on the side, it's a pitty Struts doesn't support REST style > URLs well. If anyone has any tips or thoughts on this, I'll be glad to > here from you! REST can be considered as a *fix* to the SOAP based web services where every one has to invent or re-invent protocols over the SOAP. It increases the scalability over the SOAP model by using its stateless URLs to resources. It solves some problems where RPC based web services can'nt. But when we come to real world applications, we need stateful mechanisms to integrate different web services. The idea to bundle resources and user interfaces together in web services and deliver them as needed is one of key innovations in Carrier. One of use cases is that one page author publishes a resource with user interface at one web site, another author could incorporate the published resource and user interface into his own web applications in a different web site. This is what we called Hyper Action Wizard in Carrier. At this moment, we have not gone that far yet. But you could do it across application modules now. > > -- > Eric Jain > Jing Netspread Carrier http://www.netspread.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
