StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In WCF RIA Services - you have to remember that their is a client side model that gets loaded first BEFORE the call back is issued. This client side model is NOT EF, but simply a rendering of what EF looks like on the server side. The WCF RIA Services call load this model first, before issuing the call back with a REFERENCE to the entities in the underlying model.</p> <p>I would encourage you to look at the Rx framework to leverage multiple async calls before returning to the UI client with "work done" mentally. Using Rx, you can call several async methods and wait for all to be completed before you return to the UI. Each call would load the client side model, in smaller bits, allowing the work to be done in parallel before returning. Remember, this is a SOA architecture, and it's easy (speaking to myself) to fall back into the design of blocking calls.</p> <p>(Task Parrallel Library (TPL) is also another way, but is making it's way into SL5. I'm not that familar with TPL and the nuances between when to use RX and/or TPL.)</p> <p>I've used this strategy to pull data down the hierarchtical tree of what data that I'm returning- first job is the upper level, then the lower level, etc. Remember that navigation properties on the client are nothing more than linq queries under the covers, where the primary key is used to filter on the foriegn key. The client side model (at this point it's not an EF model, but something close to it) also has referential integrity constraints, but these only apply when inserting records, not LOADING records.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload