LCDS appears to be stateful session on the server. This blog talks about a solution that stores state on the client instead.
Dmitry Serebrennikov's List: Flex lazy loading
-
-
Lazy loading and paging add some complexity to your application. Due to the asynchronous nature of RPC calls in Flex, it's hard to "hide" the fact that the data may not be available to a particular view.
-
One way around this is to design classes that provide an "asynchronous interface" to callers. Using this technique, all data is provided to callers via a call-back or listener mechanism, regardless of whether the data is actually available or not.
-
-
Sep 10, 09
Data synchronization using state on the client only (stateless server). Apparently LCDS uses a statefull server pattern.
Basic idea:
- RPC-based CRUD calls pushed to server
- server replies OK/FAIL synchronously
- client puts the modified object into a pending state
- server also sends async message with the updated object to all peer servers
- peer servers push the same message out to their connected clients
- clients compare the received object's type+id+version to what they have and update accordingly (same as LCDS)
- original client moves object out of PENDING state
If we don't care about stale data on some clients, this can be simplified further.-
But what if you need more than a single server? Cluster, you might say. Unfortunately, that doesn't really work at any serious scale.
-
-
1 - 4 of 4
20 items/page
List Comments
(0)
List Info
4 items | 3 visits