ML> Out of curiosity, if we were to web-enable Maximus what 
 ML> would be the best design approach ?

 PK> I doubt it would be practical or worth doing this, as 
 PK> the basis for Maximus is interaction with the user, 
 PK> which is easily handled by stock Web servers and some 
 PK> form of custom scripting. The hard part would be 
 PK> resource access (Message and File areas), just how do 
 PK> you want to store the data... Perhps some form of SQL 
 PK> would be the way to go for the message base...

Yeah. Maintaining access control across menus and functions would be
interesting. An EleBBS maintainer suggested exporting ACLs to cookies.

It wouldn't be too hard to access and export existing squish messages by
looking at how MaxED or TimeED does it. The rest can be done with web
forms. There're probably existing tools that do all of this.

 PK> Unless you really wish to retain the look and feel of 
 PK> Maximus, when Telnet serves you fine.

I'm seeking to extend Maximus's functionality and accessibility for when
telnet is unavailable eg. when blocked behind a company firewall, or java
applets thwarted by browser security settings.

The convenience of accessing your own BBS from a web browser is a worthwhile pursuit.

I'm sure it'd involve a messy hack job unless Maximus is rewritten, and I'm
not prepared to embark on that (yet). I'm still figuring out the make
files. :)

This is a long term endeavour. As such I might have a release by 2020 :)
Might as well brainstorm in the meantime.


--- Maximus/2 3.01