Hello

i would to speak about the method choose by Strataframe , to use business object on the web.

If you use an Ipad or Android with sim card to access on the website app.

When you load a webpage , the session are stored in variable of session. If there are a micro cut network,
when the user write on the textbox.

The business object loose the variable of the session and the user loose his data,
cause the webpage reload , the binding refresh the textbox.

In php or ado.net, it's the same like a transaction , the data are send on the end, with the querie and the user don't depend the variable of session,
it's the DNA of the web data centric.

I don't know how the entity works because i use strata, but my policy is put to the challenge with my clients on my choice of strata.


Strata can work on the Winform with public variable, but in the web , the variable session can be kill by the network or the timeout, and the user want so to kill me.

I would like to know , if in the new version of strata with entities inherit, can be to change this way for me ?

Or If you see my problem and you can fix it ?

Can you help me to get an edit only when the user push validate button on the end of input his field ? do not depend a session variable ?

thanks for your help in advance.
Olivier


==============================================
Asp.net C# - Strataframe - telerik
==============================================

For the version 2.0

It's possible to modify variable session name with temporary name, and not the businessobject name inside.

Cause if we open 2 tab , with the same webpage, strata make a confusion with data, like a data session public in foxpro.

thanks
Olivier

==============================================
Asp.net C# - Strataframe - telerik
==============================================

Hello Trent

Thanks for the detail, the bottom line is that even SF V1 is all disconnected data.  It is how to manage that disconnected data and then update the server.  Regardless, SF V2 with the entity model will make this process easier and more seamless.  There are fewer hands in the cookie jar, so to speak.  Removing the ADO.NET component will also give a huge leg up.  

Thanks trent,