Konstantin Priblouda wrote:
>
> > This will allow one to use / in the templates, the
> > urls will still
> > contain , (comma)
> > Turbine treats pathinfo as name/value pairs.
> > Therefore you cannot use /
> > in template paths as it will mess up the name value
> > pairing.
> >
> > template/store,Department.vm/id/1 =>
> > template=store,Department.vm and
> > id=1
> > template/store/Department.vm/id/1 => template=store
> > and Department.vm=id
> > and 1=
>
> Well, I see. But why to choose / as separator?
> What was wrong with classical way of parameter
> passing?
> ( ?&= ) If it would be used there will be no
> need to write parameter parsing. It would be done by
> servlet container.
>
> BTW, am I wrong that turbine is meant too be used
> with path mapping only?
>
You can use query parameters, "pathinfo parameters", or a combination of
the two. You should be able to do something like:
$link.addQueryData("template", "store/Department.vm") and it will work
fine. Though I have not tested
this. The main reason for using pathinfo over query data is that most
indexers ignore url's that contain query data as they are dynamic
content. It may also help with log analysis, but i am not an expert in
these areas. If you have a site that is dynamically generated such as a
store, but you want your site to be indexed, it is best to make it
appear as static data.
john mcnally
>
> There is only one problem -> it looks ugly
> "template/user%2CFluxUserList.vm"
>
IE will show %2C as a comma, so it is not quite so ugly, though i am not
sure what makes %2C uglier than comma. Not sure whether IE users or
netscape/mozilla users are more concerned about url prettiness, but you
can be comforted that most users will not see the encoding and i doubt
more will not care what the url looks like anyway.
john mcnally
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
