You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by bo <bo...@groupserve.com> on 2000/09/27 23:27:18 UTC
phone.com cache problem
Hi All,
While I am using xsl to transform xml to wml, I hope the cache of the phone
doesn't work. so I should use the following:
*************
<head>
<meta http-equiv="Cache-Control" content="must-revalidate"/>
</head>
*************
This will not work if the attributes order of meta is reversed. While I use
it in xsl, the final wml code would become:
*************
<head>
<meta content="must-revalidate" http-equiv="Cache-Control"/>
</head>
*************
The order of the two attributes in meta has been changed and will not work.
So my question is :
How can I prevent the automatic order change while using xsl?
Thanks!
Fan
RE: phone.com cache problem
Posted by bo <bo...@groupserve.com>.
This doesn't work either. The final wml code will become:
<head>
<meta content="max-age=0" forua="true" http-equiv="cache-control" />
</head>
-----Original Message-----
From: ChenJP [mailto:chenjp@email.com]
Sent: Wednesday, September 27, 2000 9:10 PM
To: cocoon-users@xml.apache.org
Subject: Re: phone.com cache problem
try following :
<head>
<meta forua="true" http-equiv="cache-control" content="max-age=0"/>
</head>
----- Original Message -----
From: "bo" <bo...@groupserve.com>
To: <co...@xml.apache.org>
Sent: Thursday, September 28, 2000 6:27 AM
Subject: phone.com cache problem
> Hi All,
>
> While I am using xsl to transform xml to wml, I hope the cache of the
phone
> doesn't work. so I should use the following:
>
> *************
> <head>
> <meta http-equiv="Cache-Control" content="must-revalidate"/>
> </head>
> *************
> This will not work if the attributes order of meta is reversed. While I
use
> it in xsl, the final wml code would become:
>
> *************
> <head>
> <meta content="must-revalidate" http-equiv="Cache-Control"/>
> </head>
> *************
> The order of the two attributes in meta has been changed and will not
work.
>
> So my question is :
> How can I prevent the automatic order change while using xsl?
>
> Thanks!
>
> Fan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
Re: phone.com cache problem
Posted by ChenJP <ch...@email.com>.
try following :
<head>
<meta forua="true" http-equiv="cache-control" content="max-age=0"/>
</head>
----- Original Message -----
From: "bo" <bo...@groupserve.com>
To: <co...@xml.apache.org>
Sent: Thursday, September 28, 2000 6:27 AM
Subject: phone.com cache problem
> Hi All,
>
> While I am using xsl to transform xml to wml, I hope the cache of the phone
> doesn't work. so I should use the following:
>
> *************
> <head>
> <meta http-equiv="Cache-Control" content="must-revalidate"/>
> </head>
> *************
> This will not work if the attributes order of meta is reversed. While I use
> it in xsl, the final wml code would become:
>
> *************
> <head>
> <meta content="must-revalidate" http-equiv="Cache-Control"/>
> </head>
> *************
> The order of the two attributes in meta has been changed and will not work.
>
> So my question is :
> How can I prevent the automatic order change while using xsl?
>
> Thanks!
>
> Fan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
Re: Missing example in 1.8?
Posted by Uli Mayring <ul...@denic.de>.
On Wed, 27 Sep 2000, Per Kreipke wrote:
> What happened to the 'complex' sample in 1.8?
Once cocoon has reference platforms defined, I'm going to work it over and
release it again. AFAIK it never was a part the cocoon distribution.
Ulrich
--
Ulrich Mayring
DENIC eG, Softwareentwicklung
Missing example in 1.8?
Posted by Per Kreipke <pe...@onclave.com>.
What happened to the 'complex' sample in 1.8?
Per