Menu
▾
▴
xmpppy-devel — Main place to discuss problems request features and to get support.
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(4) |
Feb
|
Mar
|
Apr
(5) |
May
(11) |
Jun
|
Jul
|
Aug
(7) |
Sep
(17) |
Oct
(4) |
Nov
(1) |
Dec
(10) |
| 2005 |
Jan
(9) |
Feb
(10) |
Mar
(3) |
Apr
(4) |
May
(12) |
Jun
(24) |
Jul
(22) |
Aug
(29) |
Sep
(74) |
Oct
(47) |
Nov
(25) |
Dec
(22) |
| 2006 |
Jan
(36) |
Feb
(9) |
Mar
(36) |
Apr
(33) |
May
(39) |
Jun
(9) |
Jul
(18) |
Aug
(18) |
Sep
(26) |
Oct
(48) |
Nov
(14) |
Dec
(9) |
| 2007 |
Jan
(10) |
Feb
(2) |
Mar
(9) |
Apr
(3) |
May
(9) |
Jun
|
Jul
(12) |
Aug
(20) |
Sep
|
Oct
(16) |
Nov
(4) |
Dec
(21) |
| 2008 |
Jan
(32) |
Feb
(11) |
Mar
(4) |
Apr
(13) |
May
(13) |
Jun
(16) |
Jul
(1) |
Aug
(8) |
Sep
(9) |
Oct
(23) |
Nov
(7) |
Dec
|
| 2009 |
Jan
(17) |
Feb
(11) |
Mar
(35) |
Apr
(10) |
May
(8) |
Jun
(14) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
(2) |
Nov
|
Dec
(5) |
| 2010 |
Jan
(15) |
Feb
(4) |
Mar
|
Apr
|
May
(5) |
Jun
(4) |
Jul
(3) |
Aug
(1) |
Sep
(10) |
Oct
(2) |
Nov
(8) |
Dec
(3) |
| 2011 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(4) |
Sep
|
Oct
|
Nov
(4) |
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
(5) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(1) |
Nov
(14) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(1) |
| 2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Norman R. <no...@ra...> - 2009-06-19 13:20:41
|
On Fri, Jun 19, 2009 at 2:43 PM, Will Siddall <wil...@gm...>wrote: > I pretty much took the xsend example and re-purposed it... but instead > of sending presence info or sending a message, I want to look for a > vcard but everytime it gets to the 'disp.plugin(cl)' line, it faults > with: > ahh, connect will create a dispatcher and plug it in for you, so you don't need to do that yourself. You can get the current instance like this: disp = cl.Dispatcher -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |
|
From: Will S. <wil...@gm...> - 2009-06-19 13:08:20
|
I pretty much took the xsend example and re-purposed it... but instead
of sending presence info or sending a message, I want to look for a
vcard but everytime it gets to the 'disp.plugin(cl)' line, it faults
with:
File "xmpp/client.py', line 88, in DEBUG
self._owner.DEBUG(self.DBG_LINE,text,severity)
AttributeError: Dispatcher instance has no attribute '_owner'
This is what I've got so far. I cut out the bit from the xsend example:
if len(sys.argv) < 2:
print "Syntax: %s JID"%sys.argv[0]
sys.exit(0)
tojid=sys.argv[1]
...
if not auth:
print 'could not authenticate!'
sys.exit()
print 'authenticated using',auth
print ''
#cl.SendInitPresence(requestRoster=0) # you may need to uncomment
this for old server
disp=xmpp.dispatcher.Dispatcher()
disp.plugin(cl)
for srchRes in xmpp.features.discoverItems(disp,tojid):
print srchRes
On Thu, Jun 18, 2009 at 5:50 AM, Norman Rasmussen<no...@ra...> wrote:
> On Wed, Jun 17, 2009 at 9:24 PM, Will Siddall <wil...@gm...>
> wrote:
>>
>> I've gotten as far as creating a dispatcher object, but the next line
>> when I initialize the dispatcher's plugin, it crashes. I'm
>> authenticating, so, it's just to do the search.
>
> can you post the code that's failing, it's easier to debug that way.
> by 'discover search' do you mean vcard / disco info / or iq:search?
>
> --
> - Norman Rasmussen
> - Email: no...@ra...
> - Home page: http://norman.rasmussen.co.za/
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Xmpppy-devel mailing list
> Xmp...@li...
> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel
>
>
|
|
From: Norman R. <no...@ra...> - 2009-06-18 08:50:25
|
On Wed, Jun 17, 2009 at 9:24 PM, Will Siddall <wil...@gm...>wrote: > I've gotten as far as creating a dispatcher object, but the next line > when I initialize the dispatcher's plugin, it crashes. I'm > authenticating, so, it's just to do the search. > can you post the code that's failing, it's easier to debug that way. by 'discover search' do you mean vcard / disco info / or iq:search? -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |
|
From: Will S. <wil...@gm...> - 2009-06-17 19:24:56
|
Hey guys, I've just picked up the package the other day and love it. I have to say that example usage is really scarce, so much of the development's been at a stand still for me. The only thing I'm looking for is to be able to log into a server and do a discovery search for any jid, especially those not in a roster list, and display the contact's attributes. I've gotten as far as creating a dispatcher object, but the next line when I initialize the dispatcher's plugin, it crashes. I'm authenticating, so, it's just to do the search. Any help is greatly appreciated. Thanks Will |
|
From: Carlos A. <car...@gm...> - 2009-05-22 06:55:07
|
>> Btw, do you now any jabber client library (python, perl, ruby, ...) with >> XEP-0124 support? After a lot of googling I'm not able to find anything >> in order to implement a few simple scripts to test a BOSH server. > > Gajim developpment version has BOSH support. > > You can get it in mercurial repository I'll check it out today. Thanks Yann! -- Carlos. |
|
From: Yann Le B. <as...@la...> - 2009-05-21 19:17:53
|
Carlos Abalde <car...@gm...> a écrit : > Hi all, > > Could you please confirm me if XEP-0124 is supported in the xmpppy > library? After reviewing the code I'm pretty sure it is not, however I > would like to confirm it. indeed it's not. > Btw, do you now any jabber client library (python, perl, ruby, ...) with > XEP-0124 support? After a lot of googling I'm not able to find anything > in order to implement a few simple scripts to test a BOSH server. Gajim developpment version has BOSH support. You can get it in mercurial repository -- Yann ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Carlos A. <car...@gm...> - 2009-05-21 16:59:13
|
Hi all, Could you please confirm me if XEP-0124 is supported in the xmpppy library? After reviewing the code I'm pretty sure it is not, however I would like to confirm it. Btw, do you now any jabber client library (python, perl, ruby, ...) with XEP-0124 support? After a lot of googling I'm not able to find anything in order to implement a few simple scripts to test a BOSH server. Thank you very much! -- Carlos. |
|
From: ErikZ <eri...@gm...> - 2009-05-15 16:06:48
|
There we go. I went into both accounts and used the "Add contact". Once I was able to send and receive messages from the gmail screen, the fuction worked. I now have a script that will alert me when my server has an issue. Thanks! On Fri, May 15, 2009 at 12:45 AM, Norman Rasmussen <no...@ra...> wrote: > On Thu, May 14, 2009 at 11:12 PM, ErikZ <eri...@gm...> wrote: >> So, now it's working. Kind of. There's no errors, and just a few >> warnings. But my IM client (pidgin) isn't getting any messsges. And my >> Google phone didn't get it either. I'm seeing some warnings, but >> nothing that would stop the message from going out? > > Do XXXX and YYYY have subscriptions between their accounts? If they're > not on each other's roster and auth'ed, then Google typically blocks > messages. > > -- > - Norman Rasmussen > - Email: no...@ra... > - Home page: http://norman.rasmussen.co.za/ > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Xmpppy-devel mailing list > Xmp...@li... > https://lists.sourceforge.net/lists/listinfo/xmpppy-devel > |
|
From: Norman R. <no...@ra...> - 2009-05-15 06:45:31
|
On Thu, May 14, 2009 at 11:12 PM, ErikZ <eri...@gm...> wrote: > So, now it's working. Kind of. There's no errors, and just a few > warnings. But my IM client (pidgin) isn't getting any messsges. And my > Google phone didn't get it either. I'm seeing some warnings, but > nothing that would stop the message from going out? Do XXXX and YYYY have subscriptions between their accounts? If they're not on each other's roster and auth'ed, then Google typically blocks messages. -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |
|
From: ErikZ <eri...@gm...> - 2009-05-14 21:12:44
|
Ah! Thanks for the example!
After giving it a working .xsend file, it ended with "could not
connect". So I made the second change you suggested and it gave me
tons of debug info.
It had an issue with no pydns being available. Loaded that with easy_install.
So, now it's working. Kind of. There's no errors, and just a few
warnings. But my IM client (pidgin) isn't getting any messsges. And my
Google phone didn't get it either. I'm seeing some warnings, but
nothing that would stop the message from going out?
>xsend YYY...@gm... hi
Invalid debugflag given: always
Invalid debugflag given: nodebuilder
DEBUG:
DEBUG: Debug created for build/bdist.linux-x86_64/egg/xmpp/client.py
DEBUG: flags defined: always,nodebuilder
DEBUG: socket start Plugging <xmpp.transports.TCPsocket instance
at 0x2af8f8e70b00> into <xmpp.client.Client instance at
0x2af8f8e706c8>
DEBUG: socket start Successfully connected to remote host
('talk2.l.google.com', 5222)
DEBUG: dispatcher start Plugging <xmpp.dispatcher.Dispatcher
instance at 0x2af8f8e77440> into <xmpp.client.Client instance at
0x2af8f8e706c8>
DEBUG: dispatcher info Registering namespace "unknown"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(unknown)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(unknown)
DEBUG: dispatcher info Registering namespace
"http://etherx.jabber.org/streams"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: dispatcher info Registering namespace "jabber:client"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(jabber:client)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(jabber:client)
DEBUG: dispatcher info Registering protocol "iq" as <class
'xmpp.protocol.Iq'>(jabber:client)
DEBUG: dispatcher info Registering protocol "presence" as <class
'xmpp.protocol.Presence'>(jabber:client)
DEBUG: dispatcher info Registering protocol "message" as <class
'xmpp.protocol.Message'>(jabber:client)
DEBUG: dispatcher info Registering handler <bound method
Dispatcher.streamErrorHandler of <xmpp.dispatcher.Dispatcher instance
at 0x2af8f8e77440>> for "error" type->
ns->(http://etherx.jabber.org/streams)
DEBUG: dispatcher warn Registering protocol "error" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: socket sent <?xml version='1.0'?>
<stream:stream xmlns="jabber:client" to="gmail.com" version="1.0"
xmlns:stream="http://etherx.jabber.org/streams" >
DEBUG: socket got <stream:stream from="gmail.com"
id="F4803319A409EAFF" version="1.0"
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
<stream:features>
<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls">
<required/>
</starttls>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>X-GOOGLE-TOKEN</mechanism>
</mechanisms>
</stream:features>
DEBUG: dispatcher warn Unknown stanza: features
DEBUG: dispatcher ok Dispatching unknown stanza with type->
props->[u'urn:ietf:params:xml:ns:xmpp-tls',
u'urn:ietf:params:xml:ns:xmpp-sasl'] id->None
DEBUG: tls start Plugging <xmpp.transports.TLS instance at
0x2af8f8e77b00> into <xmpp.client.Client instance at 0x2af8f8e706c8>
DEBUG: tls ok TLS supported by remote server. Requesting TLS start.
DEBUG: dispatcher info Registering handler <bound method
TLS.StartTLSHandler of <xmpp.transports.TLS instance at
0x2af8f8e77b00>> for "proceed" type->
ns->(urn:ietf:params:xml:ns:xmpp-tls)
DEBUG: dispatcher warn Registering namespace
"urn:ietf:params:xml:ns:xmpp-tls"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-tls)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-tls)
DEBUG: dispatcher warn Registering protocol "proceed" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-tls)
DEBUG: dispatcher info Registering handler <bound method
TLS.StartTLSHandler of <xmpp.transports.TLS instance at
0x2af8f8e77b00>> for "failure" type->
ns->(urn:ietf:params:xml:ns:xmpp-tls)
DEBUG: dispatcher warn Registering protocol "failure" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-tls)
DEBUG: socket sent <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
DEBUG: socket got <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
DEBUG: dispatcher ok Got urn:ietf:params:xml:ns:xmpp-tls/proceed stanza
DEBUG: dispatcher ok Dispatching proceed stanza with type->
props->[] id->None
DEBUG: tls ok Got starttls proceed response. Switching to TLS/SSL...
DEBUG: dispatcher stop Plugging <xmpp.dispatcher.Dispatcher
instance at 0x2af8f8e77440> out of <xmpp.client.Client instance at
0x2af8f8e706c8>.
DEBUG: dispatcher start Plugging <xmpp.dispatcher.Dispatcher
instance at 0x2af8f8e77dd0> into <xmpp.client.Client instance at
0x2af8f8e706c8>
DEBUG: dispatcher info Registering namespace "unknown"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(unknown)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(unknown)
DEBUG: dispatcher info Registering namespace
"http://etherx.jabber.org/streams"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: dispatcher info Registering namespace "jabber:client"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(jabber:client)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(jabber:client)
DEBUG: dispatcher info Registering protocol "iq" as <class
'xmpp.protocol.Iq'>(jabber:client)
DEBUG: dispatcher info Registering protocol "presence" as <class
'xmpp.protocol.Presence'>(jabber:client)
DEBUG: dispatcher info Registering protocol "message" as <class
'xmpp.protocol.Message'>(jabber:client)
DEBUG: dispatcher info Registering handler <bound method
Dispatcher.streamErrorHandler of <xmpp.dispatcher.Dispatcher instance
at 0x2af8f8e77dd0>> for "error" type->
ns->(http://etherx.jabber.org/streams)
DEBUG: dispatcher warn Registering protocol "error" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: socket sent <?xml version='1.0'?>
<stream:stream xmlns="jabber:client" to="gmail.com" version="1.0"
xmlns:stream="http://etherx.jabber.org/streams" >
connected with tls
DEBUG: socket got <stream:stream from="gmail.com"
id="B71839407070635D" version="1.0"
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
<stream:features>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>PLAIN</mechanism>
<mechanism>X-GOOGLE-TOKEN</mechanism>
</mechanisms>
</stream:features>
DEBUG: dispatcher warn Unknown stanza: features
DEBUG: dispatcher ok Dispatching unknown stanza with type->
props->[u'urn:ietf:params:xml:ns:xmpp-sasl'] id->None
DEBUG: sasl start Plugging <xmpp.auth.SASL instance at
0x2af8f8e7a320> into <xmpp.client.Client instance at 0x2af8f8e706c8>
DEBUG: dispatcher info Registering handler <bound method
SASL.SASLHandler of <xmpp.auth.SASL instance at 0x2af8f8e7a320>> for
"challenge" type-> ns->(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: dispatcher warn Registering namespace
"urn:ietf:params:xml:ns:xmpp-sasl"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: dispatcher warn Registering protocol "challenge" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: dispatcher info Registering handler <bound method
SASL.SASLHandler of <xmpp.auth.SASL instance at 0x2af8f8e7a320>> for
"failure" type-> ns->(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: dispatcher warn Registering protocol "failure" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: dispatcher info Registering handler <bound method
SASL.SASLHandler of <xmpp.auth.SASL instance at 0x2af8f8e7a320>> for
"success" type-> ns->(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: dispatcher warn Registering protocol "success" as <class
'xmpp.protocol.Protocol'>(urn:ietf:params:xml:ns:xmpp-sasl)
DEBUG: socket sent <auth
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"
mechanism="PLAIN">Yi53YXMuYTE4MUBnbWFpbC5jb20AYi53YXMuYTE4MQByZXRhcmRlZA==</auth>
DEBUG: socket got <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>
DEBUG: dispatcher ok Got urn:ietf:params:xml:ns:xmpp-sasl/success stanza
DEBUG: dispatcher ok Dispatching success stanza with type->
props->[] id->None
DEBUG: sasl ok Successfully authenticated with remote server.
DEBUG: dispatcher stop Plugging <xmpp.dispatcher.Dispatcher
instance at 0x2af8f8e77dd0> out of <xmpp.client.Client instance at
0x2af8f8e706c8>.
DEBUG: dispatcher start Plugging <xmpp.dispatcher.Dispatcher
instance at 0x2af8f8e7a518> into <xmpp.client.Client instance at
0x2af8f8e706c8>
DEBUG: dispatcher info Registering namespace "unknown"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(unknown)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(unknown)
DEBUG: dispatcher info Registering namespace
"http://etherx.jabber.org/streams"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: dispatcher info Registering namespace "jabber:client"
DEBUG: dispatcher info Registering protocol "unknown" as <class
'xmpp.protocol.Protocol'>(jabber:client)
DEBUG: dispatcher info Registering protocol "default" as <class
'xmpp.protocol.Protocol'>(jabber:client)
DEBUG: dispatcher info Registering protocol "iq" as <class
'xmpp.protocol.Iq'>(jabber:client)
DEBUG: dispatcher info Registering protocol "presence" as <class
'xmpp.protocol.Presence'>(jabber:client)
DEBUG: dispatcher info Registering protocol "message" as <class
'xmpp.protocol.Message'>(jabber:client)
DEBUG: dispatcher info Registering handler <bound method
Dispatcher.streamErrorHandler of <xmpp.dispatcher.Dispatcher instance
at 0x2af8f8e7a518>> for "error" type->
ns->(http://etherx.jabber.org/streams)
DEBUG: dispatcher warn Registering protocol "error" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: socket sent <?xml version='1.0'?>
<stream:stream xmlns="jabber:client" to="gmail.com" version="1.0"
xmlns:stream="http://etherx.jabber.org/streams" >
DEBUG: bind start Plugging <xmpp.auth.Bind instance at
0x2af8f8e7ab00> into <xmpp.client.Client instance at 0x2af8f8e706c8>
DEBUG: dispatcher info Registering handler <bound method
Bind.FeaturesHandler of <xmpp.auth.Bind instance at 0x2af8f8e7ab00>>
for "features" type-> ns->(http://etherx.jabber.org/streams)
DEBUG: dispatcher warn Registering protocol "features" as <class
'xmpp.protocol.Protocol'>(http://etherx.jabber.org/streams)
DEBUG: socket got <stream:stream from="gmail.com"
id="FDA1E1E77A1433E0" version="1.0"
xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
DEBUG: socket got <stream:features>
<bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/>
<session xmlns="urn:ietf:params:xml:ns:xmpp-session"/>
</stream:features>
DEBUG: dispatcher ok Got http://etherx.jabber.org/streams/features stanza
DEBUG: dispatcher ok Dispatching features stanza with type->
props->[u'urn:ietf:params:xml:ns:xmpp-bind',
u'urn:ietf:params:xml:ns:xmpp-session'] id->None
DEBUG: socket sent <iq type="set" id="1">
<bind xmlns="urn:ietf:params:xml:ns:xmpp-bind" />
</iq>
DEBUG: dispatcher wait Waiting for ID:1 with timeout 25...
DEBUG: socket got <iq id="1" type="result">
<bind xmlns="urn:ietf:params:xml:ns:xmpp-bind">
<jid>XXX...@gm.../7FC8F048</jid>
</bind>
</iq>
DEBUG: dispatcher ok Got jabber:client/iq stanza
DEBUG: dispatcher ok Dispatching iq stanza with type->result
props->[u'urn:ietf:params:xml:ns:xmpp-bind'] id->1
DEBUG: dispatcher ok Expected stanza arrived!
DEBUG: bind ok Successfully bound b.w...@gm.../7FC8F048.
DEBUG: socket sent <iq type="set" id="2">
<session xmlns="urn:ietf:params:xml:ns:xmpp-session" />
</iq>
DEBUG: dispatcher wait Waiting for ID:2 with timeout 25...
DEBUG: socket got <iq type="result" id="2"/>
DEBUG: dispatcher ok Got jabber:client/iq stanza
DEBUG: dispatcher ok Dispatching iq stanza with type->result
props->[] id->2
DEBUG: dispatcher ok Expected stanza arrived!
DEBUG: bind ok Successfully opened session.
authenticated using sasl
DEBUG: socket sent <message to="YYY...@gm..." id="3">
<body>hi</body>
</message>
sent message with id 3
There's a ton of info
On Thu, May 14, 2009 at 1:49 PM, Norman Rasmussen
<no...@ra...> wrote:
> my .xsend:
> JID=me...@gm...
> PASSWORD=kensentme
>
> if it still doesn't work, change:
> cl=xmpp.Client(jid.getDomain(),debug=[])
> to
> cl=xmpp.Client(jid.getDomain())
>
> which will cause lots of debug info to spew out, that you can paste
> here (obviously try it with a test user/password) when you do
>
> On Thu, May 14, 2009 at 9:38 PM, ErikZ <eri...@gm...> wrote:
>> Hi, I'm trying to get the xsend example working with google chat.
>>
>> My goal is to write a script to check something under Linux. And if it
>> fails, it will send me a message.
>>
>> Currently I'm having trouble setting up the .xsend file. There's no
>> examples on how to set it up properly. I tried hard coding the account
>> and login in the script, but it just skips it and demands a working
>> .xsend file.
>>
>> Has anyone seen a *working* example script that will send off a single
>> message to a google chat user?
|
|
From: Norman R. <no...@ra...> - 2009-05-14 19:49:58
|
my .xsend: JID=me...@gm... PASSWORD=kensentme if it still doesn't work, change: cl=xmpp.Client(jid.getDomain(),debug=[]) to cl=xmpp.Client(jid.getDomain()) which will cause lots of debug info to spew out, that you can paste here (obviously try it with a test user/password) when you do On Thu, May 14, 2009 at 9:38 PM, ErikZ <eri...@gm...> wrote: > Hi, I'm trying to get the xsend example working with google chat. > > My goal is to write a script to check something under Linux. And if it > fails, it will send me a message. > > Currently I'm having trouble setting up the .xsend file. There's no > examples on how to set it up properly. I tried hard coding the account > and login in the script, but it just skips it and demands a working > .xsend file. > > Has anyone seen a *working* example script that will send off a single > message to a google chat user? > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Xmpppy-devel mailing list > Xmp...@li... > https://lists.sourceforge.net/lists/listinfo/xmpppy-devel > -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |
|
From: ErikZ <eri...@gm...> - 2009-05-14 19:38:22
|
Hi, I'm trying to get the xsend example working with google chat. My goal is to write a script to check something under Linux. And if it fails, it will send me a message. Currently I'm having trouble setting up the .xsend file. There's no examples on how to set it up properly. I tried hard coding the account and login in the script, but it just skips it and demands a working .xsend file. Has anyone seen a *working* example script that will send off a single message to a google chat user? |
|
From: Martin O. <doc...@gm...> - 2009-04-22 13:51:44
|
Alexey, > May be you are not ignorant in xmpp, but that is not main the point here. > The thing is - you came here not to find help but just to grumble and expresss > your dissatisfaction abou t the fact that library is not what you wanted it > to be. It's up to you, but my first posts were asking about where the features were located. When you gave me the "Oh it's scattered around the API" answer, that is when I made a point to explain my views on bad API designs. I don't want or care to make you upset, so I could hardly be a troll. And if explaining myself upsets you, that's not my problem. Your right that it's a free project and I've already started work on what I need because I don't expect you to magically turn round and redesign your code on my whims. > You have been asked several times to provide specific examples to ground your > point. You failed. So until you do that I have to treat you as a troll, I > just do not have another choice. Sorry for that. Muc was the whole point, but I notice all those methods in features.py, iq:register shouldn't need to be like that, all passing in the client instance... Anyway, we won't learn anything if we're just at each other's throat. So, I consider my question answered and my views discarded. Regards, Martin |
|
From: Alexey N. <sn...@pe...> - 2009-04-22 06:56:43
|
On Monday 20 April 2009 Martin Owens wrote: > Alexey, > > I don't think I'm going to find much help here, I understand your > position and whilst I understand the xmpp protocol, I don't wish to know > it in my code. No, I don't think you will either. > There is very useful patterns which show you how to convert from a > protocol to a bunch of interlinked objects. The idea is not to _hide_ > the protocol from the end programmer, but to increase his speed of > development by providing effective implementations of the end concepts > which map into the protocol. > > If your just thinking about squireling away the basics of the protocol, > then that's fine. But I'm not convinced that's an effective API to take > care of most use cases. > > I've got a working model I may end up expanding and separating into it's > own module package to take care of the API. I'm thinking of calling it > python-xmpp-objects or python-xmpp-easy, something that explains it's > designed OO API. > > It may be possible to bring those into your code base in the future. I > haven't thought that far ahead yet though. Just wanted to make sure that > you know where I stand isn't because of ignorance of xmpp, but because > of a difference in style of programming and API separation. > > Kind Regards, Martin Owens May be you are not ignorant in xmpp, but that is not main the point here. The thing is - you came here not to find help but just to grumble and expresss your dissatisfaction abou t the fact that library is not what you wanted it to be. xmpppy is a free library and as with any free project - it doesn't owe you anything. If you want it to become better - propose something or send in a patch. If you want help - tell what you need, what you tried and what is the problem. You have been asked several times to provide specific examples to ground your point. You failed. So until you do that I have to treat you as a troll, I just do not have another choice. Sorry for that. -- Respectfully Alexey Nezhdanov |
|
From: Martin O. <doc...@gm...> - 2009-04-20 13:19:54
|
Alexey, I don't think I'm going to find much help here, I understand your position and whilst I understand the xmpp protocol, I don't wish to know it in my code. There is very useful patterns which show you how to convert from a protocol to a bunch of interlinked objects. The idea is not to _hide_ the protocol from the end programmer, but to increase his speed of development by providing effective implementations of the end concepts which map into the protocol. If your just thinking about squireling away the basics of the protocol, then that's fine. But I'm not convinced that's an effective API to take care of most use cases. I've got a working model I may end up expanding and separating into it's own module package to take care of the API. I'm thinking of calling it python-xmpp-objects or python-xmpp-easy, something that explains it's designed OO API. It may be possible to bring those into your code base in the future. I haven't thought that far ahead yet though. Just wanted to make sure that you know where I stand isn't because of ignorance of xmpp, but because of a difference in style of programming and API separation. Kind Regards, Martin Owens |
|
From: Alexey N. <sn...@pe...> - 2009-04-20 04:14:22
|
On Monday 13 April 2009 Martin Owens wrote: > > Sorry, but that is a _very_ vague answer. Can you be more specific about > > interfaces that you used before and you miss now? Code examples would be > > great. > > It was a _very_ vague question. What am I after? something that works > exactly like pyxmpp but doesn't suck? Hmm... I've asked for code examples. Isn't that precise enough. And after all - as I said already - MUC is a quite simple feature. I can see the need for Roster class because user should not be concerned with tracking contacts himself. And it can be used for the MUC as well to track room participants. So what is left is sending and receiving messages which is easily done with commands I suggested in the very begginning of this thread. I'm sorry, but I'm getting impression that you just do not know how XMPP works and to not want to know. Just some shiny interface that will hide all protocol-specific features away from you. xmpppy never intended to do that and never did. > > Didn't get it. May be you refer to 'read the source' advice somewhere in > > example scripts? There is a pydoc-generated list of interfaces that is > > enough in 90% of cases (function names and arguments are self-explanatory > > I hope). And in 10% rest, when you really want to know how it works - you > > have to read source anyways. Why that is a bad idea? > > I am, even if you could use the auto-generated pydoc, my concern is that > the documentation in the code isn't very good and it's hard enough > getting developers to work on project without them being scared away. > > I wasn't too impressed by the code either, what ever possesed you to put > such giant clause statements on one line? Well, I repeat - in almost all cases you just need function names (provided that you _know_xmpp_). If you are in doubt - you can look at docstring for that function. I agree - most docstrings do not conform to standard that python help has, but they are informative enough to give the idea of what the function does. Still in doubt (the remaining 10%) - read the code - again most of the interface functions are short enough to make that easy. Regarding big oneliner - well, I had a habit of writing them at the time. Not without a reason - with vertically oriented screen I had about 80 lines of code visible at the same time so working on the library was pretty easy - I was able to navigate through each module with only a few PgUp/PgDn and related function are always in the same place. Since then I decided that it is a wrong idea and left that habit behind but code is still there. You are free to send a patch. > Regards, Martin > > > --------------------------------------------------------------------------- >--- This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Xmpppy-devel mailing list > Xmp...@li... > https://lists.sourceforge.net/lists/listinfo/xmpppy-devel -- Respectfully Alexey Nezhdanov |
|
From: Martin O. <doc...@gm...> - 2009-04-13 14:12:17
|
> Sorry, but that is a _very_ vague answer. Can you be more specific about > interfaces that you used before and you miss now? Code examples would be > great. It was a _very_ vague question. What am I after? something that works exactly like pyxmpp but doesn't suck? > Didn't get it. May be you refer to 'read the source' advice somewhere in > example scripts? There is a pydoc-generated list of interfaces that is enough > in 90% of cases (function names and arguments are self-explanatory I hope). > And in 10% rest, when you really want to know how it works - you have to read > source anyways. Why that is a bad idea? I am, even if you could use the auto-generated pydoc, my concern is that the documentation in the code isn't very good and it's hard enough getting developers to work on project without them being scared away. I wasn't too impressed by the code either, what ever possesed you to put such giant clause statements on one line? Regards, Martin |
|
From: Alexey N. <sn...@pe...> - 2009-04-13 13:58:58
|
On Monday 13 April 2009 Martin Owens wrote: > On Mon, 2009-04-13 at 09:41 +0400, Alexey Nezhdanov wrote: > > Norman already replied about that, but I have a question: > > what exactly do you want from the library beyond the following two lines? > > > > cl.sendPresence(to='room@server/nick') > > cl.sendMessage(typ='chat',...) > > Something more OO based. I was converting one API to another and it's > not always direct since some APIs hide things and some APIs hide nothing > at all. Sorry, but that is a _very_ vague answer. Can you be more specific about interfaces that you used before and you miss now? Code examples would be great. > Although one developer has already run away because of the lack of > documentation in xmpppy. :-/ apparently "read the code" wasn't a very > good idea. Didn't get it. May be you refer to 'read the source' advice somewhere in example scripts? There is a pydoc-generated list of interfaces that is enough in 90% of cases (function names and arguments are self-explanatory I hope). And in 10% rest, when you really want to know how it works - you have to read source anyways. Why that is a bad idea? > Regards, Martin -- Respectfully Alexey Nezhdanov |
|
From: Martin O. <doc...@gm...> - 2009-04-13 12:28:48
|
On Mon, 2009-04-13 at 09:41 +0400, Alexey Nezhdanov wrote: > Norman already replied about that, but I have a question: > what exactly do you want from the library beyond the following two lines? > > cl.sendPresence(to='room@server/nick') > cl.sendMessage(typ='chat',...) Something more OO based. I was converting one API to another and it's not always direct since some APIs hide things and some APIs hide nothing at all. Although one developer has already run away because of the lack of documentation in xmpppy. :-/ apparently "read the code" wasn't a very good idea. Regards, Martin |
|
From: Alexey N. <sn...@pe...> - 2009-04-13 05:41:32
|
Norman already replied about that, but I have a question: what exactly do you want from the library beyond the following two lines? cl.sendPresence(to='room@server/nick') cl.sendMessage(typ='chat',...) On Saturday 11 April 2009 Martin Owens wrote: > Hey all, > > I'm moving a support application for Ubuntu over from pyxmpp > (python-pyxmpp) which seems deprecated in jaunty, over to xmpppy > (python-xmpp). > > My application uses MUC quite extensively, I expressed a class to > represent a chat room in my code. But I can't seem to find the way to > hook this up with xmpppy, it's like it doesn't have any internal support > for muc other than a few namespace definitions. > > Perhaps I've got the wrong end of the stick. > > https://code.launchpad.net/locoremotesupport > > Best Regards, Martin Owens -- Respectfully Alexey Nezhdanov |
|
From: Norman R. <no...@ra...> - 2009-04-11 11:27:25
|
There's no special MUC support in xmpp.py. MUC is basically just standard message and presence stanza's, so it should be fairly easy to modify your code to use xmpp.py On Sat, Apr 11, 2009 at 1:12 AM, Martin Owens <doc...@gm...> wrote: > Hey all, > > I'm moving a support application for Ubuntu over from pyxmpp > (python-pyxmpp) which seems deprecated in jaunty, over to xmpppy > (python-xmpp). > > My application uses MUC quite extensively, I expressed a class to > represent a chat room in my code. But I can't seem to find the way to > hook this up with xmpppy, it's like it doesn't have any internal support > for muc other than a few namespace definitions. > > Perhaps I've got the wrong end of the stick. > > https://code.launchpad.net/locoremotesupport > > Best Regards, Martin Owens > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Xmpppy-devel mailing list > Xmp...@li... > https://lists.sourceforge.net/lists/listinfo/xmpppy-devel > -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |
|
From: Martin O. <doc...@gm...> - 2009-04-10 23:13:02
|
Hey all, I'm moving a support application for Ubuntu over from pyxmpp (python-pyxmpp) which seems deprecated in jaunty, over to xmpppy (python-xmpp). My application uses MUC quite extensively, I expressed a class to represent a chat room in my code. But I can't seem to find the way to hook this up with xmpppy, it's like it doesn't have any internal support for muc other than a few namespace definitions. Perhaps I've got the wrong end of the stick. https://code.launchpad.net/locoremotesupport Best Regards, Martin Owens |
|
From: Norman R. <no...@ra...> - 2009-03-26 19:51:22
|
you can create a Browser and PlugIn to the client, then you can setDiscoHandler to hook up an event handler, have a look around line 500 in http://xmpppy.cvs.sourceforge.net/viewvc/xmpppy/xmpppy/yahoo-transport/yahoo.py?view=markup to see and example of this handler (obviously your need would be much simpler, because you're only a single client case, not a full transport). There is no xep-0115 helper for xmpp.py, so you're on your own a bit there, the transports would love to be able to do xep-0115, so if you do end up coding support for it, it would be fantastic if you could contribute it back to xmpp.py. Cheers Norman 2009/3/26 Vikas Singhal <vik...@gm...> > Thanks not working out for me Norman. After some surfing I found that we > need to send capabilities first then it will discover more info. > http://xmpp.org/extensions/xep-0115.html > any inputs? > > > On Thu, Mar 26, 2009 at 7:20 PM, Vikas Singhal <vik...@gm... > > wrote: > >> Thanks Norman, I will try this and revert back. >> >> >> 2009/3/26 Norman Rasmussen <no...@ra...> >> >>> the sample I gave was for events (xep-0022), here's the sample for >>> chatstates (xep-0085): >>> send: >>> as before: m = Message(typ='chat',frm = fromAddress, >>> to=toAddress,body=messageBody) >>> add this: m.setTag('active',namespace=NS_CHATSTATES) >>> >>> detect: >>> composing = messageEvent.getTag('composing',namespace=NS_CHATSTATES) >>> >>> hope that helps >>> >>> On Thu, Mar 26, 2009 at 2:44 PM, Vikas Singhal < >>> vik...@gm...> wrote: >>> >>>> And how will I do that. please guide! >>>> >>>> 2009/3/26 Norman Rasmussen <no...@ra...> >>>> >>>>> sometimes clients will only generate the events when they detect that >>>>> you support them, so often you have to have sent at least one message with >>>>> 'active' to enable it. >>>>> >>>>> >>>>> 2009/3/26 Vikas Singhal <vik...@gm...> >>>>> >>>>> I am able to see the events (composing, paused etc... ) in my logs from >>>>>> the pidgin client but for the gtalk users its not appearing. any clues? >>>>>> >>>>>> >>>>>> On Thu, Mar 26, 2009 at 4:30 PM, Yann Leboulanger < >>>>>> as...@la...> wrote: >>>>>> >>>>>>> Vikas Singhal a écrit : >>>>>>> > I can only see 'chat' and 'error' in my message call back function. >>>>>>> I am >>>>>>> > not seeing any "composing" or "paused" state. >>>>>>> > >>>>>>> > Any idea why? >>>>>>> > >>>>>>> > I registered the message handler as >>>>>>> > : connection.RegisterHandler('message', messageCB) >>>>>>> >>>>>>> as I already told you, look at XEP-0085: >>>>>>> http://www.xmpp.org/extensions/xep-0085.html >>>>>>> >>>>>>> -- >>>>>>> Yann >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> _______________________________________________ >>>>>>> Xmpppy-devel mailing list >>>>>>> Xmp...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> >>>>>> _______________________________________________ >>>>>> Xmpppy-devel mailing list >>>>>> Xmp...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> - Norman Rasmussen >>>>> - Email: no...@ra... >>>>> - Home page: http://norman.rasmussen.co.za/ >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> _______________________________________________ >>>>> Xmpppy-devel mailing list >>>>> Xmp...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >>>>> >>>>> >>>> >>> >>> >>> -- >>> - Norman Rasmussen >>> - Email: no...@ra... >>> - Home page: http://norman.rasmussen.co.za/ >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Xmpppy-devel mailing list >>> Xmp...@li... >>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >>> >>> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Xmpppy-devel mailing list > Xmp...@li... > https://lists.sourceforge.net/lists/listinfo/xmpppy-devel > > -- - Norman Rasmussen - Email: no...@ra... - Home page: http://norman.rasmussen.co.za/ |
|
From: Vikas S. <vik...@gm...> - 2009-03-26 15:28:17
|
Thanks not working out for me Norman. After some surfing I found that we need to send capabilities first then it will discover more info. http://xmpp.org/extensions/xep-0115.html any inputs? On Thu, Mar 26, 2009 at 7:20 PM, Vikas Singhal <vik...@gm...>wrote: > Thanks Norman, I will try this and revert back. > > > 2009/3/26 Norman Rasmussen <no...@ra...> > >> the sample I gave was for events (xep-0022), here's the sample for >> chatstates (xep-0085): >> send: >> as before: m = Message(typ='chat',frm = fromAddress, >> to=toAddress,body=messageBody) >> add this: m.setTag('active',namespace=NS_CHATSTATES) >> >> detect: >> composing = messageEvent.getTag('composing',namespace=NS_CHATSTATES) >> >> hope that helps >> >> On Thu, Mar 26, 2009 at 2:44 PM, Vikas Singhal < >> vik...@gm...> wrote: >> >>> And how will I do that. please guide! >>> >>> 2009/3/26 Norman Rasmussen <no...@ra...> >>> >>>> sometimes clients will only generate the events when they detect that >>>> you support them, so often you have to have sent at least one message with >>>> 'active' to enable it. >>>> >>>> >>>> 2009/3/26 Vikas Singhal <vik...@gm...> >>>> >>>> I am able to see the events (composing, paused etc... ) in my logs from >>>>> the pidgin client but for the gtalk users its not appearing. any clues? >>>>> >>>>> >>>>> On Thu, Mar 26, 2009 at 4:30 PM, Yann Leboulanger <as...@la... >>>>> > wrote: >>>>> >>>>>> Vikas Singhal a écrit : >>>>>> > I can only see 'chat' and 'error' in my message call back function. >>>>>> I am >>>>>> > not seeing any "composing" or "paused" state. >>>>>> > >>>>>> > Any idea why? >>>>>> > >>>>>> > I registered the message handler as >>>>>> > : connection.RegisterHandler('message', messageCB) >>>>>> >>>>>> as I already told you, look at XEP-0085: >>>>>> http://www.xmpp.org/extensions/xep-0085.html >>>>>> >>>>>> -- >>>>>> Yann >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> _______________________________________________ >>>>>> Xmpppy-devel mailing list >>>>>> Xmp...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >>>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> _______________________________________________ >>>>> Xmpppy-devel mailing list >>>>> Xmp...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >>>>> >>>>> >>>> >>>> >>>> -- >>>> - Norman Rasmussen >>>> - Email: no...@ra... >>>> - Home page: http://norman.rasmussen.co.za/ >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Xmpppy-devel mailing list >>>> Xmp...@li... >>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >>>> >>>> >>> >> >> >> -- >> - Norman Rasmussen >> - Email: no...@ra... >> - Home page: http://norman.rasmussen.co.za/ >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Xmpppy-devel mailing list >> Xmp...@li... >> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel >> >> > |
|
From: Vikas S. <vik...@gm...> - 2009-03-26 13:51:28
|
Thanks Norman, I will try this and revert back.
2009/3/26 Norman Rasmussen <no...@ra...>
> the sample I gave was for events (xep-0022), here's the sample for
> chatstates (xep-0085):
> send:
> as before: m = Message(typ='chat',frm = fromAddress,
> to=toAddress,body=messageBody)
> add this: m.setTag('active',namespace=NS_CHATSTATES)
>
> detect:
> composing = messageEvent.getTag('composing',namespace=NS_CHATSTATES)
>
> hope that helps
>
> On Thu, Mar 26, 2009 at 2:44 PM, Vikas Singhal <vik...@gm...
> > wrote:
>
>> And how will I do that. please guide!
>>
>> 2009/3/26 Norman Rasmussen <no...@ra...>
>>
>>> sometimes clients will only generate the events when they detect that you
>>> support them, so often you have to have sent at least one message with
>>> 'active' to enable it.
>>>
>>>
>>> 2009/3/26 Vikas Singhal <vik...@gm...>
>>>
>>> I am able to see the events (composing, paused etc... ) in my logs from
>>>> the pidgin client but for the gtalk users its not appearing. any clues?
>>>>
>>>>
>>>> On Thu, Mar 26, 2009 at 4:30 PM, Yann Leboulanger <as...@la...>wrote:
>>>>
>>>>> Vikas Singhal a écrit :
>>>>> > I can only see 'chat' and 'error' in my message call back function. I
>>>>> am
>>>>> > not seeing any "composing" or "paused" state.
>>>>> >
>>>>> > Any idea why?
>>>>> >
>>>>> > I registered the message handler as
>>>>> > : connection.RegisterHandler('message', messageCB)
>>>>>
>>>>> as I already told you, look at XEP-0085:
>>>>> http://www.xmpp.org/extensions/xep-0085.html
>>>>>
>>>>> --
>>>>> Yann
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> _______________________________________________
>>>>> Xmpppy-devel mailing list
>>>>> Xmp...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel
>>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Xmpppy-devel mailing list
>>>> Xmp...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel
>>>>
>>>>
>>>
>>>
>>> --
>>> - Norman Rasmussen
>>> - Email: no...@ra...
>>> - Home page: http://norman.rasmussen.co.za/
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Xmpppy-devel mailing list
>>> Xmp...@li...
>>> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel
>>>
>>>
>>
>
>
> --
> - Norman Rasmussen
> - Email: no...@ra...
> - Home page: http://norman.rasmussen.co.za/
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Xmpppy-devel mailing list
> Xmp...@li...
> https://lists.sourceforge.net/lists/listinfo/xmpppy-devel
>
>
|
