The parser I wrote for the JabberWookie library is SAX-like and will
execute the callbacks the moment the tag (opening or closing) is
complete. It was written w/Jabber in mind, so it has a few extra
callbacks that a normal SAX parser wouldn't, but I've used it for
general XML data just the
I want to develop Jabber Source and sink.
Jabber Source means the source application should register with Jabber server ([EMAIL
PROTECTED]) and should wait for the messages reaching at this id. And the sink
application is that it should forward the messages coming to a particular JID.
So which
How about clarifying your imperative and interrogatory? What do you want
to know? You still do not properly define the roles of your sink and
your source.
You could do /both/ all programs. It is trivial to rewrite attributes
on packets, send them on their merry way and also to listen for
Hi guy,
i am familiar with the terms source and sink, so i guess you are from
the computer science front :-)
i guess you want some sort of a robot forwarding from one jid to another
jid.
there is no program to do this (Someone can write it). you need to write
it your own.
ulrich
Tenny
I'm looking to implement a Jabber server (v1.x) supporting file transfers.
Are there any stable implemementations of JEP-0096?
(on a related note, does Jabber2 have jep-0096 functionality out of the
box?)
Thanks,
Dustin
_
Is your
JD,
Having intermediate callbacks is the main reason why people
use a SAX parser. So that is an implementation issue with
.NET's SAX parser.
Craig
On Fri, Mar 26, 2004 at 11:16:16PM -0800, JD Conley wrote:
Unfortunately the parser masquerading as SAX in the .NET Framework
doesn't work like
Hi, Tenny,
I think you have source and sink the wrong way around ;-)
A source application sends OUT information over particular namespace(s) - it
is the source of the information. A sink application draws IN data from
namespaces it is interested in (which could just be the namespace that is
On Saturday 27 March 2004 7:53 am, Dustin Sell wrote:
I'm looking to implement a Jabber server (v1.x) supporting file transfers.
v1.x of what? jabberd? There are many jabber servers, you know. :)
In any case, I don't know what you mean about a jabber server supporting file
transfers. If
Hey Justin, thanks for the reply... and sorry for being so ambiguous. Yes,
I was referring to jabberd v1.x.
I was originally looking into implementing a solution using JEP-0003 (PASS),
and then JEP-0065, but after looking into it some more, it appeared that
JEP-0096 was the modern way to go.
On Saturday 27 March 2004 4:20 pm, Dustin Sell wrote:
I was originally looking into implementing a solution using JEP-0003
(PASS), and then JEP-0065, but after looking into it some more, it appeared
that JEP-0096 was the modern way to go.
JEP-0096 is just a negotiation. JEP-0065 for actually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 27, 2004, at 5:45 PM, Justin Karneges wrote:
I'm running FreeBSD 4.4 on a VPS account -- I couldn't get Twisted
installed (which proxy65 relies on) and working correctly, so I
started
looking for another solution.
What issues did you encounter
11 matches
Mail list logo
