From jjwiseman at yahoo.com  Thu Nov  3 19:40:22 2005
From: jjwiseman at yahoo.com (John Wiseman)
Date: Thu, 3 Nov 2005 11:40:22 -0800
Subject: [cl-xmpp-devel] asdf-install link broken
Message-ID: <0C6434FD-3F23-4067-BB27-46BD92FCE903@yahoo.com>

http://common-lisp.net/project/cl-xmpp/cl-xmpp_latest.tar.gz gives me
a 404.


John



From erik.enge at gmail.com  Wed Nov  9 20:22:04 2005
From: erik.enge at gmail.com (Erik Enge)
Date: Wed, 9 Nov 2005 15:22:04 -0500
Subject: [cl-xmpp-devel] asdf-install link broken
In-Reply-To: <0C6434FD-3F23-4067-BB27-46BD92FCE903@yahoo.com>
References: <0C6434FD-3F23-4067-BB27-46BD92FCE903@yahoo.com>
Message-ID: <58f839b70511091222w19e4f8c7j3d1e8c479ecf2905@mail.gmail.com>

On 11/3/05, John Wiseman <jjwiseman at yahoo.com> wrote:
> http://common-lisp.net/project/cl-xmpp/cl-xmpp_latest.tar.gz gives me
> a 404.

Oops, fixed.

Thanks,
Erik.


From adam.thorsen at gmail.com  Thu Nov 10 16:33:46 2005
From: adam.thorsen at gmail.com (Adam Thorsen)
Date: Thu, 10 Nov 2005 09:33:46 -0700
Subject: [cl-xmpp-devel] All calls return connection object
Message-ID: <290f54b70511100833j1ecd12eeu285d61b600cd5d00@mail.gmail.com>

I've been working with cl-xmpp for the past couple of days.  I seem to
be able to create a connection object successfully:

(defvar connection (xmpp:connect :hostname "jabber.loglibrary.com"))

However,

All subsequent calls to the API seem only to return the connection
object, and accomplish nothing:

