[JDEV] Autoupdate

Jonathan Pobst jpobst at utk.edu
Tue Jul 16 12:03:06 CDT 2002


I think he meant how do you tell the server when a new version is available.
For the update.jabber.org, per my understanding, this was tied to
maintaining a record of your client on the JabberCentral.org website, and
telling it (via I assume a web interface), that a new version was available.
That record was then queried by the server agent on jabber.org and compared
to the version number the client sent in to see if a newer version was
available.

hope that helps,
pobst

-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
Sami Haahtinen
Sent: Tuesday, July 16, 2002 11:26 AM
To: jdev at jabber.org
Subject: Re: [JDEV] Autoupdate


On Tue, Jul 16, 2002 at 04:04:29AM -0400, Kriggs wrote:
> How does the server a client is connected to know that there is a new
version
> available? Does the server query some database when the client asks? From
> what I understand, the server DOES have something to do with this...

like Ben already explained, you can send a certain type of presence to
the agent, with my agent we use format like:

<iq to='client at update.ressukka.net/50'i type='get'>
  <query xmlns='jabber:iq:autoupdate'/>
</iq>

where client is the name of the client in question (which is marked to
the database) and 50 is the current version of the client. the server
will return new version(s) as a result to that query

ofcourse, this is the case with my agent, but the common idea is that
the client sends a request and tells it's current version with it. you
could also do it so that you trigger the agent to probe you, but just
telling the agent your version is the simplest and fastest way..

Sami

--
			  -< Sami Haahtinen >-
      -[ Notify immediately if you do not receive this message ]-
	-< 2209 3C53 D0FB 041C F7B1  F908 A9B6 F730 B83D 761C >-
_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev




More information about the JDev mailing list