From: avi@...4.com (Avi Bryant)
Date: 2002-02-14T11:55:19+09:00
Subject: Re: IOWA troubles (was Re: choice of HTML templating system)

Thomas Hurst <tom.hurst@clara.net> wrote in message news:<20020213235732.GB41767@voi.aagh.net>...

> Well, the thing is, what's the point in serving content if the one
> way of specifying it's location is a meaningless jumble of characters?

I think you and Julian and are cross-purpose here - IOWA is intended
strictly
for web-based applications, not for serving content per se.  Desktop
applications don't have bookmarks or multiple entry points or sensible
named locations either.

> Well, concider I want to serve fairly static content

That's easy: don't use IOWA ;-).  There are lots of other, perhaps
more general solutions that have understandable URLs, but for what
IOWA wants to do (maintain state, lots of it, well) gibberish in the
URL line is a necessary evil.

> > If you really cared about the URI's you could probably have a frameset
> > with just one frame or something and put the iowa page in the frame.
> > Then browsers wouldn't show the URI changing, they just show the URI
> > of the frameset - I think.
> 
> Sorry, I'm afraid you're going to burn in the fiery pits of hell for all
> eternity for suggesting something 10x worse than messy URI's ;)

Seconded. :-)
Cheers,
Avi