This question is locked. New answers and comments are not allowed.
I'm new to this, just got through the reverse engineer and am studying the documentation. I want to use this ORM in a data-centric Web application binding the persistent objects to the UI controls. I need scaleability. This line in the OpenAccess ORM Disconnected API ( Programmers Guide ) threw me :
'But there are also application situations that do not allow a direct or a permanent database connection. Examples are Web applications and other asynchronous applications that still need .....'
I had concluded that ObjectScope was OK for a Web Application - with Optimistic Concurrency defaults I can't see a database connection which spans the UI interactions. Some of the code examples encouraged me by illustrating ObjectScope Transactions which included UI operations in their cope. I had also concluded that ObjectContainer was primarily for Web Services or portable applications.
Is the statement above saying that it is only appropriate for the DAL to give out the persistent objects in ObjectScope for Windows/Lan based applications ? with ObjectContainer essential for Web hosted applications?
Michael
'But there are also application situations that do not allow a direct or a permanent database connection. Examples are Web applications and other asynchronous applications that still need .....'
I had concluded that ObjectScope was OK for a Web Application - with Optimistic Concurrency defaults I can't see a database connection which spans the UI interactions. Some of the code examples encouraged me by illustrating ObjectScope Transactions which included UI operations in their cope. I had also concluded that ObjectContainer was primarily for Web Services or portable applications.
Is the statement above saying that it is only appropriate for the DAL to give out the persistent objects in ObjectScope for Windows/Lan based applications ? with ObjectContainer essential for Web hosted applications?
Michael