| Pakket | mx.data |
| Klasse | public class ManualSyncConfiguration |
| Overerving | ManualSyncConfiguration  Object |
| Taalversie: | ActionScript 3.0 |
| Productversie: | Adobe Digital Enterprise Platform Data Services for Java EE 3 |
| Runtimeversies: | Flash Player 9, AIR 1.1 |
autoSyncEnabled feature.
When autoSyncEnabled is true,
the server automatically routes messages by tracking
precisely which objects are being managed on each client. This is not a fully
scalable system as each server maintains a store of (at least) the ids of all
objects managed by its connected clients. Also, all data messages are routed
to all servers.
You can improve the efficiency of that process or restrict synchronizing of data by manually matching producers (either other clients or server code) and client consumers. LCDS provides a flexible mechanism for matching producers and consumers. You can either do this simply by matching topics published by producers and subscribed to by consumers. Each producer can specify a list of subtopics and each consumer can subscribe to a list of subtopics (note: delivery is always relative to the parent destination which can be considered the parent topic).
For advanced usage, producers send an arbitrary set of name/value pairs. Consumers subscribe using a selector expression (using JMS's selector language - similar to a primitive SQL where clause). Each message gets the producer's name/value pairs set as message headers. These headers are matched against the Consumer's selector expression on the server and only if there is a match is the message routed. You can use these mechanisms in combination as well.
Note that the manual sync configuration only routes changes to the client. The
client still must execute the fill(), getItem(),
or other method so that it has a place to receive
those changes. If a client receives a pushed message for an item which is not
managed on that client, it will be ignored. You can see the debug logging information
on the client to detect when this is happening. Also, the debug logging on the
server can be used to diagnose subscription problems on the server.
Overerfde openbare eigenschappen verbergen
Overerfde openbare eigenschappen weergeven| Eigenschap | Gedefinieerd door | ||
|---|---|---|---|
 | constructor : Object
Verwijzing naar het klasseobject of de constructorfunctie van een bepaalde objectinstantie. | Object | |
| Methode | Gedefinieerd door | ||
|---|---|---|---|
|
Geeft aan of voor een object een opgegeven eigenschap is gedefinieerd. | Object | |
|
Geeft aan of een instantie van de klasse Object zich in de prototypeketen van het object bevindt dat als parameter is opgegeven. | Object | |
|
Geeft aan of de opgegeven eigenschap bestaat en kan worden opgesomd. | Object | |
|
Stelt de beschikbaarheid van een dynamische eigenschap voor lusbewerkingen in. | Object | |
|
Geeft de tekenreeksweergave van dit object weer, geformatteerd volgens de locatiespecifieke conventies. | Object | |
|
Retourneert een tekenreeksrepresentatie van het opgegeven object. | Object | |
|
Retourneert de primitieve waarde van het opgegeven object. | Object | |
Wed Jun 13 2018, 11:42 AM Z