CL-USER> (xmpp:message connection "awt at jabber.loglibrary.com" "what's
going on?")
#<CL-XMPP:CONNECTION to jabber.loglibrary.com:5222 (open) {40D789D1}>
CL-USER>


CL-USER> (xmpp:presence connection)
#<CL-XMPP:CONNECTION to jabber.loglibrary.com:5222 (open) {40D789D1}>
CL-USER>


None of the above actually seem to work (the account's buddy icon
doesn't appear to come online, and no messages are recieved from it.)

If I describe the connection object, this is what I see:

CL-USER> (describe (xmpp:discover connection))
#<CL-XMPP:CONNECTION to jabber.loglibrary.com:5222 (open) {40D789D1}>
is an instance of class #<STANDARD-CLASS CL-XMPP:CONNECTION>.
The following slots have :INSTANCE allocation:
 SERVER-STREAM     #<SB-SYS:FD-STREAM for "a constant string"
{40CE75A9}>
 SOCKET            #<SB-BSD-SOCKETS:INET-SOCKET descriptor 10
{40BFA049}>
 SERVER-XSTREAM    NIL
 STREAM-ID         NIL
 HOSTNAME          "jabber.loglibrary.com"
 PORT              5222
; No value
CL-USER>


I am using SBCL obtained a few days ago via darwinports.

Thanks,
-Adam


From erik.enge at gmail.com  Thu Nov 10 20:56:53 2005
From: erik.enge at gmail.com (Erik Enge)
Date: Thu, 10 Nov 2005 15:56:53 -0500
Subject: [cl-xmpp-devel] All calls return connection object
In-Reply-To: <290f54b70511100833j1ecd12eeu285d61b600cd5d00@mail.gmail.com>
References: <290f54b70511100833j1ecd12eeu285d61b600cd5d00@mail.gmail.com>
Message-ID: <58f839b70511101256v7301c03fw4c2ffcb1365b1c94@mail.gmail.com>

On 11/10/05, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> All subsequent calls to the API seem only to return the connection
> object, and accomplish nothing:

This is the intended behavior.  I would like to print the actual XML
sent to the server but presently CXML doesn't allow me to do that
easily without writing my own binary stream which converts to
characters and prints to a secondary character stream (eg
*standard-output*) like broadcast streams do.  I would welcome such a
patch.

I didn't see a call to xmpp:auth, was that just a slip or are you not
calling it?

According to the RFCs, if you are interested in presence information,
the recommended order is auth -> presence -> any messaging.

Also, I don't see a call to xmpp:begin-xml-stream.  This is required
as the first thing you do after xmpp:connect.  A good client should
also call xmpp:end-xml-stream before calling close on the connection
object.

> None of the above actually seem to work (the account's buddy icon
> doesn't appear to come online, and no messages are recieved from it.)

To receive replies from the server, try xmpp:receive-stanza-loop and
see what it returns to you.

* (defparameter *connection* (xmpp:connect :hostname "jabber.loglibrary.com"))
*CONNECTION*
* (xmpp:begin-xml-stream *connection*)
"<stream:stream to='jabber.loglibrary.com'
xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams'
version='1.0'>"
* (xmpp:receive-stanza-loop *connection*)
Received: #<XML-ELEMENT STREAM:STREAM (4:0:0) {A9AF861}>
Received: #<XML-ELEMENT STREAM:FEATURES (0:2:0) {B3AA159}>

You can define xmpp:handle to get these replies programmatically, as
shown in the README.

Try these suggestions and let me know if you still can't get it to work.

Thanks,
Erik.


From adam.thorsen at gmail.com  Fri Nov 11 01:39:28 2005
From: adam.thorsen at gmail.com (Adam Thorsen)
Date: Thu, 10 Nov 2005 18:39:28 -0700
Subject: [cl-xmpp-devel] All calls return connection object
In-Reply-To: <58f839b70511101256v7301c03fw4c2ffcb1365b1c94@mail.gmail.com>
References: <290f54b70511100833j1ecd12eeu285d61b600cd5d00@mail.gmail.com>
	<58f839b70511101256v7301c03fw4c2ffcb1365b1c94@mail.gmail.com>
Message-ID: <290f54b70511101739k3d28ced3y40d8ebd69d00e46e@mail.gmail.com>

Erik, this is the code I use to initialize the connection, as is
suggested on common-lisp.net:

(require :cl-xmpp)

(defvar connection (xmpp:connect :hostname "jabber.loglibrary.com"))

;; initiate XML stream with server
(xmpp:begin-xml-stream connection)

;; authenticate (or use xmpp:register to make an account)
 (xmpp:auth connection "test" "whatever" "server")

;; let the server know you want to receive/send presence information
;; (this makes you "come online" if others have a subscription with
you
 (xmpp:presence connection)

I then execute this on the SLIME REPL:

CL-USER> (xmpp:message connection "awt at jabber.loglibrary.com" "what's
going on?")

However, I am still not recieving messages from test at jabber.loglibrary.com.

Is there some way I can find out what's happening?  Where the message
is getting lost or not transmitted?  Is there a simpler test I can
perform?

I swtiched (from the first email I sent) from SBCL 9.5 on OSX to SBCL
9.5 on Gentoo/x86 because I thought it might be a threading issue, but
no luck.

Thanks,
-Adam

On 11/10/05, Erik Enge <erik.enge at gmail.com> wrote:
> On 11/10/05, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> > All subsequent calls to the API seem only to return the connection
> > object, and accomplish nothing:
>
> This is the intended behavior.  I would like to print the actual XML
> sent to the server but presently CXML doesn't allow me to do that
> easily without writing my own binary stream which converts to
> characters and prints to a secondary character stream (eg
> *standard-output*) like broadcast streams do.  I would welcome such a
> patch.
>
> I didn't see a call to xmpp:auth, was that just a slip or are you not
> calling it?
>
> According to the RFCs, if you are interested in presence information,
> the recommended order is auth -> presence -> any messaging.
>
> Also, I don't see a call to xmpp:begin-xml-stream.  This is required
> as the first thing you do after xmpp:connect.  A good client should
> also call xmpp:end-xml-stream before calling close on the connection
> object.
>
> > None of the above actually seem to work (the account's buddy icon
> > doesn't appear to come online, and no messages are recieved from it.)
>
> To receive replies from the server, try xmpp:receive-stanza-loop and
> see what it returns to you.
>
> * (defparameter *connection* (xmpp:connect :hostname "jabber.loglibrary.com"))
> *CONNECTION*
> * (xmpp:begin-xml-stream *connection*)
> "<stream:stream to='jabber.loglibrary.com'
> xmlns='jabber:client'
> xmlns:stream='http://etherx.jabber.org/streams'
> version='1.0'>"
> * (xmpp:receive-stanza-loop *connection*)
> Received: #<XML-ELEMENT STREAM:STREAM (4:0:0) {A9AF861}>
> Received: #<XML-ELEMENT STREAM:FEATURES (0:2:0) {B3AA159}>
>
> You can define xmpp:handle to get these replies programmatically, as
> shown in the README.
>
> Try these suggestions and let me know if you still can't get it to work.
>
> Thanks,
> Erik.
>


From erik.enge at gmail.com  Fri Nov 11 02:39:49 2005
From: erik.enge at gmail.com (Erik Enge)
Date: Thu, 10 Nov 2005 21:39:49 -0500
Subject: [cl-xmpp-devel] All calls return connection object
In-Reply-To: <290f54b70511101739k3d28ced3y40d8ebd69d00e46e@mail.gmail.com>
References: <290f54b70511100833j1ecd12eeu285d61b600cd5d00@mail.gmail.com>
	<58f839b70511101256v7301c03fw4c2ffcb1365b1c94@mail.gmail.com>
	<290f54b70511101739k3d28ced3y40d8ebd69d00e46e@mail.gmail.com>
Message-ID: <58f839b70511101839j60070157sb08da49c951e1544@mail.gmail.com>

On 11/10/05, Adam Thorsen <adam.thorsen at gmail.com> wrote:
> Is there some way I can find out what's happening?  Where the message
> is getting lost or not transmitted?  Is there a simpler test I can
> perform?

I'm sitting here with telnet sessions open with both jabber.org and
jabber.loglibrary.com and getting wildly different results using the
same queries.  I wonder what version of jabber they are running at
loglibrary.com; perhaps the new version 2?  Whatever it is it works
with Adium but clearly not with cl-xmpp so I'd like to figure out
what's going wrong.

I don't have CVS access from this machines right now but I will make
some changes to the CVS version of cl-xmpp tomorrow which will help us
debug this.  To see if you get the same problem simply call
xmpp:receive-stanza-loop after your call to xmpp:auth and you should
see a xmpp:xmpp-protocol-error.  It's saying "feature-not-implemented"
but I don't know which feature; jabber.org has no problem with the XML
we're sending it.

I'll have more tomorrow.

Thanks,
Erik.


From erik.enge at gmail.com  Fri Nov 11 02:53:05 2005
From: erik.enge at gmail.com (Erik Enge)
Date: Thu, 10 Nov 2005 21:53:05 -0500
Subject: [cl-xmpp-devel] All calls return connection object
In-Reply-To: <58f839b70511101839j60070157sb08da49c951e1544@mail.gmail.com>
References: <290f54b70511100833j1ecd12eeu285d61b600cd5d00@mail.gmail.com>
	<58f839b70511101256v7301c03fw4c2ffcb1365b1c94@mail.gmail.com>
	<290f54b70511101739k3d28ced3y40d8ebd69d00e46e@mail.gmail.com>
	<58f839b70511101839j60070157sb08da49c951e1544@mail.gmail.com>
Message-ID: <58f839b70511101853p57accd51s98fe5f87c1c4c1cd@mail.gmail.com>

After a little more testing and breaking out tcpdump I can see what's
going on.  The fact that I have to use tcpdump to see what's being
sent back and forth is a huge sign that I need to improve the
debugability of cl-xmpp.  I already have code which makes it easier
and I'll add this to CVS tomorrow.

Ok, so what's going on?  jabber.loglibrary.com expects SASL
authentication and does not support non-sasl authentication (as
described in JEP0078).  cl-xmpp doesn't support SASL authentication so
that's our problem, however, I'm implementing TLS and SASL support
right now and should have this working and stable within the next few
days (I may be a little short on time so give me two or three days). 
I'll send an email to the mailinglist when I announce 0.6.0 which will
have all these fixes and TLS and SASL support.

Thanks,
Erik.


From erik.enge at gmail.com  Fri Nov 18 22:11:57 2005
From: erik.enge at gmail.com (Erik Enge)
Date: Fri, 18 Nov 2005 17:11:57 -0500
Subject: [cl-xmpp-devel] All calls return connection object
In-Reply-To: <58f839b70511101839j60070157sb08da49c951e1544@mail.gmail.com>
References: <290f54b70511100833j1ecd12eeu285d61b600cd5d00@mail.gmail.com>
	<58f839b70511101256v7301c03fw4c2ffcb1365b1c94@mail.gmail.com>
	<290f54b70511101739k3d28ced3y40d8ebd69d00e46e@mail.gmail.com>
	<58f839b70511101839j60070157sb08da49c951e1544@mail.gmail.com>
Message-ID: <58f839b70511181411t6b26c28ek575128691ac1c2aa@mail.gmail.com>

After much debugging SASL is now working and included in the 0.6 release.

Let me know if there are any issues.

Thanks,
Erik.