Make your own free website on Tripod.com

Enterprise Project
About Enhydra Enterprise
Project Mail Lists
Working Groups
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Designers: Hello


good points - I've come to rely on external , usually JS, routines for most of
the heavy lifting in these areas.  This is especially helpful w/ XML handling.  I
hadn't meant to imply that F5 should be used to develop monolithic applications ,
but IMO it has advanced to the point that Flash UI components are viable within
the context of 'real" applications.

D

Jordan Duggan wrote:

> Dear Sir,
>
> Hello. Flash 5's native support for XML is definitely a leap forward, but
> here are a few definite considerations when implementing its use in
> applications. Flash has always been notoriously bad with memory management.
> In Flash 4 all variables were essentially global variables with no means
> what so ever of managing scope other than destroying the symbols which
> housed the variables off of the working area. Flash 5 improved memory
> management with the ability to create limited scope variables, but the
> overall memory space available is still pretty crummy. What this translates
> into is a very cramped computing space. This cramped space becomes apparent
> when trying to work with even moderately sized XML documents. Flash requires
> the entire XML document to be read in before you can perform any type of
> analysis or manipulation. Flash uses DOM parsing, which means any attempt to
> scan the entire document requires the creation of a set of nested "for"
> loops. This type of effort to get a high level view of what comes in seems
> like you've take all of the bad attributes of SAX and DOM parsing and put
> them into one really inefficient method of processing XML. It would be great
> if some sort of RPC or RMI system could be developed so that Flash could
> kick out a lightweight XML-RPC (http://www.xmlrpc.com/) and have all of the
> memory intensive scanning of larger XML documents be taken care of on the
> server as opposed to inside of flash's memory space. The result of the
> external scan could then be passed back in via another lightweight XML
> document.
>
> Love to keep talking, but have to run into a meeting. Look forward to more
> discussion.
>
> Jordan Duggan
> Chief Creative Officer
> Indicium Design
> Voice: 919-829-0650
> Cell: 919-696-7936
> Fax: 801-912-1503
>

-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe designers" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-designers@enhydra.org.