🚀 go-pugleaf

In article <9211151841.AA00343@intuitiveedge.com> monty@intuitiveedge.com  
(Montgomery Zukowski) writes:
> 
> 	Has anyone given much thought on how to split applications into a  
> core server and a user interface object?  

A more classical approach would be to put the core data model in a server  
process and have a UI-oriented client. The server publishes a central data  
object from which you can navigate to all the other data objects.  
Generally, one would avoid giving the data objects any knowledge of user  
interface specifics. 

This give you, firstly, the ability to have more than one client access  
the data model and, secondly, the potential to write clients for other  
platforms (if by some miracle we get compatible Distributed Object  
implementations on other platforms). However, taking these last leaps also  
puts you up against all sorts of standard database issues, like concurrent  
access, persistence, navigational activation, periodic passivation, etc.

Roger