From: sera@... (Francis Hwang)
Date: 2004-05-08T13:03:56+09:00
Subject: Re: What is Borges?

Julian Fitzell <julian@beta4.com> wrote in message news:<409C0C0E.6040002@beta4.com>...> 
> > - Can it work with mod_fastcgi/ruby?
> > - Does the sessioning stuff support automatic fallback to GET-based 
> > session ID propagation if the user has disabled cookies?
> 
> Seaside/Borges use GET parameters for session.  Avi and I do not like 
> using cookies for session keys, not just because of the obvious problem 
> that some people disable cookies but also because it prevents the user 
> from having two windows open in two different sessions at the same time.
> 
> It wouldn't be hard at all to support cookie-based session keys 
> instead--just a simple matter of programming--but we have no desire to 
> have such a feature.  We have had clients express interest, though, so 
> if it was something that somebody really wanted, we would probably 
> consider adding it (to seaside, that is).

What does a session imply here? Is there any room in this paradigm for
reflecting some state in a cookie and some state in a URL?

Let's say I'm selling some of my old CDs online, using a site that
uses cookies for login. And I want to reprice them by opening up a
bunch of tabs in my browser, which all might point to URLs like

http://my.site.com/reprice.rb?item=8787
http://my.site.com/reprice.rb?item=8788
http://my.site.com/reprice.rb?item=8789
http://my.site.com/reprice.rb?item=8790

There are two types of state here: The logic information keyed to a
cookie, and the item information keyed in the URL. Is this the sort of
thing that could be done in Borges?

From seeing the presentation at RubyConf last year it seemed very
impressive to me, but at the same time I had reservations because it
seemed like URLs that are so dependent on state would heavily resist
bookmarking ... are those reservations fair?

Francis