Design decision and implementation best practice question for custom client-server

Here are requirements of the one of the use cases. I think I know what to do, but I need advice on getting it correctly. Assume that there

will be tends of thousands of users.

INPUT:

Custom client will call the following API:

http://www.mydomain.com/api/users

OUTPUT:

(It can also be jason or properly formatted xml, but it doesn’t matter)

I’ll have a web application at this API which will fetch results from the following table that will have the following fields:

id, JID, name, email, status_id, last_offline, last_latitude, last_longitude

The JID field will be used to map this table and the jabber server data user table. I know that there has to be a process that will be

constantly updating the status_id (for jabber user’s online/offline status), last_offline, last_latitude, last_longitude fields of this

table.

Does that piece of code should reside in a component ?

If yes, then how should the client (or the jabber server) send that component (or plugin) the notifications of users getting online or

offline, and their ever changing latitude/longitude so that when next time the web API is called, it can return updated results ?

If not, what are other elegant options. Can anyone send me a sample openfire component code in java ?