--rErXCrER28iYcLtG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Kirk Haines (khaines / enigo.com) wrote:

> > 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?
> 
> Not exactly the way that you show.  *ponder*  Hmm, Eric, how would you
> do this with Borges?
> 
> With Iowa, if one expected that someone would want to do this, then
> one could create an entry point into the application mapping /reprice
> to the Reprice component, for example.  And the Reprice component
> would look for an item= parameter to get the item number.  This would
> let the application construct URLs like this:
> 
> http://my.site.com/reprice?item=8787
> http://my.site.com/reprice?item=8788

It would work nearly identically in Borges:

http://example.com/borges/reprice/8787 would take you to a reprice page
for item 8787, while http://example.com/borges/reprice would give you a
list of the items in your store.

-- 
Eric Hodel - drbrain / segment7.net - http://segment7.net
All messages signed with fingerprint:
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04


--rErXCrER28iYcLtG
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQFAndWsMypVHHlsnwQRAlMnAJ9e5bcRr25/KBpHGiJyAk35t1VE7QCfdRfw
ZEQ2XcxU+OZ3fyA3a0aeVpon
-----END PGP SIGNATURE-----

--rErXCrER28iYcLtG--