Re: [Vrs-development] VRS and SEE/DEE goals

[Tim Terlegård]

> >  I guess it's the DEE that does all the
> > network job, making a
> > distributed system of SEEs.
>
> As far as I know, DEE does not address distributed
> precessing at all, except in the sense that a
> procedure's code can be downloaded from the central
> ASP server, as an explicir request, and locally
> executed.

I think it's time to get a discussion of DEE going. I thought some DotGNU 
members were here, but I guess I'll bring that discussion to the DotGNU list.


> > That's exactly what I have in mind.  The protocols
> > are plugins that layer over the functional parts.  I
> > think this may be anohter area where VRS and SEE
> > thinking have differed.

Then I think SEE is nuts  :-)


> > Hmm, sounds weird. Why not make the design in such a
> > way that it'll be easy
> > to add new protocols?
>
> Well, that's basically what we want to do.  Exactly
> how this is done has not been nailed down yet.  If you
> have some ideas, please throw them out.

You could take a brief look at my thesis which is titled "Design of a Secure 
Network Management System". Besides network management it also discusses 
mobile agents, security, Java middleware like Jini and Jiro and ends with a 
design of a network management system. I'm not sure if anything in the 
document is new to you, but you may look at it if you want. An idea of 
handling different protocols is discussed there. The idea is taken from JMX 
(Java Management Extensions). http://www.se.linux.org/~tim/thesis.pdf


-- Tim