Re: [JDEV] autoupdate
Peter Saint-Andre wrote: > I can add something about this to the upcoming Jabber Client > Development Guide -- I'll chat with pgm about how he does it in > Exodus. > Peter Yeah, this just needs to be added to a doc someplace, that says "we reccomend using HTTP HEAD" to do this feature. Right now Exodus does both HTTP HEAD (for fetching daily builds) and the old school presence-hack-madness model. pgm. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] autoupdate
I can add something about this to the upcoming Jabber Client Development Guide -- I'll chat with pgm about how he does it in Exodus. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php On Mon, 7 Oct 2002, Thomas Muldowney wrote: > I'm not sure that's necessary, and potentially part of the problem. > Like Joe said, a HTTP HEAD works pretty good for them, and it's > drastically more simple than the old method =) Every case could > potentially have it's own method based on their server resources and > what not. > > --temas > > > On Mon, Oct 07, 2002 at 02:05:21AM +0100, Richard Dobson wrote: > > Then maybe what should be done is defining an informational standard > > for doing it so people starting out dont have to work it out themselves > > and have something to start from. > > > > Richard > > > > On Sunday, October 6, 2002, at 06:36 pm, Peter Saint-Andre wrote: > > > > >I second the motion. > > > > > >Peter > > > > > >-- > > >Peter Saint-Andre > > >Jabber Software Foundation > > >http://www.jabber.org/people/stpeter.php > > > > > >On Fri, 4 Oct 2002, Thomas Muldowney wrote: > > > > > >>The only reason I can remember was to have on central place to look > > >>at, > > >>but we quickly learned what a mess that is. I would say I'm in favor > > >>of > > >>people dealing with it themselves. > > >> > > >>--temas > > >> > > >> > > >>On Fri, Oct 04, 2002 at 01:00:24PM -0600, Joe Hildebrand wrote: > > >>>In Exodus, we've implemented both the (relatively lightly documented) > > >>>current way, as well as a simple HTTP HEAD. The HEAD approach seems > > >>>to work > > >>>pretty well... Can someone remind me of the reasons why the more > > >>>complex > > >>>protocol is necessary, since autoupdate is so similar to the HTTP > > >>>caching > > >>>problem? > > >>> > > >>>-- > > >>>Joe Hildebrand > > >>> > > >>> > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] autoupdate
I'm not sure that's necessary, and potentially part of the problem. Like Joe said, a HTTP HEAD works pretty good for them, and it's drastically more simple than the old method =) Every case could potentially have it's own method based on their server resources and what not. --temas On Mon, Oct 07, 2002 at 02:05:21AM +0100, Richard Dobson wrote: > Then maybe what should be done is defining an informational standard > for doing it so people starting out dont have to work it out themselves > and have something to start from. > > Richard > > On Sunday, October 6, 2002, at 06:36 pm, Peter Saint-Andre wrote: > > >I second the motion. > > > >Peter > > > >-- > >Peter Saint-Andre > >Jabber Software Foundation > >http://www.jabber.org/people/stpeter.php > > > >On Fri, 4 Oct 2002, Thomas Muldowney wrote: > > > >>The only reason I can remember was to have on central place to look > >>at, > >>but we quickly learned what a mess that is. I would say I'm in favor > >>of > >>people dealing with it themselves. > >> > >>--temas > >> > >> > >>On Fri, Oct 04, 2002 at 01:00:24PM -0600, Joe Hildebrand wrote: > >>>In Exodus, we've implemented both the (relatively lightly documented) > >>>current way, as well as a simple HTTP HEAD. The HEAD approach seems > >>>to work > >>>pretty well... Can someone remind me of the reasons why the more > >>>complex > >>>protocol is necessary, since autoupdate is so similar to the HTTP > >>>caching > >>>problem? > >>> > >>>-- > >>>Joe Hildebrand > >>> > >>> msg07259/pgp0.pgp Description: PGP signature
Re: [JDEV] autoupdate
Then maybe what should be done is defining an informational standard for doing it so people starting out dont have to work it out themselves and have something to start from. Richard On Sunday, October 6, 2002, at 06:36 pm, Peter Saint-Andre wrote: > I second the motion. > > Peter > > -- > Peter Saint-Andre > Jabber Software Foundation > http://www.jabber.org/people/stpeter.php > > On Fri, 4 Oct 2002, Thomas Muldowney wrote: > >> The only reason I can remember was to have on central place to look >> at, >> but we quickly learned what a mess that is. I would say I'm in favor >> of >> people dealing with it themselves. >> >> --temas >> >> >> On Fri, Oct 04, 2002 at 01:00:24PM -0600, Joe Hildebrand wrote: >>> In Exodus, we've implemented both the (relatively lightly documented) >>> current way, as well as a simple HTTP HEAD. The HEAD approach seems >>> to work >>> pretty well... Can someone remind me of the reasons why the more >>> complex >>> protocol is necessary, since autoupdate is so similar to the HTTP >>> caching >>> problem? >>> >>> -- >>> Joe Hildebrand >>> >>> >>>> -Original Message- >>>> From: Peter Saint-Andre [mailto:[EMAIL PROTECTED]] >>>> Sent: Thursday, October 03, 2002 11:09 PM >>>> To: [EMAIL PROTECTED] >>>> Subject: [JDEV] autoupdate >>>> >>>> >>>> Actually I was just about to ask someone for a JEP on that -- >>>> we need a >>>> real solution to the software update problem, not the current hacks. >>>> >>>> Peter >>>> >>>> -- >>>> Peter Saint-Andre >>>> Jabber Software Foundation >>>> http://www.jabber.org/people/stpeter.php >>>> >>>> On Thu, 3 Oct 2002 [EMAIL PROTECTED] wrote: >>>> >>>>>> And no - we have no way to make the fix a mandatory >>>> release. Are you >>>>>> offering to fix update.yabber.org so that it actually works? >>>>> >>>>> Opps, make that update.jabber.org that is broken... >>>>> >>>>> Michael. >>>> >>>> ___ >>>> jdev mailing list >>>> [EMAIL PROTECTED] >>>> http://mailman.jabber.org/listinfo/jdev >>>> >>> ___ >>> jdev mailing list >>> [EMAIL PROTECTED] >>> http://mailman.jabber.org/listinfo/jdev >> > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] autoupdate
I second the motion. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php On Fri, 4 Oct 2002, Thomas Muldowney wrote: > The only reason I can remember was to have on central place to look at, > but we quickly learned what a mess that is. I would say I'm in favor of > people dealing with it themselves. > > --temas > > > On Fri, Oct 04, 2002 at 01:00:24PM -0600, Joe Hildebrand wrote: > > In Exodus, we've implemented both the (relatively lightly documented) > > current way, as well as a simple HTTP HEAD. The HEAD approach seems to work > > pretty well... Can someone remind me of the reasons why the more complex > > protocol is necessary, since autoupdate is so similar to the HTTP caching > > problem? > > > > -- > > Joe Hildebrand > > > > > > > -Original Message- > > > From: Peter Saint-Andre [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, October 03, 2002 11:09 PM > > > To: [EMAIL PROTECTED] > > > Subject: [JDEV] autoupdate > > > > > > > > > Actually I was just about to ask someone for a JEP on that -- > > > we need a > > > real solution to the software update problem, not the current hacks. > > > > > > Peter > > > > > > -- > > > Peter Saint-Andre > > > Jabber Software Foundation > > > http://www.jabber.org/people/stpeter.php > > > > > > On Thu, 3 Oct 2002 [EMAIL PROTECTED] wrote: > > > > > > > > And no - we have no way to make the fix a mandatory > > > release. Are you > > > > > offering to fix update.yabber.org so that it actually works? > > > > > > > > Opps, make that update.jabber.org that is broken... > > > > > > > > Michael. > > > > > > ___ > > > jdev mailing list > > > [EMAIL PROTECTED] > > > http://mailman.jabber.org/listinfo/jdev > > > > > ___ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] autoupdate
The only reason I can remember was to have on central place to look at, but we quickly learned what a mess that is. I would say I'm in favor of people dealing with it themselves. --temas On Fri, Oct 04, 2002 at 01:00:24PM -0600, Joe Hildebrand wrote: > In Exodus, we've implemented both the (relatively lightly documented) > current way, as well as a simple HTTP HEAD. The HEAD approach seems to work > pretty well... Can someone remind me of the reasons why the more complex > protocol is necessary, since autoupdate is so similar to the HTTP caching > problem? > > -- > Joe Hildebrand > > > > -Original Message- > > From: Peter Saint-Andre [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, October 03, 2002 11:09 PM > > To: [EMAIL PROTECTED] > > Subject: [JDEV] autoupdate > > > > > > Actually I was just about to ask someone for a JEP on that -- > > we need a > > real solution to the software update problem, not the current hacks. > > > > Peter > > > > -- > > Peter Saint-Andre > > Jabber Software Foundation > > http://www.jabber.org/people/stpeter.php > > > > On Thu, 3 Oct 2002 [EMAIL PROTECTED] wrote: > > > > > > And no - we have no way to make the fix a mandatory > > release. Are you > > > > offering to fix update.yabber.org so that it actually works? > > > > > > Opps, make that update.jabber.org that is broken... > > > > > > Michael. > > > > ___ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev msg07240/pgp0.pgp Description: PGP signature
RE: [JDEV] autoupdate
In Exodus, we've implemented both the (relatively lightly documented) current way, as well as a simple HTTP HEAD. The HEAD approach seems to work pretty well... Can someone remind me of the reasons why the more complex protocol is necessary, since autoupdate is so similar to the HTTP caching problem? -- Joe Hildebrand > -Original Message- > From: Peter Saint-Andre [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 11:09 PM > To: [EMAIL PROTECTED] > Subject: [JDEV] autoupdate > > > Actually I was just about to ask someone for a JEP on that -- > we need a > real solution to the software update problem, not the current hacks. > > Peter > > -- > Peter Saint-Andre > Jabber Software Foundation > http://www.jabber.org/people/stpeter.php > > On Thu, 3 Oct 2002 [EMAIL PROTECTED] wrote: > > > > And no - we have no way to make the fix a mandatory > release. Are you > > > offering to fix update.yabber.org so that it actually works? > > > > Opps, make that update.jabber.org that is broken... > > > > Michael. > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] autoupdate
Actually I was just about to ask someone for a JEP on that -- we need a real solution to the software update problem, not the current hacks. Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.php On Thu, 3 Oct 2002 [EMAIL PROTECTED] wrote: > > And no - we have no way to make the fix a mandatory release. Are you > > offering to fix update.yabber.org so that it actually works? > > Opps, make that update.jabber.org that is broken... > > Michael. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
On Tue, Jul 16, 2002 at 09:39:05AM -0600, Ben Schumacher wrote: > It relies on S2S. The current autoupdate protocol (which could be cleaned > up a little) is designed so that clients send a presence packet with the > following format: > > > Where '1251235123' is a unique identifier, '0.1.2.3' is the current > version number, and update.jabber.org is (of course) the target host. If FWIW, there's some more background here: http://www.pipetree.com/jabber/update.html cheers dj ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
RE: [JDEV] Autoupdate
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Sami Haahtinen Sent: Tuesday, July 16, 2002 11:26 AM To: [EMAIL PROTECTED] 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: 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 [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
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: 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 [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
On Tue, 16 Jul 2002, 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... It relies on S2S. The current autoupdate protocol (which could be cleaned up a little) is designed so that clients send a presence packet with the following format: Where '1251235123' is a unique identifier, '0.1.2.3' is the current version number, and update.jabber.org is (of course) the target host. If your server doesn't have S2S configured, then autoupdate won't work. Cheers, bs. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
On July 16, 2002 02:02 am, you wrote: > On Mon, Jul 15, 2002 at 04:35:08PM -0400, Kriggs wrote: > > So it is the client's job to talk directly to the autoupdate service > > provider? > > yes, the autoupdate-agent has no way of knowing which clients are in use > everywhere in the world. > > also it is a much better thing to send the autoupdate request through > jabber than to poll a website or something, as the client has already > made it's connection to jabber server, you have less work and more > reliable way of passing on the request. Hmmm. Maybe I should ask my question a different way. 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... ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
On Mon, Jul 15, 2002 at 04:35:08PM -0400, Kriggs wrote: > So it is the client's job to talk directly to the autoupdate service provider? yes, the autoupdate-agent has no way of knowing which clients are in use everywhere in the world. also it is a much better thing to send the autoupdate request through jabber than to poll a website or something, as the client has already made it's connection to jabber server, you have less work and more reliable way of passing on the request. 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 [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
The plan is to get the Releases tool under jabberstudio.org to work and then I'll deploy a version of update-agent that will feed off that data. Thomas Muldowney wrote: >Ryan was looking at this interaction, he had a plan but the JS work has >been a speedy blur right now. Ryan what was the plan? > >--temas > > >On Mon, 2002-07-15 at 11:22, Peter Millard wrote: > > >>I think the hope is to incorporate the JabberStudio stuff back into the >>update.jabber.org agent. Temas?? Any plans/thoughts about this?? The >>JabberCentral stuff worked a long while ago, but it's been broke ever since >>JC was moved to another provider, and now sits behind a firewall. >> >>Peter M. >> >>Michael Brown wrote: >> >> >>>update.jabber.org *should* interact with the version numbers of >>>clients released on Jabbercentral.com I'm told, but alas it is >>>currently broken. :( >>> >>>Michael >>> >>> >>> >How do you get the whole network of servers to know if there is a >new version of your client? > > Each time the client starts up it should send a presence packet to an update server; this server will then send back a message if a newer version of the client software is available. Please see: http://docs.jabber.org/jpg/html/main.html#CH-AUTOUPDATE >>___ >>jdev mailing list >>[EMAIL PROTECTED] >>http://mailman.jabber.org/listinfo/jdev >> >> > > >___ >jdev mailing list >[EMAIL PROTECTED] >http://mailman.jabber.org/listinfo/jdev > > -- Ryan Eatmon [EMAIL PROTECTED] Jabber.org - Perl Teamjid:[EMAIL PROTECTED] ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
So it is the client's job to talk directly to the autoupdate service provider? -Kriggs ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
On Mon, Jul 15, 2002 at 11:40:31PM +1000, Michael Brown wrote: > update.jabber.org *should* interact with the version numbers of clients > released on Jabbercentral.com I'm told, but alas it is currently broken. :( i can also offer autoupdate service, i built one sometime back, and it is currently being used by rival v3 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 [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
Ryan was looking at this interaction, he had a plan but the JS work has been a speedy blur right now. Ryan what was the plan? --temas On Mon, 2002-07-15 at 11:22, Peter Millard wrote: > I think the hope is to incorporate the JabberStudio stuff back into the > update.jabber.org agent. Temas?? Any plans/thoughts about this?? The > JabberCentral stuff worked a long while ago, but it's been broke ever since > JC was moved to another provider, and now sits behind a firewall. > > Peter M. > > Michael Brown wrote: > > update.jabber.org *should* interact with the version numbers of > > clients released on Jabbercentral.com I'm told, but alas it is > > currently broken. :( > > > > Michael > > > >>> How do you get the whole network of servers to know if there is a > >>> new version of your client? > >> > >> Each time the client starts up it should send a presence packet to an > >> update server; this server will then send back a message if a newer > >> version of the client software is available. Please see: > >> > >> http://docs.jabber.org/jpg/html/main.html#CH-AUTOUPDATE > > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
I think the hope is to incorporate the JabberStudio stuff back into the update.jabber.org agent. Temas?? Any plans/thoughts about this?? The JabberCentral stuff worked a long while ago, but it's been broke ever since JC was moved to another provider, and now sits behind a firewall. Peter M. Michael Brown wrote: > update.jabber.org *should* interact with the version numbers of > clients released on Jabbercentral.com I'm told, but alas it is > currently broken. :( > > Michael > >>> How do you get the whole network of servers to know if there is a >>> new version of your client? >> >> Each time the client starts up it should send a presence packet to an >> update server; this server will then send back a message if a newer >> version of the client software is available. Please see: >> >> http://docs.jabber.org/jpg/html/main.html#CH-AUTOUPDATE ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
update.jabber.org *should* interact with the version numbers of clients released on Jabbercentral.com I'm told, but alas it is currently broken. :( Michael > > How do you get the whole network of servers to know if there is a new version > > of your client? > > Each time the client starts up it should send a presence packet to an > update server; this server will then send back a message if a newer > version of the client software is available. Please see: > > http://docs.jabber.org/jpg/html/main.html#CH-AUTOUPDATE ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Autoupdate
Kriggs wrote: > How do you get the whole network of servers to know if there is a new version > of your client? Each time the client starts up it should send a presence packet to an update server; this server will then send back a message if a newer version of the client software is available. Please see: http://docs.jabber.org/jpg/html/main.html#CH-AUTOUPDATE ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] Autoupdate
I have a question that's probably been asked many times before, so I apologize. But: How do you get the whole network of servers to know if there is a new version of your client? -Kriggs ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] AutoUpdate server
update.jabber.org is not currently up and running. This is a known issue, and one that I'm hoping I can find time to work on very very soon. Once it is back up and working, JabberCentral contains the frontend to the update.jabber.org database. Talk to justin about getting Yabber set up there for now. That said, we are also going to be working on update.jabebrstudio.org that will tie directly into JabberStudio and serve files based on your project there. Our hope is to make it a one stop project management site, but that might take longer to get. Michael Brown wrote: > Can anyone tell me if it is possible to get a client configured on the > jabber.org server such that the server will reply to my clients autoupdate > requests as documented here?: > >http://docs.jabber.org/jpg/html/main.html#CH-AUTOUPDATE > > Are any other clients using the jabber.org server in this way? It seems > like a great idea, but since we don't run a a server of our own, we need one > to point Yabber at. Also, how do you go about keeping the server up to date > with client version numbers? > > Thanks, > > Michael. > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] AutoUpdate server
Can anyone tell me if it is possible to get a client configured on the jabber.org server such that the server will reply to my clients autoupdate requests as documented here?: http://docs.jabber.org/jpg/html/main.html#CH-AUTOUPDATE Are any other clients using the jabber.org server in this way? It seems like a great idea, but since we don't run a a server of our own, we need one to point Yabber at. Also, how do you go about keeping the server up to date with client version numbers? Thanks, Michael. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] autoupdate feature
Right now the autoupdate feature is something of a hack (IMHO) and I feel we need a better framework for autoupdates (e.g., although the current one works, there is a central point of failure on update.jabber.org), especially one that doesn't use a hack to the presence element. You could certainly create your own mini-protocol for this, to be used just by your own client and server. Or perhaps some other folks here might want to collaborate on a better protocol and implementation for this... Peter On Sat, 1 Sep 2001, Michal Leinweber wrote: > I'm writting own client for Jabber and I want to use autoupdate feature. Are > there any servers providing autoupdate feature other than update.jabber.org? > Is there some framework to provide autoupdate feature on my own server? > Something that will receive autoupdate presence messages from clients and > look in some database of versions and sends answer to client ? Also I want > to track usage of my client, based on autoupdate queries to my server. > > Thanx for answer > McLEI > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] autoupdate feature
I'm writting own client for Jabber and I want to use autoupdate feature. Are there any servers providing autoupdate feature other than update.jabber.org? Is there some framework to provide autoupdate feature on my own server? Something that will receive autoupdate presence messages from clients and look in some database of versions and sends answer to client ? Also I want to track usage of my client, based on autoupdate queries to my server. Thanx for answer McLEI ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
