<snip>In ATG's et. al. defense, it is often important to pass session data and other URL-encoded info for shopping, personalization, and perhaps advanced reporting, but do the URLs really have to be interminably long and opaque? </snip>
> Cheers, > > Tony Byrne Passing data via URL rewriting, or by traversing subpaths is nasty old school web development. Fine for quick and dirty weekend projects - I'm guilty of using these techniques on occasion. But it's unnecessary, and in my opinion, unacceptable to use these techniques in so-called high-end "next generation" applications. There are other methods for client-side and server-side persistence, each with its own advantages and drawbacks. A quick Internet search on persistence, and passing parameters between pages and applications will reveal several techniques. I guess you can say I do hate the impossibly long and non-meaningful-to-the-user URLs that are generated by some of today's CMS packages. :-) Joe -- http://cms-list.org/ more signal, less noise.
