Samuel Goto a écrit :
I would like to write it in C ...
i'm having sockets.h doutbs ... once i get a socket working,
everything else should be straightforward ( xml, protocol, etc )
since I wrote a client library ... I know that sockets should be easy
to do, but I am having problems with it (
I would like to write it in C ...
i'm having sockets.h doutbs ... once i get a socket working,
everything else should be straightforward ( xml, protocol, etc )
since I wrote a client library ... I know that sockets should be easy
to do, but I am having problems with it ( since it is a connection
Quoting Samuel Goto <[EMAIL PROTECTED]>:
Hello,
I am writing a new jabber component, and I was wondering if anyone
would have a good start point for writing it ... I read the jabber
component protocol, so I acctually need help on coding ( like using
libraries, tutorials, documents, sockets, e
Hello,
I am writing a new jabber component, and I was wondering if anyone
would have a good start point for writing it ... I read the jabber
component protocol, so I acctually need help on coding ( like using
libraries, tutorials, documents, sockets, etc ).
Any help is appreciated,
cya,
> In my previous post, I want to ask if I should let my codes do some
> checking after TLS negotiation and before SASL negotiation. Now my
> codes start SASL immediately after a successful TLS negotiation and
> this is what I understand from the XMPP spec.
You can't really assume that the client w
For Gaim, it sends registration related information (password etc.)
after a successful TLS negotiation, so the stream is protected, not in
cleartext I think.
In my previous post, I want to ask if I should let my codes do some
checking after TLS negotiation and before SASL negotiation. Now my
codes
Thanks, I did read this document. Apart from pretending a user, my
component does some component-specific things, so the choice of the
technology was right. But since it allows me to talk to IM gateways
and login under different user IDs to them, I wonder why not let a
component pretend to be a Ja
Hi Chen, Hao,
note that the XMPP spec does not know about jabber:iq:register. You can
read the RFC that after TLS negotiation you have to login using SASL.
But is it really what you want to enforce the client? Doing that would
mean you require the client to register for the new account using a
Hi Konstantin!
The problem with your approach is that as a component you always have to
send fully addressed stanzas including a source address. Your stanza is
missing the from attribute. The session manager would not be able to
send anything back to you.
From the log message I am assuming you
This is long, and it's early, so if it doesn't make sense, don't be
angry with me
You can do this if you write a component which creates and maintains
sessions.
I do this in 1.4.x for a web-based jabber client, where the webapp makes
a component connection to the server, and then brings sessi
I am implementing TLS and SASL for JiveMessenger. Gaim Jabber client
works very well with my new codes (for those registered account). But,
when I use Gaim to register a new account, I find that Gaim will send
registration information after a successful TLS negotiation, whereas
my codes are expecti
On Thu, Aug 18, 2005 at 11:42:09AM +0100, Richard Dobson wrote:
> Another solution you might want to look into is using the
> component protocol to connect to the server depending on what you
> are trying to do this might work for you:
> http://www.jabber.org/jeps/jep-0114.html
Thanks, I did read
I investigated a little bit more on the possibility for a component
to pretent to be a user. From a connected service, I tried to send
a regular jabber:iq:auth iq set packet. Whatever the packet looked
like, it was ignored by the Jabber server with the following log
message:
20050818T10:13:10: [w
I investigated a little bit more on the possibility for a component
to pretent to be a user. From a connected service, I tried to send
a regular jabber:iq:auth iq set packet. Whatever the packet looked
like, it was ignored by the Jabber server with the following log
message:
20050818T10:13:10: [wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alessandro Bottoni wrote:
> Which Python library would you use for developing a small Jabber client?
> pyxmpp (looks like the "official" python library)
> http://pyxmpp.jabberstudio.org/
This is the only python library I ever tried, and I had no prob
Hi,
> Which Python library would you use for developing a small Jabber client?
Twisted (http://twistedmatrix.com/) is also a very popular framework,
although not Jabber-only.
> pyxmpp (looks like the "official" python library)
As far as i know, there is no 'official' python library (nor one in
Which Python library would you use for developing a small Jabber client?
jabber.py (seems to be dead since 2003)
http://jabberpy.sourceforge.net/
pyxmpp (looks like the "official" python library)
http://pyxmpp.jabberstudio.org/
xmpp.py (a russian alternative. Very well documented and apparently
I'm just starting to develop Jabber-based apps and I'm looking for a good
book.
At Amazon's I found these 3 titles:
Jabber Developer's Handbook
By William Wright, Dana Moore
http://www.amazon.com/exec/obidos/ASIN/0672325365/qid=1124288642/sr=2-1/ref=pd_bbs_b_2_1/103-4249885-5594254
Programming
18 matches
Mail list logo
