From cl-xmpp-devel at common-lisp.net  Thu Apr  6 19:28:45 2006
From: cl-xmpp-devel at common-lisp.net (cl-xmpp)
Date: Thu, 06 Apr 2006 19:28:45 -0000
Subject: [cl-xmpp-devel] [cl-xmpp] #1: let's try this now
Message-ID: <079.214f8fc7e7d826224b6d2634635795b0@common-lisp.net>

#1: let's try this now
------------------------+---------------------------------------------------
       Id:  1           |      Status:  new                     
Component:  component1  |    Modified:  Thu Apr  6 15:28:45 2006
 Severity:  normal      |   Milestone:                          
 Priority:  normal      |     Version:                          
    Owner:  somebody    |    Reporter:  erik.enge at gmail.com     
------------------------+---------------------------------------------------
 should work

-- 
Ticket URL: <http://common-lisp.net:8000/cl-xmpp-trac/ticket/1>
cl-xmpp <http://common-lisp.net/project/cl-xmpp>
cl-xmpp

From erik.enge at gmail.com  Thu Apr  6 19:33:09 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Thu, 6 Apr 2006 15:33:09 -0400
Subject: [cl-xmpp-devel] [cl-xmpp] #1: let's try this now
In-Reply-To: <079.214f8fc7e7d826224b6d2634635795b0@common-lisp.net>
References: <079.214f8fc7e7d826224b6d2634635795b0@common-lisp.net>
Message-ID: <58f839b70604061233q58d76a92p681f411d501e1f8e@mail.gmail.com>

Sorry gusy, I'm using cl-xmpp to test Trac.  Hopefully I shouldn't
have to spam this list more than a few more times.

Erik.


From joelr1 at gmail.com  Wed Apr 26 14:41:20 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 15:41:20 +0100
Subject: [cl-xmpp-devel] GoogleTalk authentication error
Message-ID: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>

Folks,

Am I doing something wrong here? I'm using Allegro 8.0 and had to  
patch cffi just a bit. Is google not liking the digested password?

#<CL-XMPP:CONNECTION to talk.google.com:5222 (open) @ #x10d791a2>
CL-USER> (xmpp:auth x "donbolsa at gmail.com" "xxx"  
"resource" :mechanism :digest-md5)
<iq id="auth2" type="set"><query  
xmlns="jabber:iq:auth"><username>donbolsa at gmail.com</ 
username><digest>13fe1484e53e8bc7bd78114f062a4fcb8d1e0b79</ 
digest><resource>resource</resource></query></iq>><iq id="auth2"  
type="error"><query  
xmlns="jabber:iq:auth"><username>donbolsa at gmail.com</ 
username><digest>13fe1484e53e8bc7bd78114f062a4fcb8d1e0b79</ 
digest><resource>resource</resource></query><error code="400"  
type="modify" err:hostname="vaae68.prod.google.com"  
err:bnsname="vaae68"  
err:stacktrace="com.google.buzz.core.Stanza.buildError(Stanza.java: 
289) | com.google.buzz.core.Stanza.buildError(Stanza.java:265) |  
com.google.buzz.connection.ConnectionEndpoint.sendErrorToClient 
(ConnectionEndpoint.java:258) |  
com.google.buzz.connection.JabberAuthModule.sendErrorAndClose 
(JabberAuthModule.java:232) |  
com.google.buzz.connection.JabberAuthModule.handleAuthSet 
(JabberAuthModule.java:180) |  
com.google.buzz.connection.JabberAuthModule$2.handleStanza 
(JabberAuthModule.java:56) |  
com.google.buzz.connection.ConnectionEndpointFactory.handleClientStanza( 
ConnectionEndpointFactory.java:186) |  
com.google.buzz.connection.ConnectionEndpoint.processStanzaFromClient 
(ConnectionEndpoint.java:275) |  
com.google.buzz.connection.XmppEndpoint.processStanzaFromClient 
(XmppEndpoint.java:739) |  
com.google.buzz.connection.XmppStanzaParser.stanza 
(XmppStanzaParser.java:54) | com.google.buzz.xml.StanzaParser 
$StreamFactory.addChild(StanzaParser.java:149) |  
com.google.buzz.xml.FactoryHandler.onEnd(FactoryHandler.java:118) |  
com.google.buzz.xml.RecklessParser.reportTag(RecklessParser.java:996)  
| com.google.buzz.xml.RecklessParser.doparse(RecklessParser.java:534)  
| com.google.buzz.xml.RecklessParser.parse(RecklessParser.java:327) |  
com.google.buzz.xml.StanzaParser.parse(StanzaParser.java:94) |  
com.google.buzz.connection.XmppEndpoint.continueDataReceived 
(XmppEndpoint.java:968) | com.google.buzz.connection.XmppEndpoint 
$4.runEndpoint(XmppEndpoint.java:942) | " xmlns:err="google:rich- 
errors"><bad-request xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/ 
 ><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">missing password</ 
