Blogs

Showing 1 - 5 of 21 results.
Items per Page 5
of 5
First Previous Last

Forums

« Back to Extension Mobility API Questions

some questions that the documentation doesn't answer

Combination View Flat View Tree View
Threads [ Previous | Next ]
some questions that the documentation doesn't answer
Answer
3/1/10 1:33 PM
I recently rewrote my EM lib to be more object oriented (and while at it implemented the new operations that CCM8 offers). Looking at the DTD I noted a couple of things that I cannot explain:
 
What is the appEncryptedCertificate good for?
 
In logoutAll and logout there are two optional attributes remoteIPAddr and isViaHeaderSet. What are those good for?
 
Then exclusiveDuration... the documentation doesn't say what it does.
 
Then what's the checkUser operation good for?
 
Finally, the 8.01 documentation is ambiguous about the logoutAll operation:
 
According to what's new & changed, this logs out all users from all devices
 
According to the method description, "The LogoutAll operation logs out all the users from the device"..

but to the best of my knowledge, only one user can be logged in on any device... so what's the deviceName parameter in the example good for? And the example operation seems to be a logout request, not logoutall and the response... I think the response is what the request looks like and perhaps the response contains the list of devices that have been logged out.
 
Flag

RE: some questions that the documentation doesn't answer
Answer
3/2/10 1:40 AM as a reply to Stephan Steiner.
Hmm.. these are good questions emoticon
 
<exclusiveDuration> should be the length of the login period.  I.e. the user will be logged out automatically when this time expires.
 
The undocumented stuff in the DTD - appEncryptedCertificate/remoteIpAddr/isViaHeaderSet/checkUser - is probably vestigial, but I have a request into engineering to confirm and/or explicate.  We need to cleanup/update the DTD and docs here.
 
I do know that <logoutAll> is intended to logout all E/M users, and so should not have a deviceName paramter (this is borne out by the DTD.)  It definitely looks like the example in the doc is messed up.
Flag

Collateral


No files available