Re: Javascript implementation limitation

btw, I'm not familiar with chiba. how much of the processing is done client-side in chiba? one reason I'm prefering client-side solution is for responsiveness of the ui. other server side implementations introduce a lag which is not acceptable for my app.

--- On Fri, 12/4/09, Joern Turner <joernturner@me.com> wrote:


From: Joern Turner <joernturner@me.com>
Subject: Re: Javascript implementation limitation
To: "Mats Eklund" <mats.eklund@yahoo.com>
Cc: www-forms@w3.org
Date: Friday, December 4, 2009, 10:00 AM


Mats,

On Dec 3, 2009, at 10:21 PM, Mats Eklund wrote:

> Hi,
> 
> 
> I'm weighing pros and cons of two xforms implementations, one is a server side implementation and the other is a browser side implementation in javascript. It appears to me that one inherent limitation of a javascript implementation is that xforms submissions with replace="all" is impossible to achieve. Any insights welcome?
> 
That's not right. In Chiba we support submission/@replace="all". Though it comes to the price of having an additional URI param on the resulting URL. On the other hand you can always substitute a replace all with a combination of submission and load.

Regards,

Joern

> 
> Thanks,
> 
> Mats
> 
>