--- In [email protected], "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > We are working on improving the ability to do these types of > "master/detail" relationships in future LC DS versions with a single > destination. Using one destination is obviously how you'd like to do > it but you do run into some performance problems for large collections > and object graphs with how it is implemented today. In the future > we'll have additional metadata to specify on association properties (at > least) which let you specify one or more properties are unfetched until > the client tries to access them. >
That is great! I can't wait to see next LC DS version. > > > I take it you are turning off auto-sync so you can use the "paged fill" > stuff -i.e. the fill methods which return a page at a time? (We hope > to also remove that limitation in the next release as well). > Yes, that is exactly why i turned off auto-sync. I saw in an archive post that in future DS version it will by possible to auto-sync paged fill (one more feature I'm looking forward to :) > > > The simple answer for keeping data between two destinations in sync is > that in your assembler's updateItem method for one destination you use > the DataServiceTransaction.updateItem method for the other destination > (or similarly for createItem and deleteItem) > > > But when auto-sync is turned off, clients using that destination won't > receive those pushed changes. You can however use manual > synchronization. Clients can subscribe to one or more subtopics or use > a selector expression which specifies which messages they want to > receive. Clients or server code which publishes changes can specify > which subtopics those messages go to. > > Thanks! I will try to do this like that. Gabriel
