- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 2 Dec 2008 08:17:56 +0000 (UTC)
On Sat, 1 Nov 2008, Erik Wilde wrote:
> > >
> > > The benefit would be having more control over the construction of
> > > the URI rather than just the query parameters. I could have a form
> > > with two simple fields "a" and "b" and specify
> > > "http://test.org/customers/{a}/reports/{b}" as the action URI.
> >
> > I don't understand why this is such a big deal. Such, the URIs are
> > nicer, but, big deal. Just do a redirect if it matters that much.
>
> i think this is the fundamental problem. you can do redirects if you
> have everything under one control, the service provider and the one
> building the forms. if this is not the case, then there is no way you
> can do redirects. there is a service with a given URI scheme, and you
> have to use it like that. can you build a form for it?
Just build a redirector on the same site as you build the form.
> anyway, like i said above, html5 might decide not to be interested in
> that functionality or might regard it as out of scope. all i want to say
> here is that to see the value in that proposal, it is important to
> depart from the traditional view of form clients and services always
> being created by one entity.
I think it's an interesting proposal, but it doesn't seem ground-breaking
enough to really warrant additions in HTML5 at this point.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 2 December 2008 00:17:56 UTC