While I agree that the WebOS solution is overkill for the DynAPI. The
Loadpanel approach is not the most solid bridge to deliver dynamic (dynamic
being defined as 'dynamic server/client interaction') content. I think we
need to explore alternatives/improvements to the glue between the DynAPI and
the wealth of server-side power that exists out there.
JS is client. It performs best in that world. The server-side unlocks a
whole new world of "dynamics" that currently tend to funnel into very "dead"
client interfaces. That's what peaked my interest in the DynAPI in the
first place. I loath the limited realm that FLASH delivers along with its
pathetic CPU chewing rendering engine. I like the fact that the DynAPI
leaves options 100% open for me to pick and choose front-to-back delivery
platforms.
Currently loadpanel is probably the weakest link supporting the DynAPI
platform. But it is the "only" link we currently have to bridge between two
very different worlds. Fix and optimize it....,
then you will see magic...
The "art" of client side interface will meet the "fandango dance" of the
server-side apps and really enhance the overall forumla for developing and
delivering the web experiences of tomorrow.
Ray
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
