We use a similar principle, with a little more state checking being done,
but generally the same thing.
Thor HW
----- Original Message -----
From: "Dave Ford" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 16, 2000 6:57 PM
Subject: BMP: Checking for Dirty in ejbStore
> For BMP, is it standard practice to maintain some type of "isDirty"
> variable? This way, when ejbStore is called, one can check to see if the
> data has changed since the last ejbStore call.
>
> The Oriely EJB book has an example of BMP and it's ejbStore does not do
> this. Thus, one would think that the "isDirty" technique is not the norm.
On
> the other hand, based on the rapid fire calling of the ejbStore method by
> the container, it seems very ineficient to NOT do the "isDirty" thing.
>
> What are your opinions?
>
> Dave Ford
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
