From: Julian Fitzell <julian@...4.com>
Date: 2004-05-08T11:57:26+09:00
Subject: Re: Differences between Iowa and Borges; was Re: What is Borges?

Kirk Haines wrote:
> * Iowa uses a template type architecture using plain HTML. Borges generates 
> the HTML programatically using an API to describe the content and a renderer 
> to take that description and turn it into appropriate content (which means 
> that the same Borges application could, in theory, generate HTML or run from 
> command line or generate a Fox GUI).

This is only because we haven't implemented a templating layer in 
Seaside.  There is a templeting system called Nori written by Colin 
Putney for Seaside, so it can be done.

> * Iowa has full access to the HTTP headers that are received and that are to 
> be sent back to the browser, making it easy to use cookies, set content 
> types, and that sort of thing, where needed.  I don't know about 
> Borges/Seaside on this one?

Seaside does as well.  We don't pass the server's request object in 
directly because we want an abstraction there, but we do have a request 
object that is accessible.

> * They are both pretty neat, even though they really have more differences 
> than similarities.  Borges definitely pushes the innovation envelope more 
> than Iowa does.  Iowa is more conventional.

I don't know about conventional.  But Seaside *is* the successor to 
Iowa, so it's hardly surprising that Seaside pushes the envelope more.