RE: [hyades-dev] Hyades Protocol Specification

["Barr, Dan" <Dan.Barr@xxxxxxxxxxxxx>]

Andy,

As a small example: when the layer 0 document was sent out for review, I had
no idea where you thought layer 0 would end and layer 1 would begin, etc. If
perhaps there was some sort of (moderately detailed) topology describing
what each layer would generally be responsible for. Sorta like the old "tell
them what you're going to tell them, tell them, then tell them what you told
them" when giving a presentation. This way, perhaps you'll get more feedback
on various pieces if people aren't waiting for what the "next piece" is
before providing feedback. Kinda like seeing the picture of the jigsaw
puzzle before you start putting together pieces.

The system agents would be a perfect example. If you had something which
provided a high-level view, and shared it, the feedback you get could be
more helpful to you as you go deeper.

-Dan


-----Original Message-----
From: hyades-dev-admin@xxxxxxxxxxx
[mailto:hyades-dev-admin@xxxxxxxxxxx]On Behalf Of Kaylor, Andrew
Sent: Monday, July 19, 2004 1:38 PM
To: hyades-dev@xxxxxxxxxxx
Subject: RE: [hyades-dev] Hyades Protocol Specification


Dan,

Actually, I don't know if there has been a document that does quite what
you're asking.  But then again, I'm not quite sure what you're asking.

The protocol document does make a lot of assumptions that we have a shared
idea about agents and what they're for.  Is that where the disconnect is
happening?  Or do you want a rough sketch of what some of the system agents
are?

-Andy

-----Original Message-----
From: hyades-dev-admin@xxxxxxxxxxx [mailto:hyades-dev-admin@xxxxxxxxxxx] On
Behalf Of Barr, Dan
Sent: Thursday, July 15, 2004 6:03 AM
To: hyades-dev@xxxxxxxxxxx
Subject: RE: [hyades-dev] Hyades Protocol Specification

Andy,

It might be helpful to have your high-level view of the interactions between
various players which would outline how things like the "system agent" might
work. Perhaps you posted this a long time ago and some of us never got it?
In any case, it might help focus comments on the appropriate piece when
providing feedback.

Just my 2¢...

-Dan

-----Original Message-----
From: hyades-dev-admin@xxxxxxxxxxx
[mailto:hyades-dev-admin@xxxxxxxxxxx]On Behalf Of Kaylor, Andrew
Sent: Wednesday, July 14, 2004 2:26 PM
To: hyades-dev@xxxxxxxxxxx
Subject: RE: [hyades-dev] Hyades Protocol Specification


Luc,

Thanks for your feedback.

Regarding the list of registered applications, I'd like to do away with
that whole concept.  Launching of applications is being moved out of the
HCE and into a system agent which exists for just such a purpose.  It is
my intention that this system agent will be able to launch any
application, not just those listed in a configuration file.

As I understand it, the list of registered applications was introduced
as a quick and easy security measure.  When we get rid of it, we'll need
to have "real" security in place.  That is still to be done.

-Andy

-----Original Message-----
From: hyades-dev-admin@xxxxxxxxxxx [mailto:hyades-dev-admin@xxxxxxxxxxx]
On Behalf Of Plaetinck, Luc
Sent: Tuesday, July 13, 2004 9:45 AM
To: 'hyades-dev@xxxxxxxxxxx'
Subject: [hyades-dev] Hyades Protocol Specification

First, a remark on Vishnu's document about the Hyades Collection Engine
Protocol Layer 2 - Agent Interface: 
- section 1.1.1.3.6: wouldn't it make sense to call this
CID_AGENT_STOP_MONITORING, in pairing with 1.1.1.3.2
CID_AGENT_START_MONITORING? CID_AGENT_STOP to me seems to be the
companion
of CID_AGENT_RUN

Now about Andrew Kaylor's "Hyades Protocol Specification" Revision 0.4:
The configuration for the HCE allows specification of applications that
can
be started up (ApplicationType). In the Layer 2 protocol there is the
Agent
Manager Interface, and an interface that deals with starting up
applications
(on the local or remote HCE). Is this interface specified/documented
yet? In
the current version of Hyades, there is no way to query the RAC (HCE)
for
the applications registered, which would be handy. Therefore I propose
adding a command CID_QUERY_AVAILABLE_APPLICATIONS which would return a
set
of Application Info blocks (see ApplicationType definition in the
config.xsd)

Regards,
Luc



The contents of this e-mail are intended for the named addressee only.
It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or
disclose
it to anyone else. If you received it in error please notify us
immediately
and then destroy it. 

_______________________________________________
hyades-dev mailing list
hyades-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/hyades-dev
_______________________________________________
hyades-dev mailing list
hyades-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/hyades-dev



The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it. 

_______________________________________________
hyades-dev mailing list
hyades-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/hyades-dev
_______________________________________________
hyades-dev mailing list
hyades-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/hyades-dev



The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.