I realize the advantages of the query strings with slashes
instead of ? and &.. I've implemented similar parameter
parser for other non java servlet setups.


Problem.. It really screws with anybody's ability to analyze
the logfile in a meaningfull way as far as counting page hits
or anything.. Anybody have any ideas on how to get the best
of both worlds? Search engines think the pages are semi static
but log analysis doesn't choke?

If I'm forced to go back to <servletname>?param=value&param=value
is there any easy way to switch to this in turbine?  I assume
I'll have to fix the $link. object in the Velocity context to output the
type I want and that is it since the parameter parser never
lost the ability to understand the ?=& style.

My best option would be if I could combine the two, rather
than having

/servlet/turbine?template=UserInfo&ID=5

I would need 
/servlet/turbine/template/UserInfo?ID=5

so that the log stats will see real page hit count for the template
and not just the turbine servlet. thoughts on how to easily implement
this assuming that template is the first arguement in the query string?


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to