Hello all,
I recently ran into some problems using jabberd on an installation of Redhat
Linux 7.1. I found a workaround, although some may be able to find a better
solution.
Essentially, the problem was jabberd couldn't bind to ANY ports. The output
(when running "jabberd -h localhost"):
I think you idea is good, except for one thing. The IP address would be a
bad thing to broadcast like that, even if its just back to the offended (?)
client. The problem I see is this is a potential security risk, since we're
openly broadcasting the IP of someone using a service.
For me at leas
Title: RE: [JDEV] Multiple logins
I must
agree with Jens on this one, or at least partly: I think
clients need to auto-reconnect (at the user's preference), but
the libraries that clients are built on top of should
NOT attempt an auto-reconnect. Let the client code handle
an auto-reconnec
Hello all,
I am having some problems with jabberd (version 1.4.1). Specifically, I
cannot (for the life of me) get it to continue executing from within a
script. I will execute (from CLI):
jabberd -h localhost -H /usr/jabber/ -c /usr/jabber/jabber.xml &
And run just fine. But if I put this li
1 11:12 AM
To: [EMAIL PROTECTED]
Subject: Re: [JDEV] Probs w/ Jabberd 1.4.1 and Scripts
Got any debug output for us?
--temas
On Tue, May 29, 2001 at 08:52:42AM -0700, Matthew Miller wrote:
> Hello all,
>
> I am having some problems with jabberd (version 1.4.1). Specifically, I
> cann
OK, here it comes...
I have been working off-and-on on a distributed bug-tracking system. Now
that I am more familiar with Jabber's protocols (and now that I have an
"active" audience awaiting an actual system!), I am looking at using Jabber
for the messaging layer.
So, why send this around her
port it via
jabber to one (or more) JIDs for > analysis.
> > Is this the kind of
thing you're looking at, or are you thinking of >
something wider? > > Al.
> > - Original
Message - > From: "Matthew Miller"
<[EMAIL PROTECTED]> > To:
<[
#x27;
Subject: RE: [JDEV] Jabber - Scripting Language
I agree that something XML-related would be best. But I feel we need to
determine what the problem-set is before we settle on solutions.
Peter
On Thu, 7 Jun 2001, Matthew Miller wrote:
> Here's my $0.02...
>
> Jabber's pro
Here's my $0.02...
Jabber's protocol is described in XML, right? And there's currently
something called the Document Object Model, right? Which defines an
interface for events?
Although Jabber isn't a Document-centric environment, a DOM-like model (with
events) could be fairly easily defined,
(I apologize if this comes late, I receive the "digest" rather than being
swamped with e-mails...)
I'm mostly guessing here, but I believe the reason for a "running" XML
document is for the implicit connection status this provides. If the
document is still open (and there hasn't been an ungracef
Short Answer: "not really"
Long Answer:
The Jabber user ID (JID) (e.g. "[EMAIL PROTECTED]/work") is made up of three
parts: the username (linuxwolf), host (outer-planes.net), and the resource (work).
The username and resource are oft-times optional. The username and host is not case
sensit
11 matches
Mail list logo
