By kohlerm
via kohlerm.blogspot.com
Published: Aug 20 2008 / 14:32
BlazeDS is an open source remoting solution for accessing Java objects from Flex applications.
It claims to be efficient by using a binary protocol to send data of HTTP.
Unfortunately it currently has a major drawback, that will not allow it to scale well for a lot of applications.
SaveShareSend
Tags: flash-flex, java
Comments
YeFFreY replied ago:
Don't compare RIA application with basic html application...
Cache can be done locally...
Only data are needed, not all the html pages...
kohlerm replied ago:
IMHO the term RIA is pretty much undefined. Actually with "normal" web applications you can cache html, code and data (Json or XML for example).
BlazeDS does not support this.
See the follow up post :
http://kohlerm.blogspot.com/2008/08/blazeds-does-not-make-use-of-http.html
madarco replied ago:
The author state that BalzeDS won't scale because it doesn't use the http cache mechanism.
I don't see how this can be a problem, or can affect scaling.
If his problem is the client-side caching, he can do it easily in his client-logic.
kohlerm replied ago:
Hi madarco,
Off course it affects scaling, because it will do more requests. It's as simple as that.
Regarding client-side caching. How should the client know, how long the data is valid.
This is something that only the server knows. BlazeDS does not support sending this information to the client(together with the data).
There's also no "standard" caching library available with Flex, which supports stuff like eviction and replacement strategies.
Voters For This Link (4)
Voters Against This Link (8)