Apple Rackmounts

[Chris Bunch]

> for an interface driven app, which Frontier still
> is to a large extent, there's no substitute for working on the
> console

 Well, that's what I'd have said a year ago.

I have used all of Timbuktu, Radio, and WebEdit (usually behind Radio)
extensively over the past year or so. Gradually, I find I am using TB2 less
and less, and am relying 80% on WebEdit and 20% on Radio via the browser
button.

The functions I use TB2 for now tend to be the rare occasions when I decide
to change the name of the site, or somesuch, or (more usually) when I create
a new Manila site and the URL for the site somehow gets screwed up and I
need to do a global search and replace on the whole site. Even then (traffic
permitting) I could check out and check in the whole site via WebEdit if
need be and do that locally.

I have a remote server tucked away across town which I only rarely visit in
person: Frontier 7, Mac OS X. A headless daemon would be fine (easier to
control via SSH), and an XML-RPC to search and replace would be a killer.

C
___________________



> --Brian Hughes wrote:
>> That's a compelling reason to have a 'headless' version of Frontier
>> which runs as a daemon under a privileged user.
> 
> I would say yes and no to this. While I like the idea of being able
> to run Frontier the same way I can run MySQL and PostgreSQL, it's not
> really the same type of application. I find that there are all kinds
> of times when I want/need to work in Frontier's interface. You can
> proabably do 98% of that work via Timbuktu (which I'm not that
> familiar with), but for an interface driven app, which Frontier still
> is to a large extent, there's no substitute for working on the
> console.
> 
> -Brian
> 
>