On Fri, 16 Feb 2001, you wrote:
> > But why not just expose everything to the outside world? What if the developer
> > _wants_ to expose all of the classes?
>
> Could also ask: What if the developer
> does _not_ want to expose all of the
> classes?
> Bean implementation can contain
> trade secrets that clients should not
> have access to.
In that case it would be the bean deployer's job to protect his trade secrets,
not the container developer's job to prevent anything useful being done to
protect a few, surely.
[snip]
> But any clients that have already
> downloaded interface classes that
> are changed will have to be restarted
> anyway.
> If we are lucky, these clients just
> crash, but they might not.
> Consider the following remote
> interface change that will not make
> clients crash:
> << /** Set time in seconds. */
> << void setTime(int seconds)
> --
> >> /** Set time in milliseconds. */
> >> void setTime(int millis)
Well, if you were using hot-redeploy in a deployment, then yes, I think that
would be a problem. My inclination would always be to have scheduled downtime
for an upgrade, though, rather than just do a hot re-deploy. What if your
re-deploy somehow crashes the server? You should have tested it first, but it
might... Then your boss calls you up and chews you out for the server going
down when it wasn't meant to. Much prefer telling everyone it's going to go
down late one night than to send it down and knock a few hundred clients off...
Tom
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
