Having dug a bit deeper this is the architecture I am considering. When starting out on a new system in unfamiliar territory one never knows how stable things are going to be, what gotchas there are around the corner and whether when you ramp up from test data to real data volumes things will fall apart. I would therefore really appreciate hearing from anyone that has a similar architecture running, or even one part of it.
Here it is then:
Browser >> Tier1 (Seaside and all app logic) >(via OperaORB-native)> Tier2 (Server Wrappers to named pipes) >(pipes)> ['C' Server Processes]
To date all I have done is the Seaside tutorial, got a test message from Tier1 (XP) to Tier2 (Linux) using OperaORB and run up some processes using OSProcess. It's not a lot to base an architecture on. I just have a gut feel it will go. I did have one complete lockup while I was playing with OperaORB, caused by user error but does give me a stability concern.
Thanks in advance for any responses.
Bob
*** Confidentiality Notice *** Proprietary/Confidential Information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply email.
squeak-dev@lists.squeakfoundation.org