Hey

On Wed, 2 Aug 2000 10:28:44 -0400, James Cook <[EMAIL PROTECTED]> wrote:
>The risk of stale data is not so good for most of the apps I have written. I
>agree that you could put read-only data in a cache since it isn't going to
>change. I don't think developers have a lot of issues with that anyway. They
>can just mark their beans to use option a, or they can just use SLSB.

Yes, this is for read-mostly option A beans. As I belive I stated at the
beginning. No silver bullet, just a nice technique for a particular
case, that's all. (and I would !guess! that read-mostly option A beans
are "fairly" common in web-apps).

>The other thing that is not good with the approach is the amount of
>asynchronous messaging. That's a lot of extra traffic on the network. I
>would imagine that it would be a drain after a certain threshold of
>transactions are met.

Again, this is for read-mostly, so the amount of asynch messaging should
be fairly small. Nevertheless, if one uses a light-weight JMS
implementation, as I intend to do, the performance should be ok. I've
done some simple testing with RMI/JRMP and have been able to get a
throughput of 15000 messages per second with 200 clients talking to a
messaging server. That's ok for me.

>It would be interesting to see if the solution you presented would actually
>be faster in practice. I'm not so sure it would. And the risk of stale data
>shoots it down for many of us anyway.

Yes, it will be interesting to see :-)

>I think EJB needs a helper framework (not part of spec) to help in
>concurrency issues. Everyone still rolls their own, and I feel the majority
>of developers do not even realize the concurrency problems in their
>applications.

Agree 100%.

/Rickard

--
Rickard �berg

Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com

===========================================================================
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".

Reply via email to