> Amazon is a pretty good example; there's a rather complex > Web app that > runs the site, and I can't ever remember seeing a > ?query-string URL; > it appears to pass all arguments as hierarchical elements > separated by > "/".
We do things like this now, using Webware and mod_rewrite. Not that I'm particularily enamored with having to create page-specific regexps for mod_rewrite, but I think it will be specific and hard to generalize for webware to automatically handle. For instance, old-style URL for us: http://www.somewhere.com/products.psp?id=502 is viewed/linked for the real world: http://www.somewhere.com/products/502 and could just as easily be http://www.somewhere.com/products/view/502 as opposed to perhaps http://www.somewhere.com/products/502/order which could map to the real webware URL of http:://www.somewhere.com/order.psp?productid=502 The main reason we switched to this was actually for search engines, as they tend to ignore query strings, and our customers would prefer that every product gets hit. I imagine Amazon's reasons would be similar. I'm not sure at all how I would tell Webware to do this stuff. In my mind the purpose is to remove restraints of the underlying technical solution (what Webware pages do what processing), which mod_rewrite is perfectly suited for. Luke ===== ------------------ Reference Counting Garbage Collection: Look out philosophy majors, things really DO cease to exist when no one is looking at them! ------------------ __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
