Mark Taylor wrote:
> Alasdair Allan wrote: >> When a client registers with a Hub it gets its private-key back >> from the Hub. Should it also get it's public-key (ie the client- >> id)? Is there any circumstances where a client will need to know >> its own client-id? > > Currently undecided: see first part of the ISSUE: getHubID/ > getSelfID thread.
Okay. Another issue... looks like we might get tool kit issues,
In response to the following registration post,
<?xml version="1.0" encoding="UTF-8"?>
<methodCall>
<methodName>samp.hub.register</methodName>
<params>
<param><value><string>Nu3DwlDwMMbLVKqMNOVR</string></value></param>
</params>
</methodCall>
Which looks exactly like example method call from the specification. I get his back from the Perl XMLRPC server
<?xml version="1.0" encoding="UTF-8"?>
<methodResponse>
<params>
<param><value><string>registerResponse</string></value></param>
<param><value><string>pfFBQXMjYyns2</string></value></param>
</params>
</methodResponse>
rather than what you have in section 4.4 which doesn't have the
<param><value><string>registerResponse</string></value></param>
line included. Is what you have what is returned from a Java implementation? If so I think I've just run into our first toolkit issue... *sigh*
Al. Received on 2008-05-02Z13:28:00