John I went "stateless" with stateless RBOs and OPEN2 rather than OPEN method.
We were using Object Handles in Session Variables to hold connection handles. So once we lost those if we had stayed stateful then we would have had to use the REFRESH method to restore the state of objects when each page that needed them was invoked. We chose not to run stateful because the way the website was getting hits this would be a performance bottleneck downstream (and it did grow - A LOT!). So we ran stateless RBOs with OPEN2 method and instantiated connections on each invocation where needed. What did we need to keep? Well a fair amount of DATA - we put that in form fields, hidden fields, browser cookies, query strings etc... it was surprising how much we just didn't need. All the web pages were re-entrant (display / enter / change - ONE form for each form use on the WWW - modified by the method used to invoke it.). In the end stateless - while (maybe) not as fast as stateful with object handles let us achieve a few key things we needed: 1. Scalability 2. Able to use a web farm 3. Focused us on moving as much processing load from the backend to the web pages. (lightened the backend so maybe in the end was faster). It paid back big time for us (and the client) - and they have gone on to greater and better (RedBack) things since then. They must be one of - if not THE - biggest RedBack users worldwide. Regards JayJay -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Bullard Sent: 13 June 2007 13:40 To: [email protected] Subject: RE: [U2] RedBack Garbage Collection Thanks for the info; I had not heard this one before. All of the apps that I have written so far are quite small-scale and, although I do use session variables, I don't think they are affected by the conditions that you mentioned. However, we all know what will happen if I make the ASSumption that they will STAY small-scale; so I have to ask for my future work: What methodology do you use in place of session variables? John B. -----Original Message----- ... The problem is IIS itself: IIS Session Variables are thread-locked to the specific IIS thread on which they were instantiated. ... ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
