Sim IJskes - QCG wrote:
On 10/07/2010 02:47 PM, Greg Trasuk wrote:
On Thu, 2010-10-07 at 05:36, Sim IJskes - QCG wrote:
Can somebody come up with a use case where it is absolutely necessary to
download code at runtime, where the effort of downloading it upfront is
so big compared to at runtime?
Gr. Sim
Smart proxies. Flexible protocols. Two services offering the same
interface, one of which uses JERI and one of which uses an in-memory
handler. Remote event listeners that do filtering on the "event
generator" side, and only go to the consumer if the consumer is really
interested in the event.
Thanks. But having preloaded smart proxies does not prohibit this, does it?
Do you deploy jini on the factory floor? How does that work in practice,
do you have a lot of sensors and actuators that you reset after a
software update? Or do you deploy a complete new codebase (in different
package combinations) over all the devices?
An factory floor with unified control over software upgrade timing for
the whole system, including all clients and servers, is the easy case.
That environment will probably also have unified control over virus
detection etc.
The more interesting problem is a long-running, 7/24, application that
uses Internet-accessible services provided by many different
organizations, each with their own, uncoordinated, upgrade schedule and
policies.
I thought the point of the Jini proxy system was to hide changes that do
not affect the interface, so that the application can, for example,
replace a service that has become unavailable or untrusted with a new
one that implements the same interface with minimal disruption.
Patricia
