Ok. You said you had an application, not an API. You're right that
you'd have to train developers in that situation or find another way
to do it.
On 3/26/08, Laurent Marchal <[EMAIL PROTECTED]> wrote:
> Yep the only problem is that users of the API will have to manually move
> objects between
Yep the only problem is that users of the API will have to manually move
objects between DataContexts, so they will have to know what to do.
I spend this whole day to rewrite the API and pass a datacontext for
every call.
So I let developers manage their datacontexts.
thanks.
Mike Kienenberg
Why not create a new DataContext when you need to do write operations?
On 3/25/08, Laurent Marchal <[EMAIL PROTECTED]> wrote:
> Hi all !
>
> I spent some time searching documentation about the thread-safety status
> of DataContext, i found some answers on this mailing list but i would
> like to
Hi all !
I spent some time searching documentation about the thread-safety status
of DataContext, i found some answers on this mailing list but i would
like to know some details :
I have a big application (Eclipse RCP based) which monitors a database,
so i have to poll the database each 10 s
