Hi, Tuesday (10 August 2004)
Here are two problems that Harry Lewis identified in a phone call
last Friday:
(1) RegisterForManagement doesn't scale
- one for EVERY end legacy or WIMS agent
- not a reasonable model over the public Internet
(2) WIMS Manager can't request WIMS Proxy to do discovery
- makes WIMS Proxy installation much more difficult
Below are proposed solutions.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221 Grand Marais, MI 49839
phone: +1-906-494-2434
email: imcdonald@sharplabs.com
------------------------------------------------------------------------
(1) Add one new parameter to RegisterForManagement operation
RegisterForManagement (sourceURI : URI, targetURI : URI,
agentURIs : URI,
operations : WIMSOperationsSupported,
actions : WIMSActionsSupported,
objects : WIMSObjectsSupported)
statusString : StatusString,
operations : WIMSOperationsSupported,
actions : WIMSActionsSupported,
objects : WIMSObjectsSupported,
schedule : Schedule
Parameters:
agentURIs : xsd:anyURI
- URIs of the WIMS Agents or Legacy Agents currently managed by this
WIMS Proxy. These values MAY use the 'pwg-wims:' URL scheme and
MUST conform to [RFC2396].
Note: This parameter allows a WIMS Proxy to bundle multiple
registrations into a single operation sent to a WIMS Manager (for
scalability of the WIMS protocol to large networks).
(2) Define new DiscoverAgents WIMS action
DiscoverAgents (targetURI : URI,
parameters : any)
Description:
Discover legacy and WIMS agents visible to this WIMS Proxy, which
MUST include a list of the discovered Agent URIs in a subsequent
RegisterForManagement to the WIMS Manager identified in the Schedule
or ExecuteAction.
Parameters:
targetURI : xsd:anyURI
- URI of the WIMS Proxy to perform the discovery. This value MUST
use the 'pwg-wims:' URL scheme and MUST conform to [RFC2396].
parameters : pwg-sm:ActionElementAny
- Vendor extension parameters from any namespace.
This archive was generated by hypermail 2b29 : Tue Aug 10 2004 - 11:53:08 EDT