> -----Original Message----- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 31, 2006 12:04 PM > To: MyFaces Development > Subject: Re: Bookmarking, History and JSF > > Ok, I've discussed with Manfred and Thomas some more, and our personal > preference would be proposal 2 with (optional) encryption (or > signature, just so that the user can't temper with the URL).
Option 1 would also enable outside-applications to generate correct links and therefor can be attractive for corporations having lots of interacting web-apps.. > > regards, > > Martin > -----Original Message----- > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 31, 2006 12:06 PM > To: MyFaces Development > Subject: Re: Bookmarking, History and JSF > > Ok, I'll implement the interface, you the simple server store > implementation - is that a deal ;) ? Should be possible... > > By the way - any update on the optional validator stuff together with > partial validation? Ok, maybe we should start a different thread on > this ;) Sorry, am still setting me up again to continue work on the OV... But PV is one of the first things I want to check... So many loose ends to check and tie up ... regards Alexander > > regards, > > Martin > > On 1/31/06, Jesse Alexander (KBSA 21) > <[EMAIL PROTECTED]> wrote: > > > > > > > -----Original Message----- > > > From: Martin Marinschek [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, January 31, 2006 11:58 AM > > > To: MyFaces Development > > > Subject: Re: Bookmarking, History and JSF > > > > > > Yeah - but where do you store these tinyurls? On the server? > > > In a database? > > > > Offer an interface that can be implemented by a developer, allowing > > for DB-persistance, plus deliver a simple implementation using a > > file-store? > > > > regards > > Alexander > > > > > > > > +1 for making it configurable, -1 for making it the default ;) > > > > > > regards, > > > > > > Martin > > > > > > On 1/31/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > > > 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 > > > > > > > > > > > > > -- > > > > > > http://www.irian.at > > > > > > Your JSF powerhouse - > > > JSF Consulting, Development and > > > Courses in English and German > > > > > > Professional Support for Apache MyFaces > > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
