Re: Encoding problems

2003-03-12 Thread Santiago Gala
Gianugo Rabellino wrote: Santiago Gala wrote: Last-Modified: could be filled with this (the aggregated semantics for it is clear, I think: the highest modification date in the compound validity object). For objects implementing "dynamic" retrieval, like xsp sheets, they should set "now" and a c

RE: Encoding problems

2003-03-12 Thread Carsten Ziegeler
Santiago Gala wrote: > > > Last-Modified: could be filled with this (the aggregated semantics for > it is clear, I think: the highest modification date in the compound > validity object). For objects implementing "dynamic" retrieval, like xsp > sheets, they should set "now" and a close to zero exp

Re: Encoding problems

2003-03-12 Thread Gianugo Rabellino
Santiago Gala wrote: Last-Modified: could be filled with this (the aggregated semantics for it is clear, I think: the highest modification date in the compound validity object). For objects implementing "dynamic" retrieval, like xsp sheets, they should set "now" and a close to zero expiration da

Re: Encoding problems

2003-03-12 Thread Santiago Gala
Carsten Ziegeler wrote: Santiago Gala wrote: Re: cache comments later: When I was discussing Cocoon (then new) cache ideas with Ricardo Rocha, (so around winter 2000/spring 2001) I sent an idea to Cocoon-dev about propagating the CacheValidity to set the Expires in the seriazed output. It loo

RE: Encoding problems

2003-03-11 Thread Carsten Ziegeler
Santiago Gala wrote: > Re: cache comments later: > > When I was discussing Cocoon (then new) cache ideas with Ricardo > Rocha, (so around winter 2000/spring 2001) I sent an idea to Cocoon-dev > about propagating the CacheValidity to set the Expires in the seriazed > output. It looked like a

Re: Encoding problems

2003-03-11 Thread Santiago Gala
Stefano Mazzocchi wrote: Vadim Gritsenko wrote: Stefano Mazzocchi wrote: ... On the other hand, by placing the server creates an HTTP header that instructs the user-agent about the encoding. This solved the encoding problem on *all* browsers. Why not simply patch the serializer to set pro

Re: Encoding problems

2003-03-11 Thread Vadim Gritsenko
Amir Rosen wrote: -Original Message- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 8:22 PM To: [EMAIL PROTECTED] Subject: Re: Encoding problems Vadim Gritsenko wrote: Stefano Mazzocchi wrote: ... On the other hand, by placing the

RE: Encoding problems

2003-03-11 Thread Amir Rosen
> -Original Message- > From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2003 8:22 PM > To: [EMAIL PROTECTED] > Subject: Re: Encoding problems > > > Vadim Gritsenko wrote: > > Stefano Mazzocchi wrote: > > ... >

Re: Encoding problems

2003-03-11 Thread Stefano Mazzocchi
Vadim Gritsenko wrote: Stefano Mazzocchi wrote: ... On the other hand, by placing the server creates an HTTP header that instructs the user-agent about the encoding. This solved the encoding problem on *all* browsers. Why not simply patch the serializer to set proper content-type header? D'o

Re: Encoding problems

2003-03-11 Thread Vadim Gritsenko
Stefano Mazzocchi wrote: ... On the other hand, by placing the server creates an HTTP header that instructs the user-agent about the encoding. This solved the encoding problem on *all* browsers. Why not simply patch the serializer to set proper content-type header? Vadim

Re: Encoding problems

2003-03-11 Thread Jeremy Quinn
On Tuesday, March 11, 2003, at 11:48 AM, Stefano Mazzocchi wrote: The new webapp welcome page contains a copyright character which is not encoded as the default HTML entity © or the usual &xxx; char, but it's directly copied in the proper encoding. Many thanks for your analysis and confirmati