text></error></iq
UNHANDLED: AUTHENTICATION-SUCCESSFUL
<presence></presence>
"<presence></presence>"
CL-USER>

--
http://wagerlabs.com/







From joelr1 at gmail.com  Wed Apr 26 15:22:02 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 16:22:02 +0100
Subject: [cl-xmpp-devel] GoogleTalk authentication error
In-Reply-To: <58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>
References: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
	<58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>
Message-ID: <D736C29B-99BD-43B8-AFD0-BDEAB122B676@gmail.com>

Hi Erik!

On Apr 26, 2006, at 4:17 PM, Erik Enge wrote:

> There is at least one bug here.  The library reports
> AUTHENTICATION-SUCCESSFUL when it quite clearly wasn't.  (Patches very
> welcome, I unfortunately do not use or develop cl-xmpp anymore;
> maintainers apply within :-).

I might apply if I at least get moving :-).

> There may be another bug here though I am curious, did you use
> CONNECT-TLS to connect to Google Talk?

Yes, I did.

> Also, I wonder if I recall
> correctly that after connecting using TLS to Google Talk you should
> just use the plain auth method.

Thanks for pointing me in the right direction. I'll poke around with  
this some more, having a different issue now.

No methods applicable for generic function
#<STANDARD-GENERIC-FUNCTION RUNES::XSTREAM/CLOSE> with args
(#S(CL-XMPP::SLOW-STREAM :TARGET #<FLEXI-STREAMS:FLEXI-IO-STREAM
                                    @
                                    #x10e0a76a>))
of classes (CL-XMPP::SLOW-STREAM)
    [Condition of type PROGRAM-ERROR]

	Thanks, Joel

--
http://wagerlabs.com/







From erik.enge at gmail.com  Wed Apr 26 15:17:47 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Wed, 26 Apr 2006 11:17:47 -0400
Subject: [cl-xmpp-devel] GoogleTalk authentication error
In-Reply-To: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
References: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
Message-ID: <58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>

On 4/26/06, Joel Reymont <joelr1 at gmail.com> wrote:
> Am I doing something wrong here? I'm using Allegro 8.0 and had to
> patch cffi just a bit. Is google not liking the digested password?

There is at least one bug here.  The library reports
AUTHENTICATION-SUCCESSFUL when it quite clearly wasn't.  (Patches very
welcome, I unfortunately do not use or develop cl-xmpp anymore;
maintainers apply within :-).

There may be another bug here though I am curious, did you use
CONNECT-TLS to connect to Google Talk?  Also, I wonder if I recall
correctly that after connecting using TLS to Google Talk you should
just use the plain auth method.  There error you see reported seems to
claim that you have failed to specify a password which I think makes
sense if they expect to see a <password> tag in there.

Try it with plain and see how that goes.

I'm unable to try this on my workstation presently.

Erik.


From joelr1 at gmail.com  Wed Apr 26 15:57:58 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 16:57:58 +0100
Subject: [cl-xmpp-devel] GoogleTalk authentication error
In-Reply-To: <20060426153646.GA4902@gargravarr.knowledgetools.de>
References: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
	<58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>
	<D736C29B-99BD-43B8-AFD0-BDEAB122B676@gmail.com>
	<20060426153646.GA4902@gargravarr.knowledgetools.de>
Message-ID: <7724CCA6-3C1B-4E67-9325-54E0B82FB0F6@gmail.com>

I finally got it to work. I did have to use plain authentication  
after establishing a TLS connection. Now I just have to figure out  
what XML to send for things like authorizations, etc. Oh, and make  
sure event callbacks work.

I'm also considering removing a bunch of dependencies (cl+ssl, etc.)  
when ACL 8.0 Enterprise is used. Would this be a good idea?

	Thanks, Joel

--
http://wagerlabs.com/







From david at lichteblau.com  Wed Apr 26 15:36:46 2006
From: david at lichteblau.com (David Lichteblau)
Date: Wed, 26 Apr 2006 17:36:46 +0200
Subject: [cl-xmpp-devel] GoogleTalk authentication error
In-Reply-To: <D736C29B-99BD-43B8-AFD0-BDEAB122B676@gmail.com>
References: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
	<58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>
	<D736C29B-99BD-43B8-AFD0-BDEAB122B676@gmail.com>
