James WardThanks James for responding. Yes, I understand that Flex comes kind of from a different angle. A lot of the early Flex applications might have been used to show "real time" data, such as Stock tickers.
I don't see how I can do the same with BlazeDS.
Yes of course I can build a cache on the Flex side. But that is something that I would have to do in addition and also the life time of the objects in this cache could probably not be controlled by the server.
I therefore still believe that there's room for improvement for BlazeDS.
In a similiar response Stephen Beattie
Basically he says that BlazeDS is for "real time" data only. IMHO that is a major limitation, because I can't see a technical reason why BlazeDS could not support the HTTP caching infrastructure.
I want to be able to control from my server how long the data that was just send is valid, because the server for example might now that the data will only be updated once a day.