[Seaside-dev] path parameters in WAUrl?

[Julian Fitzell]

Hmm... I haven't actually gone and looked at the code, but conceptually I'm
not totally convinced that should be part of WAUrl (after all, people could
use many syntax forms within path segments). As you said, the spec says
nothing about the meaning of the path; would it be more logical to have
something you can use to parse/generate such URLs?

Julian

On Tue, Jul 5, 2011 at 6:09 AM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> 2011/7/5 Julian Fitzell <jfitzell at gmail.com>:
> > Do you mean in the actual Seaside released package or just in your
> > application?
>
> The "trunk" code base.
>
> > Also, I'm not clear what you mean by "map the path index to the parameter
> > values"...
>
> Give the URL /examples/counter;_s=sessionId
>
>  1 -> nil (missing association)
>  2 -> {_s: sessionId}
>
> It also has the slight advantage that it doesn't have to be repeated
> as a hidden field in the form but I don't think we want to change
> this.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20110708/5c600b09/attachment.htm