Re: httpmd

Dan Creswell wrote:

>> Remember though that you might have clients that still refer to an older
>> codebase annotation (same URI when not taking the message digest into
>> account) and that when they try to download the JAR file they will
>> assume it has been tampered with. This might not be a problem with your
>> usage of mobile code, but I've been bitten by that in the past.
>>
>
> Yep that's a possible gotcha.
>
> Client's could indeed still be running but perhaps in dev, Patrick is
> tearing them down anyways.

But often in larger scale development environments you don't want
to tear down everything with every code change as I found this to be a
major time-waster.

> Patrick, a basic approach to dealing with retirement of codebase
> annotations is to control/bound their spread and be aware of how many
> clients are using a service.  Note I'm being deliberately vague here as
> I have some interesting stuff in this area.

While thinking about these issues is very important at all times, still
I experienced the most robust environment is created by having
developers use tools that would lead to consistent dealing with
many issues they were not aware of or only when explicitly asked for. To
be honest how many people will (be able to) think of all the issues
set-out in the infamous paper of Michael Warres, at least I'm not.

Codebases tend to leak to places you only find out when the shit hits
the fan and they tend to make things more brittle than you would have
hoped for in the first place. Mobile code is a gift and a curse at the
same time.

>> Did you already look at some other frameworks than what is provided as
>> part of the JTSK that solve many of the problems you will encounter when
>> working with Jini, such as evolution of download JAR files (which is not
>> an easy and efficient task to do by hand)?
>
> :)
>
> Remembering that those frameworks potentially bring their own
> baggage/requirements with them which may or may not be "compatible" with
> the needs of the user.

I'm fully aware of that, and it is really up to the user whether it
works for his/her needs. Although I keep seeing a lot of questions
related to issues for which I think a lot of energy has been spent in
(partially) solving them. And for the sake that my existence on this
earth is not a total waste of energy I felt the need the point towards
other frameworks ;-)
--
Mark

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]