[OT] RE: url-pattern

[Mike Jasnowski <mj...@bea.com>]

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:jing@netspread.com]
Sent: Tuesday, June 24, 2003 2:58 PM
To: Struts Users Mailing List
Subject: Re: url-pattern



----- Original Message -----
From: "Eric Jain" <Er...@isb-sib.ch>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
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: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org

Re: [OT] RE: url-pattern

[Jing Zhou <ji...@netspread.com>]

----- Original Message ----- 
From: "Mike Jasnowski" <mj...@bea.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Tuesday, June 24, 2003 2:35 PM
Subject: [OT] RE: url-pattern


> Not to be a nit, but how come nearly every one of your email responses
ends
> in a pitch for "Carrier"?

If you could publish core algorithms from your REAL projects that are
helpful to Struts users, that would be greate I think. Get a permission
form your employer?

>
> -----Original Message-----
> From: Jing Zhou [mailto:jing@netspread.com]
> Sent: Tuesday, June 24, 2003 2:58 PM
> To: Struts Users Mailing List
> Subject: Re: url-pattern
>
>
>
> ----- Original Message -----
> From: "Eric Jain" <Er...@isb-sib.ch>
> To: "Struts Users Mailing List" <st...@jakarta.apache.org>
> 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: struts-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: struts-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org