Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cis.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!cwlim!trier
From: trier@cwlim.INS.CWRU.Edu (Stephen C. Trier)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Terminal Emulator programming model
Message-ID: <1991May26.073607.12431@usenet.ins.cwru.edu>
Date: 26 May 91 07:36:07 GMT
References: <1991May16.101719.4369@rci.dk>
Sender: news@usenet.ins.cwru.edu
Reply-To: trier@po.CWRU.Edu
Distribution: comp.windows.ms.programmer
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 23
Nntp-Posting-Host: cwlim.ins.cwru.edu

Erik W. Jeppesen (ej@rci.dk) asks about multiple-session terminal emulators:
>What is the best programming model?
>	1. have one instance of the program for each session
>or
>	2. have one instance handle all sessions (one window per session)

I've been asking myself the same question.  I'd modify the list of questions
slightly, though:
    1. One instance of the program per session
    2. One program instance, one full-fledged window per session
    3. One program instance, one MDI child window per session

I decided that the MDI approach was out.  Although MDI would be cute,
it puts too many inherent limits on window placement.  I voted for one
instance for everything approach (option 2) -- It just feels better in
terms of memory usage and program efficiency.  I have no quantitative
data to back this up; it just seems to be a cleaner way to do things.

-- 
Stephen Trier                        Work: trier@ins.cwru.edu
Case Western Reserve University      Home: sct@seldon.clv.oh.us
Information Network Services