[Kss-devel] Server response format

[Balazs Ree]

Sat, 12 May 2007 18:28:57 +0200 keltezéssel Godefroid Chapelle azt írta:

>> I would rather not duplicate the current behaviour (at least not until
>> I understand why it is done this way) in the new kss.commands package.
>> So please enlighten me on the design choices so that I may understand
>> them.
> 
> IIRC, the main reason for this "broken" format is IE6. The trouble being
> its broken implementation for importing  in the browser document the
> nodes from the document in the response of the XMLHTTPRequest.
> 
> I am afraid you'd need to go through all the hurdles we overcame before
> finding a new format that really works.
> 
> One of those hurdles was the fact we had to be in the html namespace
> instead of being able to use the a plain kukit namespace.
> 
> However, if you can prove me wrong, I am all for a format that we could
> validate. Keep in mind that a new format would imply changes in the js
> client as well, iow stuff that would need to be tested in each browser
> that we want to support.
> 
> But I'd advise you to do this as a second step if you want to have a
> pure Python implementation. Do not underestimate the time invested in
> the current code ;-)

I also insist to decouple the question of the transport format. At the 
moment we have a transport format that works reasonably well. However 
let's not ignore the goal: to make the server side usable from plain 
python, and not changing the transport format (which would imply changes 
in the current zope components, and the javascript code immediately).

I suggest that unless it turns out that the current transport format is 
not posible or very difficult to implement from python (which is not the 
case), stick to it completely.

Also what Jeroen writes about the brokenness of current XML is not true: 
we have the parser class that validates and fixes broken html so we 
cannot at the moment issue broken xml. I suggest this behaviour is also 
preserved in the plain python generation. Iow, I do not believe the 
current solution is broken.

On the other hand we can improve the format later if we like to, but 
since it works perfect at the moment, a real good reason is needed.

-- 
Balazs Ree