W3C home > Mailing lists > Public > public-webapi@w3.org > September 2007

Re: Form Serialization Idea

From: Subbu Allamaraju <subbu.allamaraju@gmail.com>
Date: Mon, 24 Sep 2007 13:07:22 -0600
Message-ID: <e3f21b1a0709241207y2b15ef9ek59583785eafec8e2@mail.gmail.com>
To: "Garrett Smith" <dhtmlkitchen@gmail.com>
Cc: public-webapi@w3.org
Does this approach take the enctype into account? What is the behavior if a
given form can't be serialized for a given enctype?
Cheers
Subbu

On 9/11/07, Garrett Smith <dhtmlkitchen@gmail.com> wrote:
>
>
> I've started a document a while back. It's related to Robin's File and
> FileList proposal, taking it a step towards complete FORM
> serialization. Robin suggested I post my idea up here, so here goes...
>
> The problem: No standard, reliable way to get FORM data to an Ajax
> request.
>
> Proposal:
> interface HTMLFormElement {
>   string getDataSetString(); raises FileException
>   string toJSONString(); raises FileException
> };
>
> I've tried to exhaust the pros and cons of other possible solutions,
> and provided numerous references here:
> http://dhtmlkitchen.com/rec/FormSerialization.html
>
> The proposed functionality is hand-rolled into every Ajax libary
> (using javascript), and the logic to get the FORM's successful
> controls is more complicated than it initially would seem. It's
> problematic to have to depend on a library when the library components
> are interdependent on other library components. For example, use YUI,
> jQuery, or Prototype, but don't mix them in the same page.
>
> Garrett
>
>
> --
> Programming is a collaborative art.
>
>


-- 
------------------------------
http://www.subbu.org
Received on Monday, 24 September 2007 19:07:35 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 December 2014 20:05:34 UTC