Within Cocoon (within a serializer) you have all posibilities of Java
and Java provides an interface for C functions AFAIK.
Reinhard
> -Original Message-
> From: Oliver Egger [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 5:44 PM
> To: [EMAIL PROTECTED]
> Subject: Serializer
>
Carsten Ziegeler wrote:
Paul Duffin wrote:
Why is the Serializer not an instance of SitemapModelComponent when both
generators and transformations are ?
The following link shows a discussion which took place in April this
year which seemed to indicate that this was going to be changed but
u
>Paul Duffin wrote:
>Why is the Serializer not an instance of SitemapModelComponent when both
>generators and transformations are ?
>
>
>
>The following link shows a discussion which took place in April this
>year which seemed to indicate that this was going to be changed but
>unfortunately it do
Frank Taffelt wrote:
>
> Hi,
>
> it seems that the Xalan-Bug
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5779 doesn't affect
> current cocoon codebase.
>
> The current AbstractTextSerializer has a workarround for this which uses a
> simple identity transform Stylesheet. This Solution se
Someone correct me if I' m wrong but...
At the moment, I think you'll have to write an "Action" for this. AFAIK
Serializers are currently tied to the
response output stream. Personally, I think that cocoon should
ultimately seperate the location concern and
allow multiple serializers in a pip
Jens Lorenz wrote:
> Well, IMHO there are still some cases where a GZIPSerializer might
> be useful. But thanks to you Luca and Stefano for opening my eyes
> for the world outside Cocoon.
You are welcome.
Anyway, I believe that a HTML-gzipping-serializer is a bad idea because
is mixes concerns:
- Original Message -
From: "Luca Morandini" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 29, 2002 4:51 PM
Subject: RE: serializer sending gzip compressed html
> Jens,
>
> maybe it is just me, but... what about web-server compression ?
Jens,
maybe it is just me, but... what about web-server compression ?
I suppose the web-server intercepts and compresses the output coming out of any
servlet (as long as the servlet has not been called
directly (i.e. ":8080"))... am I wrong ?
Best regards,
---
Jens Lorenz wrote:
>
> Hi,
>
> since the issue has been raised on cocoon-users I've been
> hacking on serializers which automatically gzip compress
> the (cocoon) produced html before it is send to the browser
> on the client side.
> BTW: this should also reduce the size of the cache dir since
>
er would be an ugly hack.
Stefan
> -Original Message-
> From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 08, 2002 12:48 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Serializer configuration, was: [status & RT] design
> challenges
>
>
>
Vadim Gritsenko wrote:
>
> > From: Sylvain Wallez [mailto:[EMAIL PROTECTED]]
> >
> > Stefano Mazzocchi wrote:
>
>
>
> > > 1) serializers don't have full access to the component environment
> > > and some want this to be changed
> > >
> >
> > The major need is to be able to access the SourceRes
Vadim Gritsenko wrote:
>>From: Sylvain Wallez [mailto:[EMAIL PROTECTED]]
>>
>>Stefano Mazzocchi wrote:
>>
>
>
>
>>>1) serializers don't have full access to the component environment
>>>and some want this to be changed
>>>
>>The major need is to be able to access the SourceResolver. I haven't
>>s
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
>
> From: "Sylvain Wallez" <[EMAIL PROTECTED]>
>
> > Please find below an answer I gave to a colleague on cocoon-users.
After
> > more thoughts, I think to have found a good example of a Serializer
that
> > could take advantage of both Parame
From: "Sylvain Wallez" <[EMAIL PROTECTED]>
> Please find below an answer I gave to a colleague on cocoon-users. After
> more thoughts, I think to have found a good example of a Serializer that
> could take advantage of both Parameters and SourceResolver...
I have another need: I have a Seriali
14 matches
Mail list logo