Message-ID: <20060426153646.GA4902@gargravarr.knowledgetools.de>

Quoting Joel Reymont (joelr1 at gmail.com):
> No methods applicable for generic function
> #<STANDARD-GENERIC-FUNCTION RUNES::XSTREAM/CLOSE> with args
> (#S(CL-XMPP::SLOW-STREAM :TARGET #<FLEXI-STREAMS:FLEXI-IO-STREAM
>                                    @
>                                    #x10e0a76a>))
> of classes (CL-XMPP::SLOW-STREAM)
>    [Condition of type PROGRAM-ERROR]

Stacktrace?


From joelr1 at gmail.com  Wed Apr 26 15:50:06 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 16:50:06 +0100
Subject: [cl-xmpp-devel] GoogleTalk authentication error
In-Reply-To: <20060426153646.GA4902@gargravarr.knowledgetools.de>
References: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
	<58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>
	<D736C29B-99BD-43B8-AFD0-BDEAB122B676@gmail.com>
	<20060426153646.GA4902@gargravarr.knowledgetools.de>
Message-ID: <0F1F7B12-CF9B-40F2-9164-7F67E0D4F3EE@gmail.com>

Can't reproduce it now but will post next time.

On Apr 26, 2006, at 4:36 PM, David Lichteblau wrote:

> Quoting Joel Reymont (joelr1 at gmail.com):
>> No methods applicable for generic function
>> #<STANDARD-GENERIC-FUNCTION RUNES::XSTREAM/CLOSE> with args
>> (#S(CL-XMPP::SLOW-STREAM :TARGET #<FLEXI-STREAMS:FLEXI-IO-STREAM
>>                                    @
>>                                    #x10e0a76a>))
>> of classes (CL-XMPP::SLOW-STREAM)
>>    [Condition of type PROGRAM-ERROR]
>
> Stacktrace?

--
http://wagerlabs.com/







From joelr1 at gmail.com  Wed Apr 26 16:42:03 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 17:42:03 +0100
Subject: [cl-xmpp-devel] start-sax-document
Message-ID: <9F42C75C-6B3E-4474-8418-E4E46B295644@gmail.com>

Folks,

Any particular reason for this wrapper around sax:start-document?

(defun start-sax-document (handler)
   (let ((dom-builder (cxml-dom:make-dom-builder)))
     (setf (cxml:proxy-chained-handler handler) dom-builder)
     (sax:start-document dom-builder)
     dom-builder))

I would like to swap out CXML for Allegro's built-in XML/SAX parser  
and the SAX API seems to match. The DOM API is different thus I can't  
replace the above.

	Thanks, Joel

--
http://wagerlabs.com/







From david at lichteblau.com  Wed Apr 26 16:52:42 2006
From: david at lichteblau.com (David Lichteblau)
Date: Wed, 26 Apr 2006 18:52:42 +0200
Subject: [cl-xmpp-devel] start-sax-document
In-Reply-To: <9F42C75C-6B3E-4474-8418-E4E46B295644@gmail.com>
References: <9F42C75C-6B3E-4474-8418-E4E46B295644@gmail.com>
Message-ID: <20060426165242.GA5324@gargravarr.knowledgetools.de>

Quoting Joel Reymont (joelr1 at gmail.com):
> Any particular reason for this wrapper around sax:start-document?
> 
> (defun start-sax-document (handler)
>   (let ((dom-builder (cxml-dom:make-dom-builder)))
>     (setf (cxml:proxy-chained-handler handler) dom-builder)
>     (sax:start-document dom-builder)
>     dom-builder))
> 
> I would like to swap out CXML for Allegro's built-in XML/SAX parser  
> and the SAX API seems to match. The DOM API is different thus I can't  
> replace the above.

I don't understand the question.  This function installs a CXML DOM
builder in the stanza handler, which uses a CXML SAX proxy.

CL-XMPP currently uses CXML.  If you want to switch to Allegro-specific
libraries you can try to do so, but personally I would not be able to
help you with that.

Specificially, CL-XMPP uses DOM, so you would have to adapt the code to
the function names Franz chose to use, among other changes.


From joelr1 at gmail.com  Wed Apr 26 16:53:08 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 17:53:08 +0100
Subject: [cl-xmpp-devel] start-sax-document
In-Reply-To: <20060426165242.GA5324@gargravarr.knowledgetools.de>
References: <9F42C75C-6B3E-4474-8418-E4E46B295644@gmail.com>
	<20060426165242.GA5324@gargravarr.knowledgetools.de>
Message-ID: <DC9BEFAC-3EB4-48D6-B3B4-AEA993226EE6@gmail.com>


On Apr 26, 2006, at 5:52 PM, David Lichteblau wrote:

> Specificially, CL-XMPP uses DOM, so you would have to adapt the  
> code to
> the function names Franz chose to use, among other changes.

That's the answer I was looking for. I assumed you were using SAX  
internally and was wondering what DOM had to do with it.

Any particular reason for using DOM on top of SAX instead of just SAX?

	Thanks, Joel

--
http://wagerlabs.com/







From david at lichteblau.com  Wed Apr 26 17:03:33 2006
From: david at lichteblau.com (David Lichteblau)
Date: Wed, 26 Apr 2006 19:03:33 +0200
Subject: [cl-xmpp-devel] start-sax-document
In-Reply-To: <DC9BEFAC-3EB4-48D6-B3B4-AEA993226EE6@gmail.com>
References: <9F42C75C-6B3E-4474-8418-E4E46B295644@gmail.com>
	<20060426165242.GA5324@gargravarr.knowledgetools.de>
	<DC9BEFAC-3EB4-48D6-B3B4-AEA993226EE6@gmail.com>
Message-ID: <20060426170333.GA5383@gargravarr.knowledgetools.de>

Quoting Joel Reymont (joelr1 at gmail.com):
> Any particular reason for using DOM on top of SAX instead of just SAX?

That is a question for Erik, but I think the rationale is the other way
around:

He used DOM because he wanted to.

And the explicit mucking around with the SAX layer got introduced only
because CXML is a push-based (SAX-like) parser as opposed to pull-pased
(StAX-like).  (Like all other currently available XML parsers written in
Lisp that I'm aware of.)

But since CL-XMPP wants to read from the stream (which is technically
one huge XML document) not in one step but rather stanza-by-stanza,
parsing needs to be stopped and restarted after each stanza, and that
was relatively easy to accomplish by intercepting the SAX events before
handing them to the DOM builder for the current stanza.


From erik.enge at gmail.com  Wed Apr 26 17:53:34 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Wed, 26 Apr 2006 13:53:34 -0400
Subject: [cl-xmpp-devel] start-sax-document
In-Reply-To: <20060426170333.GA5383@gargravarr.knowledgetools.de>
References: <9F42C75C-6B3E-4474-8418-E4E46B295644@gmail.com>
	<20060426165242.GA5324@gargravarr.knowledgetools.de>
	<DC9BEFAC-3EB4-48D6-B3B4-AEA993226EE6@gmail.com>
	<20060426170333.GA5383@gargravarr.knowledgetools.de>
Message-ID: <58f839b70604261053s343d289fxf84d17bb876080ea@mail.gmail.com>

On 4/26/06, David Lichteblau <david at lichteblau.com> wrote:
> Quoting Joel Reymont (joelr1 at gmail.com):
> > Any particular reason for using DOM on top of SAX instead of just SAX?
>
> That is a question for Erik, but I think the rationale is the other way
> around:
>
> He used DOM because he wanted to.

Yeah it was just out of pragmatism for the reasons you listed.

Erik.


From joelr1 at gmail.com  Wed Apr 26 20:38:17 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 21:38:17 +0100
Subject: [cl-xmpp-devel] (make-error nil)
Message-ID: <00C27ABF-2FB0-4296-BF26-3CED5D6DE1F6@gmail.com>

I'm don't know cl-xmpp well enough yet to fix it but here's a bug  
report. I think it has something to do with trying to receive a  
stanza that's not there.

	Thanks, Joel

No methods applicable for generic function
#<STANDARD-GENERIC-FUNCTION CL-XMPP::MAKE-ERROR> with args (NIL) of
classes (NULL)
    [Condition of type PROGRAM-ERROR]

Restarts:
   0: [CONTINUE] Try calling it again
   1: [ABORT-REQUEST] Abort handling SLIME request.
   2: [ABORT] Abort entirely from this (lisp) process.

Backtrace:
   0: (SWANK::DEBUG-IN-EMACS #<PROGRAM-ERROR @ #x10d2a53a>)
   1: (SWANK:SWANK-DEBUGGER-HOOK #<PROGRAM-ERROR @ #x10d2a53a>  
#<Function SWANK-DEBUGGER-HOOK>)
   2: (CERROR "Try calling it again" PROGRAM-ERROR :FORMAT-CONTROL  
"No methods applicable for generic function ~s with args ~s of  
classes ~s" :FORMAT-ARGUMENTS (#<STANDARD-GENERIC-FUNCTION CL- 
XMPP::MAKE-ERROR> (NIL) (NULL)))
   3: ((METHOD NO-APPLICABLE-METHOD (T)) #<STANDARD-GENERIC-FUNCTION  
CL-XMPP::MAKE-ERROR> NIL)
   4: ((METHOD CL-XMPP::DOM-TO-EVENT (CL-XMPP:CONNECTION LIST)) #<CL- 
XMPP:CONNECTION to talk.google.com:5222 (open) @ #x10cb0c5a> (#<CL- 
XMPP:XML-ELEMENT IQ (3attr:1child:0data) @ #x10d2a1c2>))
   5: (CL-XMPP::DEFAULT-STANZA-CALLBACK #<RUNE-DOM::DOCUMENT @  
#x10d27e22> #<CL-XMPP:CONNECTION to talk.google.com:5222 (open) @  
#x10cb0c5a> :DOM-REPR NIL)
   6: ((METHOD CL-XMPP:RECEIVE-STANZA (CL-XMPP:CONNECTION)) #<CL- 
XMPP:CONNECTION to talk.google.com:5222 (open) @ #x10cb0c5a>)
   7: ((:INTERNAL (:EFFECTIVE-METHOD 1 T T NIL NIL) 0) #<CL- 
XMPP:CONNECTION to talk.google.com:5222 (open) @ #x10cb0c5a>)
   8: (EVAL (CL-XMPP:RECEIVE-STANZA X))
   9: (SWANK::EVAL-REGION "(xmpp:receive-stanza x)")
10: ((:INTERNAL SWANK:INTERACTIVE-EVAL-REGION 0))
11: ((METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (T)) #<Closure  
(:INTERNAL SWANK:INTERACTIVE-EVAL-REGION 0) @ #x10d1fd3a>)
12: (SWANK::CALL-WITH-BUFFER-SYNTAX #<Closure (:INTERNAL  
SWANK:INTERACTIVE-EVAL-REGION 0) @ #x10d1fd3a>)
13: (SWANK:INTERACTIVE-EVAL-REGION "(xmpp:receive-stanza x)")
14: (EVAL (SWANK:INTERACTIVE-EVAL-REGION "(xmpp:receive-stanza x)"))

--
http://wagerlabs.com/







From joelr1 at gmail.com  Wed Apr 26 20:34:47 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 21:34:47 +0100
Subject: [cl-xmpp-devel] GoogleTalk authentication error
In-Reply-To: <20060426153646.GA4902@gargravarr.knowledgetools.de>
References: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
	<58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>
	<D736C29B-99BD-43B8-AFD0-BDEAB122B676@gmail.com>
	<20060426153646.GA4902@gargravarr.knowledgetools.de>
Message-ID: <66D9B76F-FDB2-47C0-84E6-1E674AB53608@gmail.com>

Here you go David:

No methods applicable for generic function
#<STANDARD-GENERIC-FUNCTION RUNES::XSTREAM/CLOSE> with args
(#S(CL-XMPP::SLOW-STREAM :TARGET #<EXCL::SSL-CLIENT-STREAM
                                     fd #
                                    @
                                    #x10ab379a>))
of classes (CL-XMPP::SLOW-STREAM)
    [Condition of type PROGRAM-ERROR]

Restarts:
   0: [CONTINUE] Try calling it again
   1: [ABORT-REQUEST] Abort handling SLIME request.
   2: [ABORT] Abort entirely from this (lisp) process.

Backtrace:
   0: (SWANK::DEBUG-IN-EMACS #<PROGRAM-ERROR @ #x10b6c5c2>)
   1: (SWANK:SWANK-DEBUGGER-HOOK #<PROGRAM-ERROR @ #x10b6c5c2>  
#<Function SWANK-DEBUGGER-HOOK>)
   2: (CERROR "Try calling it again" PROGRAM-ERROR :FORMAT-CONTROL  
"No methods applicable for generic function ~s with args ~s of  
classes ~s" :FORMAT-ARGUMENTS (#<STANDARD-GENERIC-FUNCTION  
RUNES::XSTREAM/CLOSE> (#S(CL-XMPP::SLOW-STREAM :TARGET #)) (CL- 
XMPP::SLOW-STREAM)))
   3: ((METHOD NO-APPLICABLE-METHOD (T)) #<STANDARD-GENERIC-FUNCTION  
RUNES::XSTREAM/CLOSE> #S(CL-XMPP::SLOW-STREAM :TARGET #<EXCL::SSL- 
CLIENT-STREAM  fd #<MULTIVALENT #1=stream socket #1#connected from  
192.168.0.101/52975 to toolbar.google.com/5222 @ #x10adce92> @  
#x10ab379a>))
   4: ((FLET #:ENSURE-GENERIC-FUNCTION-USING-CLASS--NULL  
EXCL::INITIAL-CHEAP-SELECT-FUNCTION) #<STANDARD-GENERIC-FUNCTION  
RUNES::XSTREAM/CLOSE> #S(CL-XMPP::SLOW-STREAM :TARGET #<EXCL::SSL- 
CLIENT-STREAM  fd #<MULTIVALENT #1=stream socket #1#connected from  
192.168.0.101/52975 to toolbar.google.com/5222 @ #x10adce92> @  
#x10ab379a>))
   5: (CXML::READ-TOKEN-2 #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN- 
SEMANTIC NIL :INPUT-STACK NIL))
   6: (CXML::PEEK-TOKEN #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN- 
SEMANTIC NIL :INPUT-STACK NIL))
   7: (CXML::P/DOCUMENT #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN- 
SEMANTIC NIL :INPUT-STACK NIL) #<CL-XMPP::STANZA-HANDLER @ #x10b67e22>)
   8: (CXML::PARSE-XSTREAM #<RUNES:XSTREAM [stanza :MAIN NIL]> #<CL- 
XMPP::STANZA-HANDLER @ #x10b67e22>)
   9: (CL-XMPP::READ-STANZA #<CL-XMPP:CONNECTION to talk.google.com: 
5222 (open) @ #x10ab2afa>)
10: ((METHOD CL-XMPP:RECEIVE-STANZA (CL-XMPP:CONNECTION)) #<CL- 
XMPP:CONNECTION to talk.google.com:5222 (open) @ #x10ab2afa>)
11: ((:INTERNAL (:EFFECTIVE-METHOD 1 T T NIL NIL) 0) #<CL- 
XMPP:CONNECTION to talk.google.com:5222 (open) @ #x10ab2afa>)
12: (EVAL (CL-XMPP:RECEIVE-STANZA X))
13: (SWANK::EVAL-REGION "(xmpp:receive-stanza x)

" T)
14: ((:INTERNAL SWANK:LISTENER-EVAL 0))
15: ((METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (T)) #<Closure  
(:INTERNAL SWANK:LISTENER-EVAL 0) @ #x10b67d8a>)
16: (SWANK::CALL-WITH-BUFFER-SYNTAX #<Closure (:INTERNAL  
SWANK:LISTENER-EVAL 0) @ #x10b67d8a>)
17: (SWANK:LISTENER-EVAL "(xmpp:receive-stanza x)

--
http://wagerlabs.com/







From erik.enge at gmail.com  Wed Apr 26 20:57:34 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Wed, 26 Apr 2006 16:57:34 -0400
Subject: [cl-xmpp-devel] (make-error nil)
In-Reply-To: <00C27ABF-2FB0-4296-BF26-3CED5D6DE1F6@gmail.com>
References: <00C27ABF-2FB0-4296-BF26-3CED5D6DE1F6@gmail.com>
Message-ID: <58f839b70604261357h37380f2bw97e8eae84d4f45a6@mail.gmail.com>

On 4/26/06, Joel Reymont <joelr1 at gmail.com> wrote:
> I'm don't know cl-xmpp well enough yet to fix it but here's a bug
> report. I think it has something to do with trying to receive a
> stanza that's not there.

I remember this one.  The problem was that I was unable to get all
different ways an error may be raised (I think at least three). 
There's the old way, new way and a few variations on both (basically
using the <error> element or not).  What you have encountered here is
basically a place where I got this wrong.

What we need is a complete list of all situations and how to deal with
them and then just change the appropriate functions.  I think it's
xml-element-to-event and make-error and that's about it.

Erik.


From joelr1 at gmail.com  Wed Apr 26 21:01:36 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 22:01:36 +0100
Subject: [cl-xmpp-devel] Telling apart subscription granted and denied
Message-ID: <F899C40B-D1A9-474E-BC1A-1DCEC41961C9@gmail.com>

My apologies for this not being specific to cl-xmpp but...

How do I tell a denied subscription apart from a granted one? It  
seems that the reply that I receive is the same and the only  
difference is the error reply I get when sending a message.

I also tried to add myself to a different using GTalk and Adium and I  
did not receive a request for subscription authorization either time.  
Am I doing something wrong?

	Thanks, Joel

--
http://wagerlabs.com/







From joelr1 at gmail.com  Wed Apr 26 21:44:44 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Wed, 26 Apr 2006 22:44:44 +0100
Subject: [cl-xmpp-devel] Error when adding myself to my own roster
Message-ID: <84C51EDC-53E4-4AA1-B757-207CF08F7F71@gmail.com>

Removing does not produce this effect but adding does:

Cannot convert #<Function (:INTERNAL EXCL::UPDATE-TO-CHECKING-DFUN 0)>
to a RUNES:ROD
    [Condition of type SIMPLE-ERROR]

Restarts:
   0: [ABORT-REQUEST] Abort handling SLIME request.
   1: [ABORT] Abort entirely from this (lisp) process.

Backtrace:
   0: (SWANK::DEBUG-IN-EMACS #<SIMPLE-ERROR @ #x10d32d8a>)
   1: (SWANK:SWANK-DEBUGGER-HOOK #<SIMPLE-ERROR @ #x10d32d8a>  
#<Function SWANK-DEBUGGER-HOOK>)
   2: (ERROR "Cannot convert ~S to a ~S" #<Function (:INTERNAL  
EXCL::UPDATE-TO-CHECKING-DFUN 0)> RUNES:ROD)
   3: (RUNES:ROD #<Function (:INTERNAL EXCL::UPDATE-TO-CHECKING-DFUN  
0)>)
   4: (CXML:ATTRIBUTE "name" #<Function (:INTERNAL EXCL::UPDATE-TO- 
CHECKING-DFUN 0)>)
   5: ((:INTERNAL (:INTERNAL (:INTERNAL # 0) 0) 0))
   6: (CXML::INVOKE-WITH-ELEMENT #<Closure (:INTERNAL (:INTERNAL # 0)  
0) @ #x10d32d0a> "item")
   7: (CXML::INVOKE-WITH-ELEMENT #<Closure (:INTERNAL (:INTERNAL # 0)  
0) @ #x10d32caa> "query")
   8: (CXML::INVOKE-WITH-ELEMENT #<Closure (:INTERNAL (:INTERNAL # 0)  
0) @ #x10d32c42> "iq")
   9: (CXML::INVOKE-WITH-XML-OUTPUT #<Closure (:INTERNAL (METHOD CL- 
XMPP:ROSTER-ADD #) 0) @ #x10d30b1a> #<CXML::SINK @ #x10d32bf2>)
10: ((METHOD CL-XMPP:ROSTER-ADD (CL-XMPP:CONNECTION T T T)) #<CL- 
XMPP:CONNECTION to talk.google.com:5222 (open) @ #x10cfa6a2>  
"kuzya1 at gmail.com")
11: (EVAL (CL-XMPP:ROSTER-ADD X "kuzya1 at gmail.com"))
12: (SWANK::EVAL-REGION "(xmpp:roster-add x \"kuzya1 at gmail.com\")
" T)
13: ((:INTERNAL SWANK:LISTENER-EVAL 0))
14: ((METHOD SWANK-BACKEND:CALL-WITH-SYNTAX-HOOKS (T)) #<Closure  
(:INTERNAL SWANK:LISTENER-EVAL 0) @ #x10d30982>)
15: (SWANK::CALL-WITH-BUFFER-SYNTAX #<Closure (:INTERNAL  
SWANK:LISTENER-EVAL 0) @ #x10d30982>)
16: (SWANK:LISTENER-EVAL "(xmpp:roster-add x \"kuzya1 at gmail.com\")

--
http://wagerlabs.com/







From david at lichteblau.com  Thu Apr 27 11:53:06 2006
From: david at lichteblau.com (David Lichteblau)
Date: Thu, 27 Apr 2006 13:53:06 +0200
Subject: [cl-xmpp-devel] GoogleTalk authentication error
In-Reply-To: <66D9B76F-FDB2-47C0-84E6-1E674AB53608@gmail.com>
References: <1EC9A8CF-9FF2-4D95-94C1-5530D1A2DFA8@gmail.com>
	<58f839b70604260817g6ac45283tc1d654f81a52edac@mail.gmail.com>
	<D736C29B-99BD-43B8-AFD0-BDEAB122B676@gmail.com>
	<20060426153646.GA4902@gargravarr.knowledgetools.de>
	<66D9B76F-FDB2-47C0-84E6-1E674AB53608@gmail.com>
Message-ID: <20060427115306.GA10636@gargravarr.knowledgetools.de>

Quoting Joel Reymont (joelr1 at gmail.com):
> Here you go David:
> 
> No methods applicable for generic function
> #<STANDARD-GENERIC-FUNCTION RUNES::XSTREAM/CLOSE> with args
> (#S(CL-XMPP::SLOW-STREAM :TARGET #<EXCL::SSL-CLIENT-STREAM
>                                     fd #
>                                    @
>                                    #x10ab379a>))
> of classes (CL-XMPP::SLOW-STREAM)
>    [Condition of type PROGRAM-ERROR]

"Unexpected end of file" is what this is trying to say, I guess.

So, probably a followup-error in a situation that shouldn't occur
anyway.  Nevertheless, either of the following definitions in
cl-xmpp/xstream.lisp might help.

(defmethod runes::xstream/close ((stream slow-stream)) (close stream))
-or-
(defmethod runes::xstream/close ((stream slow-stream)) nil)


From joelr1 at gmail.com  Thu Apr 27 13:01:00 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Thu, 27 Apr 2006 14:01:00 +0100
Subject: [cl-xmpp-devel] DonBolsa
Message-ID: <4FFBB5C1-0AC5-433D-B74F-AB63F0E42D17@gmail.com>

A new bot is born:

http://donbolsa.blogspot.com/2006/04/new-bot-is-born.html


--
http://wagerlabs.com/







From joelr1 at gmail.com  Thu Apr 27 17:16:55 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Thu, 27 Apr 2006 18:16:55 +0100
Subject: [cl-xmpp-devel] Proper way of getting the presence type
Message-ID: <AEBFBB9C-999A-413D-90D9-8209CDDDC46C@gmail.com>

What is the proper way of getting the type from the presence object?  
The type- accessor does not seem to be exported from the package.

I'm trying to create a handler for the various types of presence.

	Thanks, Joel

--
http://wagerlabs.com/







From erik.enge at gmail.com  Thu Apr 27 17:48:58 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Thu, 27 Apr 2006 13:48:58 -0400
Subject: [cl-xmpp-devel] DonBolsa
In-Reply-To: <4FFBB5C1-0AC5-433D-B74F-AB63F0E42D17@gmail.com>
References: <4FFBB5C1-0AC5-433D-B74F-AB63F0E42D17@gmail.com>
Message-ID: <58f839b70604271048o6da1d369j40da97bc1c607fdb@mail.gmail.com>

On 4/27/06, Joel Reymont <joelr1 at gmail.com> wrote:
> http://donbolsa.blogspot.com/2006/04/new-bot-is-born.html

Hey, neat idea!

Erik.


From erik.enge at gmail.com  Thu Apr 27 17:25:42 2006
From: erik.enge at gmail.com (Erik Enge)
Date: Thu, 27 Apr 2006 13:25:42 -0400
Subject: [cl-xmpp-devel] Proper way of getting the presence type
In-Reply-To: <AEBFBB9C-999A-413D-90D9-8209CDDDC46C@gmail.com>
References: <AEBFBB9C-999A-413D-90D9-8209CDDDC46C@gmail.com>
Message-ID: <58f839b70604271025r40dee89ct95cca292505c751d@mail.gmail.com>

On 4/27/06, Joel Reymont <joelr1 at gmail.com> wrote:
> What is the proper way of getting the type from the presence object?

I'm sorry to say I don't remember what the spec says anymore, though...

> The type- accessor does not seem to be exported from the package.

... that's probably not a good indicator.  Read the spec and it may
turn out that the type- symbol ought to be exported.

Erik.


From joelr1 at gmail.com  Thu Apr 27 17:39:37 2006
From: joelr1 at gmail.com (Joel Reymont)
Date: Thu, 27 Apr 2006 18:39:37 +0100
Subject: [cl-xmpp-devel] Proper way of getting the presence type
In-Reply-To: <58f839b70604271025r40dee89ct95cca292505c751d@mail.gmail.com>
References: <AEBFBB9C-999A-413D-90D9-8209CDDDC46C@gmail.com>
	<58f839b70604271025r40dee89ct95cca292505c751d@mail.gmail.com>
Message-ID: <CBD1F0DA-A56A-4592-A1B7-C771F2850A2E@gmail.com>

Allright, I'll just dig in and change whatever I need. Not sure how  
useful my patches would be but I won't care about it for now.

I noticed a few problems like subscription requests not getting to  
me. I'll dig deep and fix things up.

>> The type- accessor does not seem to be exported from the package.
>
> ... that's probably not a good indicator.  Read the spec and it may
> turn out that the type- symbol ought to be exported.

--
http://wagerlabs.com/