mgmtprotocol message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: [mgmtprotocol] Requirements, a bit belated
- From: Fred Carter <fhcarter@attbi.com>
- To: mgmtprotocol@lists.oasis-open.org
- Date: Tue, 20 Aug 2002 21:31:51 -0700
Title: Message
My requirements
revolve mostly around the the ability to alter the management system. As
the management of web services (as well as management as a web service) becomes
available, more of the management may involve content sensitive management
capabilities. Therefore,
1) Management messages can define changes to management (configuration of
management)
2) Configuration messages should be able to specify their targets in a manner
that is natural (web services might be specified by URL or WSDL
file)
3) Configuration messages should include message content handling (the ability
to, say, add instrumentation based on message content)
4) Management may be active, and should include capabilities for defining "ping"
capabilities, etc.
5) Management infrastructure must not assume participation by or knowledge of
the target services.
6) Management must be ameliable to any services described by WSDL. (This
means that SOAP is not required.)
7) Configuration should be performed by messages, and not require restart or
other human intervention.
/fred
--
mailto:fhcarter@attbi.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC