Nick, We do something similar, have a look at COM+ object pooling (google/msdn). You can start up a configurable number of sessions (setting common) and call them from managed classes as required. When processing is quiescent for a set period of time, the sessions will close.
We're using this method to provide connectivity between our ASPX and BizTalk services back to UV. We don't have any patches (that I know of on uodotnet) and throughput is adequate (At least bettering the previous homebaked UV to UV socket transfer service we were previously running for speed, manageability and reliability). We have a "ping" process which returns a time from an initial ASPX call, opening or "activating" a session and calling a UV subroutine to the final genration of the response message. The first time takes 3-5 seconds, after that around 300ms. Also, I believe a future release of U2 will have support for session pooling built in. Regards, Stuart -----Original Message----- From: "Nick Cipollina" > The reason that our current processes are so fast is that we read as > much common data as humanly possible into memory at start-up so there is > little overhead while the process is running. If I have to call a > subroutine from .NET, that would actually slow processing down. I need > to get the data into .NET's memory to do something similar. ********************************************************************** This email message and any files transmitted with it are confidential and intended solely for the use of addressed recipient(s). If you have received this email in error please notify the Spotless IS Support Centre (+61 3 9269 7555) immediately, who will advise further action. This footnote also confirms that this email message has been scanned for the presence of computer related viruses. ********************************************************************** ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
