Are you passing both the incoming and outgoing message events to the
EventBroker? It sounds like you have an asymetrical configuration, which is
only getting you half of what you want.
Constantin
-Original Message-
From: Singh, Alok [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 22, 2006
Try:
In some implementations, the name of the element doesn't matter, but
you must have the namespace within.
> -Original Message-
> From: Bernino Lind [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 13, 2003 12:32 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
You'll probably want to use the 'jabber:iq:private' namespace in the
element, and your specific namespace (not to be preceded by
'jabber:') in the element within. See JEP-49
(http://www.jabber.org/jeps/jep-0049.html) for more information.
> -Original Message-
> From: Bernino Lind [mailto:
ge-
> From: David Sutton [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 14, 2003 9:18 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JDEV] MUC problems
>
>
> Hello,
>
> On Fri, Feb 14, 2003 at 08:26:05AM -0700, Constantin Nickonov wrote:
> > OK, I'll t
this instance, the user information is public and the
> implementation
> > returns each user's room JID (not a hash).
> >
> > If user information is *not* public, then the
> implementation SHOULD return
> > empty results, not hashed information, as in E
out coding in a room option that would
> allow people to disable the SHA hash jid if they really feel they
> have to. I just want to allow people to have that choice,
> rather than
> say 'I can't see a reason for it, so why bother' I also want to be
> able t
that although you currently see no reason
> for tracking
> this way, it is a function that I would like, and can see
> others needing in
> the future. This becomes especially true in cases of channel
> abuse, and for
> that reason alone I believe that the SHA hash representation
&
hen in it. If it's
non-anonymous, you have the real JID and don't need to complicate things
(which you've already conceded).
The two-phase browse seems like a good idea, i.e., get the in-room JID
from a room browse, and then dig deeper for the user's real JID by
browsing to
e
> '[EMAIL PROTECTED]/NICK' for the nickname reported
> by browse,
> the problem is that if users swap nicknames, I have no way
> of knowing
> that is what happened. The SHA1 string is unique to that user.
>
> Regards,
>
> David
>
> On Tue, Feb 11
see below
> -Original Message-
> From: David Sutton [mailto:[EMAIL PROTECTED]]
> Sent: Monday, February 10, 2003 8:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JDEV] MUC problems
> The hex string is actually a SHA1 hash of the users real jid. Its used
> to reference a user, but not rev
You could also make the 'thread' attribute hold more than one value (choose
your delimeter), i.e.,
root;parent;grandparent;etc
Since your client need only communicate with others like it, you can both
generate and make sense of this value at any point.
> -Original Message-
> From: Sea
It's entirely a client function. Jabber Instant Messenger (a free jabber.com
client) is an example of one that supports what you're trying to do, i.e.,
add contacts from search results.
Constantin
> -Original Message-
> From: Pete Birkinshaw [mailto:[EMAIL PROTECTED]]
> Sent: Monday, Jun
A bit off thread here... but registration and authentication are two
different actions, i.e., two different namespaces, two different JSM
modules, etc. Check the server config docs for more information.
---
> -Original Message-
> From: Riyaad Miller [mailto:[EMAIL PROTECTED]]
> Sent: Frid
This capability doesn't exist in the current version of the open source
groupchat service, but I know that Dave Waite is heading up a Jabber
Interest Group (JIG) with the goal of putting together a standard protocol
for doing that and more. If you're interested, you can get more info at the
Jabber
or probably a space between the two, i.e.,
> -Original Message-
>
> > Sent: usci_jabber
> >
> > Received: Invalid XML
>
> Maybe should be since
> doesn't have a starttag, and doesn't have
> a start tag.
>
> Wilbert
>
___
jdev mailing
Title:
Better
late than never... but, honestly, I send this reply a few days ago
:)
-Original Message-From:
Constantin Nickonov [mailto:[EMAIL PROTECTED]]Sent: Thursday, May
17, 2001 2:46 PMTo: '[EMAIL PROTECTED]'Subject: RE: [JDEV]
Getting a 404 trying to create a
Title:
Yes,
Jens, that is exactly how you do it using the old protocol.
---Constantin Nickonov
-Original Message-From: Jens Alfke
[mailto:[EMAIL PROTECTED]]Sent: Thursday, May 17, 2001 2:13
PMTo: [EMAIL PROTECTED]Subject: Re: [JDEV] Getting a 404
trying to create a chat room
Title:
Yes,
Jens, that is exactly how you do it using the old protocol.
---Constantin Nickonov
-Original Message-From: Jens Alfke
[mailto:[EMAIL PROTECTED]]Sent: Thursday, May 17, 2001 2:13
PMTo: [EMAIL PROTECTED]Subject: Re: [JDEV] Getting a 404
trying to create a chat
Title:
The
tag also comes into play with JUD, i.e., when there's
already an entry in the database. In such instances, the current entry is
also passed back to the client, who can choose to change it.
---Constantin Nickonov
-Original Message-From: Jens Alfke
[mailto:[
uests at it.
---
Constantin Nickonov
> -Original Message-
> From: Peter Saint-Andre [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 09, 2001 5:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JDEV] JUD docs?
>
>
> Hi Colin,
>
> There is no such doc at present.
Make sure that "jud.vkhdli08.hda.hydro.com" is resolvable, i.e., add it to
the 'hosts' file on the machine on which the Jabber server runs.
---
Constantin Nickonov
> -Original Message-
> From: Ørjan Sandland [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday
21 matches
Mail list logo
