Re: Going to other context and/or server in 1.1

[Eddie Bush]

Well, we could implement a static array of protocols somewhere - and iterate over them to see if there's a match (like was being done with module prefixes before). Then, adding support for another protocol would just be a matter of editing that one array.

Should this go in Globals?

You've got a good point, Cliff.

Cliff Rowley wrote:

I would have thought the same would apply for any specified protocol
scheme.  For example someone may wish to redirect to an ftp:// through
the action forward, or maybe news:// - who knows.  Without a protocol
specification of any description it's probably safe to assume we want
context relative.

Having said that, I don't know enough to spot any possible caveats.

-----Original Message-----
From: David Graham [mailto:dgraham1980@;hotmail.com] Sent: 18 October 2002 16:29
To: [EMAIL PROTECTED]
Subject: Re: Going to other context and/or server in 1.1

I thought of the http:// matching as well. Are there any cases when this logic wouldn't work? Hardcoding the protocol may be a bad idea.

David

--
Eddie Bush




--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>