I have a question pertaining to browser limitations with an app I have been working on with turbine
turbine has so far shown no problems rendering my screens even when loading very large amounts of data. my order entry screen loads all customers, suppliers and products and when rendered the screen runs about 800k (12000 lines) just in html and javascript. I was wondering if anyone has yet to hit any walls and at what point would I need to consider moving to a wizard type of input, breaking the entry point into multiple screens to reduce the single impact of loading all this data into one screen class. I've tested this large screen with both IE 6 and Mozilla 6 and both seem more than capable of handling it. I guess the real limitation is the clients physical ram and if you can wait long enough for the browser to parse such big files. even at this point of 12000 lines in one page, it only takes about 2 seconds to load running turbine off of an old PII with linux and 128 meg of ram and the client is roughly the same... i have only tested with about 10 users simultaneously and doesn't seem to affect performance noticeably at this point. your thoughts are appreciated and hearing other users experiences is always a Good Thing :) cheers, Jeff Painter [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
