On Tue, 8 Mar 2005 12:10:28 +0100, Micha Schopman <[EMAIL PROTECTED]> wrote: > Scott, > > There is not a specific type of application, it is more the use of leveraging > DOM in combination with JavaScript. > > I showed you a small teaser from an upcoming CMS, using a rich interface. > That interface is build up with JavaScript. Each menu, treeview, and table > consists out of OO JS, which provides sorting, drag n drop, on demand > loading, single paged interface, etc, etc. Then we also have a layered > presentation model, also entirely based on Javascript, with ui persistency > layers, reusable scripting etc.
Cool, did something similiar in early 2002ish, CMS ..heh had it "publish" pages using DHTML and 8 frames...(ie XMLHttpRequest would of been great!) and cf would generate HTML files... had everyone going OoOOOoooo how'd ya do that progress bar!... > In general this interface is about 85% javascript and only 15% initial XHTML > markup code. Even though a full refresh only leaks 50kb, an amount which is > very normal regarding references to DOM. Will you notice this in terms of > speed of the application, NO. > > Garbage collection is always a topic, whether you use Java, JavaScript, .NET, > Actionscript; The way memory is released, if you have closed database > connections, or methods of optimizing memory usage too prevent long and > painful GC flushes. Managed languages never guarantee optimal use and release > of memory. In theory they should, but in practice that is not reachable > because there are too many complex parameters involved. Yeah, i've noticed it on and off, sometimes with Coldfusion it can be a pain - ie we can delete an objects key reference but not the actual object itself (there is a way to do this using java but Sean & Co have highly recommended not to do that hehe). I guess in the end, you could write defensive DHTML until you're satisified that the memory is managed yet : - what are teh chances of a user leaving the same browser instance open for post 50mb anyway? realistically if a user were using the same IE session for say 4-8 hours? even then a typical application would really have to be pushing it to go past 50mb? - what are we doing in the end? in that i've not yet seen some actual live - in the wild - applications that have cried a foul due to Memory Leak issues? I'm yet to be convinced it is an actual wide-spread problem? (I am easily convinced too) - IE 7 is on the horizon, while its probably years away from actual takeups - yet i personally wonder as to constricting the development to using var x = y, x.dosomething, x = null & unload style tricks / hacks around the bug really worthwhile post IE 6? - I'm really yet to even see FireFox suck the memory down with a DHTML app, and will be flawed to see that happen ... I present these points not as a forced opinion down all throats, more as of a "this is whats nagging away at me for the cons of memory leak management in JS - please feel free to refute / shoot down as i hate that feeling like i'm about to pioneer something or take a technical leap of faith.... (Not saying i'm the first but hopefully you get my meaning) Newho - bed time. -- Regards, Scott Barnes http://www.mossyblog.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:197810 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
