I'm totally fine with moving the default to pretty urls.
I don't want to take the steam off of this conversation, but while you're thinking about making urls pretty.. give a minute to thinking about simplifying the url space by merging PageService and ExternalService.. do we really need two different ways to access the page when they're essentially the same thing, just with or without parameters?
what are the pros and cons of treating every PageService request as an ExternalService request, but with a dummy activateExternalPage method.. (implemented in BasePage), or simply have ExternalService not throw an exception if the page doesn't implement IExternalPage, then ExternalService supports both regular pages and externalpages..
Alright, back to the conversation at hand, friendly urls by default is totally cool.
Brian K. Wallace wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been looking at the 'normal' use case and it appears as though Friendly URLs seem to be the 'preferred' method of displaying URLs. This being the case, would it not make more sense for Friendly URLs to be the 'default' for Tapestry? I am not proposing the removal of the ability to customize the way they are generated, only the default. In proposing this, however, I'm not proposing "true/false" for their enablement. Currently, when enabling Friendly URLs, the 'ugly' URLs are still available. I'd suggest three options: enabled, relaxed, and disabled. "enabled" (not backward compatible) would completely disable the ability to access the page/resources through the 'ugly' (original Tapestry) URL. In using ACEGI for path security, it's quite disturbing to get security enabled only to find access is open through the 'un-friendly' URL. "relaxed" (backward compatible) would present Friendly URLs by default, but 'ugly' URLs would still be accessible "disabled" (backward compatible) would present the original Tapestry URLs as it is now without the Friendly URLs. I'm still all for customization of the exact nature of the 'friendliness' (the current method of stating 'html' == page, 'direct' == direct, 'sdirect' == secure direct) such that users can specify what endings they want. I'm also searching for a message on the user list from quite a while ago that takes friendly URLs a step farther, but that's kind of outside the realm of this. Thoughts on this? (I don't see any value add for 'ugly' URLs, and if Friendly URLs were popular enough - and I must say they are to me with security external to Tapestry classes - can we not make it just a little easier to 'default' them?) Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEOzcGaCoPKRow/gARAv+fAKDJ/q0UPj5vG1gkg9vU92OXcZYIrwCfffMY IcchDDj58p91C/ZaLyJ8Q+Y= =JPra -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
