You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@lenya.apache.org by Bart van Dijk <Ba...@Unilever.com> on 2005/04/18 17:51:28 UTC

Multiple file publishing

Hi,

I'm trying to publish my pages in three different ways, based on three
different style sheets. Think of having one XML file published into three
HTML files with a different layout for each of them. There might be more
than just one way to do this, but I'm not sure what to do.

Should I add two more pipelines, or add a few tasks? If someone knows how to
configure this, I'd be very happy!

Bart

Re: Multiple file publishing

Posted by so...@gmail.com.

Everybody wrote:
>Solprovider, why do you prefer your first solution over the second?

Ignoring the "caching of doctypes" issue, the two solutions are
functionally identical.  They each add a select around a function
call.  Both require the same amount of processing.  The second has a
few more lines of code, because the format suggests each parameter to
the function call be placed on a separate line, and the transform
function has more parameters than the generateConfig function; most
other programming languages would do it with one line of code..

The goal is to rewrite the line:
<map:transform src="xslt/page2xhtml-{4}.xsl">
so {4} is configurable.  
- The second version does it by copying the line and hardcoding a value.
- The first version accepts {4} is already configurable, and adds the
test where it is decided.

* Version 1 *
doctype =getDoctype() ;
transform(doctype);

function getDoctype{
if(style=="1"){
return "zzz";
}else{
return this.doctype;
}

* Version 2 *
doctype =getDoctype() ;
if(style=="1"){
transform("zzz");
}else{
transform(doctype);
}
function getDoctype{
return this.doctype;
}

The first decides doctype where doctype is decided.
The second overrides doctype where doctype is used.

MAINTENANCE CONSIDERATION: If doctype was used anywhere else, and you
want it to change for everything, it would be much cleaner to set it
in getDoctype() rather than every place it is used.

PERFORMANCE CONSIDERATION: Since doctype is only used once, it is
possible to optimize version 2 by moving the "doctype =getDoctype()"
inside the if.  For this code, that requires changing other functions
to stop passing it as a parameter.  That means changing even more code
(chancing more bugs) and changing the API (breaking other calls to the
function).

There is a function for getDoctype().  The goal is to change the
doctype.  That is the logical place to do it  -- unless doctype needs
to be set according to the usual rules, and only the display is
overridden.  Then the second version is the only one that meets the
goals.

Which version to use depends on what doctype should be in other
functions.  Since no other functions are called, it does not matter. 
Since the first version has a bug avoided in the second version, use
the second.

solprovider

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

Re: Multiple file publishing

Posted by so...@gmail.com.

On 4/26/05, Michael Wechner <mi...@wyona.com> wrote:
> you can disable the [live cache] within the sitemap default/publication-sitemap.xmap:
> <map:when test="{global:cache-dir}/{../1}.html.DISABLED">
> Michi

1. I commented the three lines for my pub.  I dislike "if(false)"
statements because the processor must perform the test.  Every
nanosecond counts.

2. I want the performance improvement from caching, but the caching is
not security concious.  Every page in my pub changes when a visitor is
logged in.  I can cache non-logged-in requests by adding 3 pipelines
to do:
if(not authenticated) checkCache

Creating pages for each type of user may require a custom Action. 
Making it generic would take some time.  Best would be an XMAP
variable for Groups or Roles.  Then decide the cache based on a some
property containing which Groups|Roles are relevant.  Then need to
store each version of the document in separate caches based on which
Groups|Roles are active for this visitor.  The only unique-per-visitor
page is their personal information; that is handled by the Session
usecase, and there is no caching.

If performance becomes an issue, I am planning to pass control to a
JavaScript function which returns which cache to use (and the original
request), then pass that around the pipelines.  We need 4 caches:
anonymous, visitor, employee, and admin.   That should be much easier
than writing a generic solution.  A generic solution could have many
caches if every combination of Groups is assigned its own directory
(although some may never be used.  In my example, all admins are
employees, so an admin-only directory would never be created.)

solprovider

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