[Seaside-dev] path parameters in WAUrl?

[Julian Fitzell]

<shrug> Ok, as you wish. :)

On Fri, Jul 8, 2011 at 11:15 AM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> 2011/7/8 Julian Fitzell <jfitzell at gmail.com>:
> > 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).
>
> If it's not part of WAUrl then it gets quite hard to support this. It
> gets passed to the application as part of the request URL, it get
> rendered on the document as part of the actions URL.
>
> > As you said, the spec says
> > nothing about the meaning of the path;
>
> The spec explicitly mentions that applications (can) do that.
>
> > would it be more logical to have
> > something you can use to parse/generate such URLs?
>
> IMHO it would be logical to have in in WAUrl.
>
> 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/0ec072be/attachment.htm