Splitting apps into UI and core server?

Thread View: comp.sys.next.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Montgomery Zukowski Sun, 15 Nov 1992 18:41

#1767

Author: Montgomery Zukowski
Date: Sun, 15 Nov 1992 18:41

16 lines
1347 bytes

	Has anyone given much thought on how to split applications into a  
core server and a user interface object?  Are there any examples on the  
archives?  I'm working on objects to support this right now but I don't want  
to re-invent the wheel.
	My approach right now is to split everything into two.  I have as  
classes DocumentManager and DocumentManagerUI, Document and DocumentUI,  
TextDoc and TextDocUI and a FileObject.  A lot of stuff will happen through  
delegation, like if a document is being saved for the first time and the file  
already exists, a Document would see if it has a UI delegate and if so a  
message would be sent and the DocumentUI would put up the alert panel and go  
from there.
	This approach involves a lot of cross talking and many classes where  
one used to suffice, but I'm not sure how else to go about it.
	Thoughts anyone?

Monty

Re: Splitting apps into UI and core server?

#1832

Author: Roger Rosner
Date: Wed, 18 Nov 1992 17:03

20 lines
1443 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads