So I may have muddied the waters here mentioning the UI & the forms.  Let 
us focus on sending the entire database to an external system.

The two systems share the same entity structure (we both reference the same 
project in visual studio).  The reason my process has to send the entire 
dataset to the 2nd process is that it won't have access to the database 
file; also note, that even if the other process was allowed to read the 
database,  there will be un-committed changes that we need to transmit so 
that the 2nd process can visualize the effects of the proposed changes.

So to answer some of your questions:

   - 150K total rows need to be loaded; some tables have a couple hundred 
   rows, others have thousands, one even has nearly 100K (this will probably 
   always be our largest table).
   - The entire object graph needs to be serialized the first time the 
   entity is opened in the application. ***the startup time is the primary 
   focus right now
   - We haven't addressed sending changes; right now it is just sending the 
   whole thing again.  The features that utilize this are mostly still under 
   development so this hasn't become a critical issue yet.
   - Data is not being eagerly loaded because how long it takes to load the 
   entire object graph.

The reason there is so much data to send is because we are doing some 
mapping things and so their are a lot of "things" that have to be rendered 
and in the appropriate order based upon parent references to other entities 
and so on and so forth.  When the entity is first loaded we render the 
existing data in the 2nd process. When a user proposes a change in the UI 
we render a preview in the 2nd process; we don't commit it to the database 
because the user can still cancel/undo the change.

I only came on to the project recently after they had designed some of 
these architectural types of things, so I have been trying to make it work 
within those confines. I am getting the feeling from your perspective that 
we may have been going about things wrong.

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/nhusers?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to