Peter,
you wrote:
> What does this mean for applications that are mostly read-only?
> For example, a graphing application where a server side in-memory cache
> of DB data could be shared by many client processes? Assume that 99%
> of accesses are reads, but there are occasional updates. Do EJBs add
> any value to this scenario?
We ran into similar design problems with making essentially 'static' data
available to lots of clients (in our case servlets). EJB entity beans just
don't seem suited to this type of access (witness the long list of notes on
this topic recently). The spirit of EB are persistent domain object
instances that are transparently managed by whatever EJB container you
choose to purchase.
We built a 'Reference Data' framework (well before EJBs) that specifically
loads relatively static data objects and makes this available to clients via
Corba/Voyager/RMI. It can run embedded within your application or in an
entirely separate JVM. There are associated methods for flushing and
reloading the object cache, publishing the type of objects contained within
the cache, etc.
It would be nice to be able to keep all of this within the EJB world, if so
I'm interested in knowing how it might be implemented.
Mikef
========================================
Mike Fontenot - Object Systems Architect
Polygon Network, Inc.
Golden, CO
========================================
===========================================================================
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".
