« Back to Extension Mobility API Questions

User and Device Query

Combination View Flat View Tree View
Threads [ Previous | Next ]
User and Device Query
Answer
2/4/09 11:13 PM
While using these queries, if a developer wants to find out the userid associated with multiple device (hypothetically speaking maybe 1000's of devices ), how long will it approximately take the API to return the result to the user ? Similarly if a user wants to know the device associated with multiple user id (hypothetically speaking huge number of user ids say 100's), how long will it take the API to return the result to the user.

The answers to these questions will help us determine whether we expose these APIs as synchronous or asynchronous methods in our Application.

Thanks,
Gaurav
Flag

Re: User and Device Query
Answer
2/5/09 2:39 AM as a reply to Gaurav Sandhir.
There are no published performance numbers on this that I'm aware of. You may be misunderstanding the function of the Extension Mobility APIs however:

  • User Query returns the CM user currently logged into the specified device. This should only be one record
  • Device query returns the devices(s) that the specified user is currently logged into. This could be more than one, but in reality I wouldn't expect it to be more than a handful
Flag

Re: User and Device Query
Answer
2/5/09 3:10 AM as a reply to Gaurav Sandhir.
Thanks for the reply.

If I understand correctly, the UserQuery API will accept multiple devices in the request, so it is possible that an application may send a bulk request for multiple devices. Similiarly an application may chose to do a device query for multiple users. Does that sound correct ?

Thanks,
Gaurav
Flag

RE: Re: User and Device Query
Answer
1/22/10 8:00 PM as a reply to Gaurav Sandhir.
Yes the assumption about multiple id's in a batch is correct.
 
The performance is dependant on your network, db size and server capacity. So the only way to find out for your customer is to test it in his network. Write a script that runs 100 requests and measure the time. Based on the outcome decide to wrap it as sync or async.
 
 
 
Flag