Hey Rickard,
> > > Say that cash register 1 and 2 at the same time scans a jBoss box,
> > > instanciates a MySession which will call the
> findByPrimaryKey for the
> > > jBoss item to get price/description. Will there be 1 or 2
> instances of
> > > the jBoss item?
> >
> > One.
>
> Exactly, although note that this is an implementation detail of the
> default cache. There is nothing that prevents us from adding an
> alternative implementation that utilizes multiple instances
> concurrently.
Yes. In this case the DB handles the transaction concurrency, right ? (But
only for commits B and C)
And the container must anyway synchronize the state of the beans (for commit
option A and for concurrency on same Tx, since commits B and C will be
handled by the DB), so that if I change something in one instance, then I
must update the state of all the other instances, am I right ? Not simple at
a first glance; well to me it seems more complicated than the current
pessimistic one :).
> In fact, if any of you have a great desire for one, and have a basic
> understanding for how to construct one, please do.
Mmmhhh. Sounds like *you* have a great desire for that :)
It is really needed ? Will give a real plus or it will be a "work that
doesn't bring bread home" (Italian saying for a heavy effort that pays
little :) ?
Regards,
Simon
> /Rickard
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
