> Regardless of the solution we use, we should abstract the creation of > the url so one can replace it with its own implementation.
+1 an abstract *layer* sounds good +1 for tinyurl like urls! -Matthias > I see three types of them: > > *) plain - pass through (so hackable) > *) encryption (leads to become too large for a GET) > *) leases - I have done this in one of my projects. The user is able to > bookmark a page but only gets a lease-ID. The server stores the correct > url for this lease (something like tinyurl) - not hackable, repeatable, > and no size limit - we just need a parameter to let a lease die if not > used for a couple of month > > > --- > Mario > > -- Matthias Wessendorf Zülpicher Wall 12, 239 50674 Köln http://www.wessendorf.net mwessendorf-at-gmail-dot-com
