Hi Lenya devs,

studying the proxy transformer reveals that it handles quite a lot
of the functionality which the uuid2url transformer already does.
IMO the proxy transformer is indeed the more appropriate place.

So IMO we should

  - move the recently refactored URL building functionality from
    the uuid2url to the proxy transformer

  - define a standardized input URL format for the proxy transformer,
    which serves also as the interface between the uuid2url and
    proxy transformers

This way the tranformers wouldn't overlap, but complement each
other (orthogonal behaviour).

IIUC the proxy transformer reacts on absolute URLs without the
context path. Is this sufficient, or should we define a specific
URL scheme (like lenya-link:/) for more clarity?


Assuming we just use absolute URLs, the sequence would look like this:

  <a href="lenya-document:{uuid}">
    |
    | uuid2url transformer
    |
  <a href="/mypub/live/foo">
    |
    | proxy transformer
    |
  <a href="http://myserver.com/foo"/>


Or, in the case of a CSS file:

  div { background: url('<root/>/images/foo.png') }
    |
    | XSLT + params
    |
  div { background: url('/mypub/live/images/foo.png') }
    |
    | Chaperon
    |
  <a href="/mypub/live/images/foo.png">
    |
    | proxy transformer
    |
  <a href="http://myserver.com/images/foo.png"/>
    |
    | XSLT
    |
  div { background: url('http://myserver.com/images/foo.png') }


WDYT?

-- Andreas


-- 
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to