Re: Javascript implementation limitation

submission then load is how I currently do it, however, this requires the server to be tweaked to respond with a redirect in a non-conventional way. By conventional I'm referring to the "PRG pattern" (http://en.wikipedia.org/wiki/Post/Redirect/Get). As long as this pattern isn't used, there is no problem. Maybe xforms was not intended to be used with this pattern...?


--- 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
> 
>