ej@rci.dk (Erik W. Jeppesen) (05/16/91)
Hello, I would like some opinions from experienced windows programmers on the following subject: I am developing a terminal emulator that will use an int14 interface and support multiple concurrent sessions. What is the best program- ming model? 1. have one instance of the program for each session or 2. have one instance handle all sessions (one window per session) Any opinions on pros and cons regarding performance, memory usage etc. will be appreciated. Thanks in advance, Erik -- Erik W. Jeppesen ej@rci.dk +45 42 65 80 00 RC International, Lautrupbjerg 1, DK-2750 Ballerup, Denmark
trier@cwlim.INS.CWRU.Edu (Stephen C. Trier) (05/26/91)
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