cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: Some notes on Deli
Date Mon, 28 Jan 2002 16:13:08 GMT
> From: Butler, Mark [mailto:Mark_Butler@hplb.hpl.hp.com]
> 
> Hi Carsten
> 
> > I see currently two (minor) problems with Deli:
> > - the legacyDevice.xml contains profile references which are URIs.
> >   As these URIs are served by Cocoon, they currently contain
> > the server name
> >   and the server port (assuming localhost and 8080 is correct).
> >   This is a bad dependency. It would be creat to have this
> > configuration
> >   independent of the servlet context.
> 
> Some possible solutions - comments please?
> 
> 1. Make profiles available as web resources:
> 
> I can copy the legacy profiles to
> http://www-uk.hpl.hp.com/people/marbut/legacyProfiles
> 
> Then we can update legacyDevices.xml to point to these profiles,
keeping the
> old file (legacyDeviceFallback.xml ?) for folks behind firewalls / not
> connected to the internet?
> 
> Possible issues here: I can't guarantee these profiles will be
permanent web
> resources e.g. if HP web pages changes etc. Perhaps my web page is not
the
> most appropriate place to site them but placing them somewhere else
will be
> more difficult.
> 
> 2. Alter the format of the legacydevice file:
> 
> Is the real problem that the legacydevice file has to use repeated
instances
> of the host name / port number? For example would a format that
abstracted
> this information as a "profile repository" be better? E.G.
> 
> <devices>
> <repository>
> 	<name>local</name>
>       <host>http://localhost</host>
> 	<port>8080</port>
> 	<path>cocoon/legacyProfiles</path>
> 	<legacyDevice>
> 		<useragentstring>MSIE</useragentstring>
> 		<profileref>mieSample.rdf</profileref>
> 	</legacyDevice>
> 	<legacyDevice>
> 		<useragentstring>mozilla</useragentstring>
> 		<profileref>mozSample.rdf</profileref>
> 	</legacyDevice>
> </repository>
> </devices>
> 
> Here, although localhost and port number are hard-coded, there is only
one
> instance to alter?

Can you use Cocoon sources or URLFactory to access this resource to
avoid having host/port completely? It would be possible to use
resource:// or context:// or file: protocols instead of (only) http
then.

Vadim

<snip/>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message