I'm running into a problem with sending messages directly to resources
which I think is related to case sensitivity, so I wanted to make sure
I am understanding the spec right.
Should [EMAIL PROTECTED]/Resource be the same as [EMAIL PROTECTED]/resource?
(This
is using ejabberd)
I switched
Thanks for the info. Will adjust my logic accordingly.
arne
On Dec 10, 2008, at 11:40 AM, Peter Saint-Andre wrote:
Peter Saint-Andre wrote:
Arne Claassen wrote:
I'm running into a problem with sending messages directly to
resources
which I think is related to case sensitivity, so I
Ok, cool. I was afraid that the ejabberd roundrobin meant that the
component instances wouldn't see all traffic. As i said, i need to do
a spike on components.
thanks!
arne
On Nov 25, 2008, at 8:54 AM, Jack Moffitt wrote:
Thanks for the info on components. I definitely need to read up a
Jack,
Thanks for the info on components. I definitely need to read up a bit
more on it. The only snag I see is that right now, I am taking
advantage of broadcast and resource affinity behavior of client bots
that can be achieved by sending to the jid with or without a resource
identifier.
One of my bot's roster is getting a bit large, so the roster request
is quite a chunk. I already persist the roster, so i'd rather just
query indivdual roster items on demand to query the subscription
state. Is there a modification to the roster IQ to ask for a single
jid? Can't find
Andy,
thanks for the reply.
On Oct 26, 2008, at 7:15 AM, Andreas Monitzer wrote:
I was the one who added XMPP forms support to libpurple (and thus,
pidgin and Adium), but I've never tested push-type forms. This may
simply be a limitation of my implementation, since I didn't consider
this to
I'm trying to determine whether XEP-0004 can be used by a bot to send
data forms to a client. I've tried a couple of things and none have
resulted in forms, but i don't know whether that is because of my lack
of understanding of the spec or lack of support in my clients (pidgin
and Adium)
