cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ovidiu Predescu <>
Subject Re: DELI support added
Date Thu, 10 Jan 2002 18:18:43 GMT
On Thu, 10 Jan 2002 17:36:28 -0000, "Butler, Mark" <> wrote:

> Hi Steven
> > > I guess we should use the resource:/ protocol for locating 
> > the profile
> > > docs, since http://localhost:8080/.../legacyProfiles/... 
> > seems like a
> > > *very* big assumption to me.
> I'm not sure what you mean by the resource:/ protocol - could you elaborate?

This is an internal Cocoon protocol which resolves the URL relative to
Cocoon's internal resources. It's much faster than posting an HTTP
request to a URL.

However the URL is not Java visible, so will not work
with the resource: protocol. You'll need to make use of SourceResolver
from Cocoon, which may not be an option for the DELI library.

> Currently developers can configure the parameter you mention in the
> legacyDevice.xml file. This associates the user agent strings of devices
> that are not CC/PP aware with URLS for "legacy" CC/PP profiles. At the
> moment I've included a few (not particularly good) legacy profiles for
> demonstration purposes. 
> Of course, as you've highlighted, developers will probably want to change
> this on a live server. Hopefully when CC/PP is widespread, there will be
> some servers acting as profiles repositories that legacyDevice.xml can point
> to. However when we get DELI working with Cocoon it will be the first
> application to support CC/PP so getting hold of profiles is actually quite
> difficult at the moment. 
> Does this seem reasonable? As ever any suggestions welcome. 

I think it does, especially if the legacy device profiles are cached
on the Cocoon side, instead of being retrieved on each request. As I
noticed from the code, you do seem to do this, right? If so the above
point may not do any good.


PS: BTW Mark, I had to disable the use of DELI from cocoon.xconf in
the MAIN trunk because Cocoon would not start up. Could you please
investigate to see what's going on?

To unsubscribe, e-mail:
For additional commands, email:

View raw message