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
On Mon, 15 Jul 2002, Matthias Wimmer wrote:
> Hi David!
>
> David Waite wrote:
>
> > This (together with the 'jabber:server' / 'jabber:component:accept'
> > namespace usage) would be rather difficult to fix at this point
> > without breaking interoperability with nearly every client, server,
Any info you could give us on the hardware, the OS, the tweaks you had
to do the the OS?
Julian
Ryan Eatmon wrote:
>
> Just to let everyone know the good news, I just got a 1.4.2 server plus
> jadc2s up to 100k concurrent connections. And there was still room to
> go higher, I just ran out
Just to let everyone know the good news, I just got a 1.4.2 server plus
jadc2s up to 100k concurrent connections. And there was still room to
go higher, I just ran out of time and test boxes.
--
Ryan Eatmon [EMAIL PROTECTED]
---
Thanks for the explanation. Your point about message ordering is well
taken, I imagine many would complain if servers did not ensure ordered
arrival. I now understand the id tag is not really for pinning down
messages in the conversation but more as a client convenience. This sucks,
so since I'm
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 p
We are working towards bringing scalability and reliability to jabberd.
I am working on a document to describe our goals, and what is currently
available. I'm hoping that next week at the Open Source Conference I
can make time to bang on this. (Having a job sucks sometimes...)
Petr Ferschm
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
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 current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I think jabber.org server doesn't support that. May be jabber.com server may
be support that. But I am not sure.
All specifications says only about client <-> server and server <-> server
communication. So it is in your way to support that
Sean Wheeler wrote:
> foo barbar
> id=1 id=2 id=3
> thread=a thread=a thread=a
>
> It is unclear whether messages 2 or 3 are
> a reply to message 1 or not. The alternate
> approach is
Just use multiple threads. Each new message (which isn't a reply) has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
each connection should start with that:
http://etherx.jabber.org/streams";>
So I think is enough to implement virtual hosts/server pool.
Dne po 8. červenec 2002 22:10 Ian Littlewood napsal(a):
> I'm in the process of building a Jabber Server
On Sun, 14 Jul 2002, Sean Wheeler wrote:
> On Sun, 14 Jul 2002, Jeremy Nickurak wrote:
> >
> > The id attribute is intended to be used so that the sender and receiver
> > can refer to particular messages. For example, someone might implement a
> > "addendum" message type/namespace that changes som
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?? A
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.
Mich
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
So its a specially coded HTML page that can cause an attached virus to be
run without user notification in un-patched versions of Outlook and Outlook
Express. Klez and other similar viruses use the technique to help spread
themselves.
- Original Message -
From: "Dave" <[EMAIL PROTECTED]>
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
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.or
Hi David!
David Waite wrote:
> This (together with the 'jabber:server' / 'jabber:component:accept'
> namespace usage) would be rather difficult to fix at this point
> without breaking interoperability with nearly every client, server,
> and server component - many of these use custom parsers
20 matches
Mail list logo
