From: Andreas N. <an...@kl...> - 2003-11-18 21:04:58
|
> Ok, good to hear. I was thinking about a three web server cluster connected > with a 1GB lan together, where server 1 operates as a lightweight reverse > proxy / static webserver / buffer for dynamic content, server 2 with lots of > memory serving dynamic content from the OI backend and server 3 as the mysql > database server with fast IO access. If I need load balancing I could add > more servers that generate dynamic content. This sounds reasonable. We use a setup, where both front and backend httpd are on the same host, because we thought the local throughput might be worth it. Also, since we serve multiple applications on this site, we wanted to be able to route some apps to special servers for processing - but this was never needed, except for debugging. We had some problems on the Oracle side ( now we replace Oracle ;-) ) > > I'm going to run several these kind of setups serving each up to 3000 users. Whoa - this is interesting and like lots of fun ;-) ... > More like 2.6 GHz P4 =) The speed problems I have had so far are about SPOPS > security checking when fetching lots of data and from several different > tables. Turning off object security and using handler security instead sure > speeds things a lot. Did you already try? > > > Since I am curious: what type of app are you thinking about ? > > What I have built so far is a school (student) management system. Some > screenshots here (shots in finnish, sorry): http://www.mimerdesk.org/RX/oi/ Although I did not understand a word ( only finish I know is from my stay in the US with 16 years of age, where a girl from Pori tought me minarakastanasinua ). We are thinking about a callcenter staffing tool ( only prototypes so far ), and this looks similar, but grown up. > > The next application I'm building at the moment is a collaborative learning > environment. You could compare such systems to groupware solutions to get an > idea how heavy the application will be. Sounds really interesting. > > These applications will be available under the GPL once we have the first > public versions ready. even better. We have problems making documentation good enough to publish some apps - time is to scarce... > > Special technical details are the XHTML interface with complete layout control > through CSS and modified OI themes. The templates we created for the XHTML > are very generic and allow object oriented approach to web interface design > (especially useful with some programmers who don't understand how to create > good user interfaces =) ). We have built an object oriented "Tool" library > which in the end outputs data structures to be passed for template toolkit, > which produces the resulting XHTML pages. The system allows creating web > pages through an object oriented interface similar to Tk/GTK etc. you use to > build desktop applications. No HTML or anything involved in creating the > interface. I`d like to see the results - sounds like a solid promising approach ! > > The benefit in the above example (see link) is that we didn't have to write > templates for any of the applications we created. We programmers used the > code to generate tools, the designers optimized the presentation. Everything > looks uniform. Once we had the interface framework ready we didn't have to > control layout at all or touch the templates. It was pretty nice to write a > new application and when you call $R->template->handler that's it. No > presentation to worry about. I like code that can be deleted, because some intelligent code does things behind the scenes! > > The disadvantage was that the number of TT templates used on each page was > relatively big (average was something like 100), so generating the page had a > slight performance hit despite the TT precompiling abilities. We decided to > heavily use OI page caching features. Still miss the ability to clear cache > for a different handler output. If you have enough RAM: the amount of cached TTs is tunable somewhere in the code. I think it was in OpenInteract::Template > > Another thing we are working on is a localization system that allows > translations to be stored separately. We probably use the standard unix > gettext and .po files for translations and hook that into OpenInteract. Just a note: there are ideas in OI2 for this. |