From burguzomo at hotmail.com  Thu Jul  3 14:09:13 2008
From: burguzomo at hotmail.com (Burguz Omonov)
Date: Thu, 3 Jul 2008 14:09:13 +0000
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
Message-ID: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>



Hey guys, I am giving cl-xmpp with usocket patch a try, and here's where it breaks:


machetto cl-xmpp # cat clxmpptest.lisp
(require :cl-xmpp)
(defvar *connection* (xmpp:connect :hostname "machetto"))
(xmpp:auth connection "user" "userpass" "res")
(xmpp:message connection "user2 at machetto" "ssup")
(xmpp:receive-stanza-loop connection)
machetto cl-xmpp #
...
sbcl --load clxmpptest.lisp

....

; registering # as USOCKET
; loading system definition from /root/.sbcl/systems/split-sequence.asd into
; #
; registering # as SPLIT-SEQUENCE

  when called with arguments
    (#S(CL-XMPP::SLOW-STREAM
        :TARGET #)).


Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.


Any hints? :)

_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx


From ehuels at gmail.com  Thu Jul  3 21:00:29 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Thu, 3 Jul 2008 23:00:29 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
Message-ID: <aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>

On Thu, Jul 3, 2008 at 4:09 PM, Burguz Omonov <burguzomo at hotmail.com> wrote:
>
>
> Hey guys, I am giving cl-xmpp with usocket patch a try, and here's where it breaks:
>
>
> machetto cl-xmpp # cat clxmpptest.lisp
> (require :cl-xmpp)
> (defvar *connection* (xmpp:connect :hostname "machetto"))
> (xmpp:auth connection "user" "userpass" "res")
> (xmpp:message connection "user2 at machetto" "ssup")
> (xmpp:receive-stanza-loop connection)
> machetto cl-xmpp #
> ...
> sbcl --load clxmpptest.lisp
>
> ....
>
> ; registering # as USOCKET
> ; loading system definition from /root/.sbcl/systems/split-sequence.asd into
> ; #
> ; registering # as SPLIT-SEQUENCE
>
>  when called with arguments
>    (#S(CL-XMPP::SLOW-STREAM
>        :TARGET #)).
>
>
> Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

Well, with your code I don't get very far (in my local network
"machetto" doesn't resolve), but when changing "machetto" to
"jabber.org", I run into a bug in your snippet above:

First you assign '*connection*' a value and after that you use
'connection' (note the lack of asterisks). Other than that, I'm unsure
what the problem can be: you're rather terse with the information
you're providing. The answers to a number of questions might help
resolve your issue:

- Which SBCL version?
- Which usocket version?
- Is "machetto" bound in your local network?
- Do you see the same error when using "jabber.org" as a server name?
- Did it work without the usocket patch?

Just some random questions to help figure out the issue :-)


Bye,

Erik.


From burguzomo at hotmail.com  Sun Jul  6 05:21:48 2008
From: burguzomo at hotmail.com (Burguz Omonov)
Date: Sun, 6 Jul 2008 05:21:48 +0000
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
Message-ID: <BAY135-W511C6C36104C8012055092AF950@phx.gbl>



Hello Erik! 
Thanks alot for your quick response. I played abit more with the code, still the same results with jabber.org. I think the code fails after receiving the first XML bundle from the xmpp server. (machetto is ejabberd v.2.0 that I had on loopback).

Here's the full snippet of the code that I am running as test now:

(require :cl-xmpp)
(defvar *connection* (xmpp:connect :hostname "jabber.org"))
(xmpp:auth *connection* "clxmpp" "clxmpp" "res")
(xmpp:message *connection* "burguzomo at gmail.com" "ssup")
(xmpp:receive-stanza-loop *connection*)

and the execution log I pasted here - http://paste.lisp.org/display/63329. I think the code still fails at the same place, something to do with cxml and sockets I guess. When using usocket patch, do I need to update any other packages ..? (trivial-gray-streams comes in mind)

 There is no applicable method for the generic function
    #
  when called with arguments
    (#S(CL-XMPP::SLOW-STREAM
        :TARGET #)).


The sbcl version is the 1.0.9-genttoo (v. 1.0.9 with gentoo patches). I simply installed it from gentoo's standard portage.

usocket version -  I am using 0.3.7 version of usocket. (installed with asdf-install). Here are the other packages/versions that I had installed:

machetto cl-xmpp # ls ~/.sbcl/site/
cl-base64-3.3.2            cxml-2007-10-21  trivial-gray-streams-2006-09-16
cl-sasl_0.3                ironclad_0.26    usocket-0.3.7
cl-xmpp                    puri-1.5.1
closure-common-2007-10-21  split-sequence
machetto cl-xmpp #

originally cl-xmpp installation using asdf-install failed due broken(?) link to trivial sockets page, so I installed all the packages manually one by one and then applied patch to installed version of cl-xmpp. (I couldn't install the trivial sockets, because I couldn't find a working mirror. any?)

I assumed that the example would work w/o usocket patch because this is basically the example from the cl-xmpp README file (I simply changed the usernames).


_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE


From david at lichteblau.com  Sun Jul  6 11:22:25 2008
From: david at lichteblau.com (David Lichteblau)
Date: Sun, 6 Jul 2008 13:22:25 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <BAY135-W511C6C36104C8012055092AF950@phx.gbl>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
Message-ID: <20080706112225.GA29844@radon>

Quoting Burguz Omonov (burguzomo at hotmail.com):
>     (#S(CL-XMPP::SLOW-STREAM
>         :TARGET #)).

http://common-lisp.net/pipermail/cl-xmpp-devel/2007-September/000089.html


From ehuels at gmail.com  Sun Jul  6 21:25:38 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Sun, 6 Jul 2008 23:25:38 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <20080706112225.GA29844@radon>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
Message-ID: <aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>

David,

On Sun, Jul 6, 2008 at 1:22 PM, David Lichteblau <david at lichteblau.com> wrote:
> Quoting Burguz Omonov (burguzomo at hotmail.com):
>>     (#S(CL-XMPP::SLOW-STREAM
>>         :TARGET #)).
>
> http://common-lisp.net/pipermail/cl-xmpp-devel/2007-September/000089.html

I was looking at the mailing list archives this morning when I tried
to answer the question by Burguz. I found that you have a git
repository with a mirror of cl-xmpp and some fixes to adjust it to
modern cxml.

Would you mind me asking for the commit-bit on the project, copying
over your changes to the CVS repository and also committing my usocket
change. Then, I could create a new _lastest.tgz release file. It might
actually help the project get back to life (or at least I hope so!).

Anybody else here with an opinion on the matter? Julian seems to have
maintained the project for a while, however hasn't done anything for a
while...

Bye,

Erik.


From ryan at acceleration.net  Mon Jul  7 15:53:32 2008
From: ryan at acceleration.net (Ryan Davis)
Date: Mon, 07 Jul 2008 11:53:32 -0400
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
Message-ID: <48723BFC.7080108@acceleration.net>

I would *love* to see this project get back to life.  I've been playing 
with it off and on for about a year with various levels of failure, and 
would really like a more solid base to work off than unofficial 
repository + unofficial patch.

Thanks,

Ryan Davis
Acceleration.net
Director of Programming Services
2831 NW 41st street, suite B
Gainesville, FL 32606

Office: 352-335-6500 x 124
Fax: 352-335-6506



Erik Huelsmann wrote:
> David,
>
> On Sun, Jul 6, 2008 at 1:22 PM, David Lichteblau <david at lichteblau.com> wrote:
>   
>> Quoting Burguz Omonov (burguzomo at hotmail.com):
>>     
>>>     (#S(CL-XMPP::SLOW-STREAM
>>>         :TARGET #)).
>>>       
>> http://common-lisp.net/pipermail/cl-xmpp-devel/2007-September/000089.html
>>     
>
> I was looking at the mailing list archives this morning when I tried
> to answer the question by Burguz. I found that you have a git
> repository with a mirror of cl-xmpp and some fixes to adjust it to
> modern cxml.
>
> Would you mind me asking for the commit-bit on the project, copying
> over your changes to the CVS repository and also committing my usocket
> change. Then, I could create a new _lastest.tgz release file. It might
> actually help the project get back to life (or at least I hope so!).
>
> Anybody else here with an opinion on the matter? Julian seems to have
> maintained the project for a while, however hasn't done anything for a
> while...
>
> Bye,
>
> Erik.
> _______________________________________________
> cl-xmpp-devel mailing list
> cl-xmpp-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-xmpp-devel
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-xmpp-devel/attachments/20080707/835a2134/attachment.html>

From green at redhat.com  Tue Jul  8 12:23:32 2008
From: green at redhat.com (Anthony Green)
Date: Tue, 08 Jul 2008 05:23:32 -0700
Subject: [cl-xmpp-devel] premature socket closure?
Message-ID: <48735C44.7060307@redhat.com>

I'm trying to use cl-xmpp with sbcl 1.0.18.  I've applied the ustream
patch as well as this one:
http://common-lisp.net/pipermail/cl-xmpp-devel/2007-September/000089.html

I can't seem to get the simplest connection going.   Any ideas?

Thanks!

Anthony Green


CL-USER> (defvar *connection* (xmpp:connect :hostname "jabber.org"))

<?xml version='1.0' ?><stream:stream to='jabber.org'
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
version='1.0'><?xml version='1.0'?version='1.0'><stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
id='3609488398' from='jabber.org' version='1.0'
xml:lang='en' 


UNHANDLED: #<XML-ELEMENT STREAM:STREAM (6attr:0child:0data)
{BB72571}>
; No value
CL-USER>


#<SB-SYS:FD-STREAM for "a socket" {BD33461}> is closed.
   [Condition of type SIMPLE-ERROR]

Restarts:
  0: [ABORT-REQUEST] Abort handling SLIME request.
  1: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread"
RUNNING {$

Backtrace:
  0: (SB-KERNEL:CLOSED-FLAME #<SB-SYS:FD-STREAM for "a socket"
{BD33461}>)[:EXT$
  1: (FORCE-OUTPUT #<SB-SYS:FD-STREAM for "a socket" {BD33461}>)
  2: (CL-XMPP::READ-STANZA #<CL-XMPP:CONNECTION to jabber.org:5222
(closed) {A7$
  3: ((SB-PCL::FAST-METHOD CL-XMPP:RECEIVE-STANZA (CL-XMPP:CONNECTION))
#<unava$
  4: (CL-XMPP:CONNECT)[:EXTERNAL]
  5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (CL-XMPP:CONNECT :HOSTNAME
"jabber.org") #<N$
  6: (SB-INT:SIMPLE-EVAL-IN-LEXENV (PROGN (CL-XMPP:CONNECT :HOSTNAME
"jabber.or$
  7: (SB-INT:SIMPLE-EVAL-IN-LEXENV (UNLESS (BOUNDP (QUOTE *CONNECTION*))
(CL-XM$
  8: (SB-INT:SIMPLE-EVAL-IN-LEXENV (SB-IMPL::%DEFVAR (QUOTE
*CONNECTION*) (UNLE$
  9: (SB-INT:SIMPLE-EVAL-IN-LEXENV (EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE)
(SB-IMP$
10: (SB-INT:SIMPLE-EVAL-IN-LEXENV (DEFVAR *CONNECTION* (CL-XMPP:CONNECT
:HOSTN$
--more-- 







From ehuels at gmail.com  Wed Jul  9 11:31:02 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Wed, 9 Jul 2008 13:31:02 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <48723BFC.7080108@acceleration.net>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
Message-ID: <aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>

On 7/7/08, Ryan Davis <ryan at acceleration.net> wrote:
> I would *love* to see this project get back to life.  I've been playing with
> it off and on for about a year with various levels of failure, and would
> really like a more solid base to work off than unofficial repository +
> unofficial patch.

Well, I've contacted the original author and my c-l.net account should
be set up now to include the cl-xmpp commit bit. So, we can start
working on a more lively project now.

Could you explain a bit more what it is that you're looking for from
your perspective? I mean, a more lively project has 2 components: (1)
a committer/maintainer and (2) visible/engaged users [who provide
feedback regarding what they're missing].

Does anybody here have anything they're missing, or are you just
experimenting with the library and running into problems so fast that
you're abandoning it immediately?


Regards,


Erik.


> Thanks,
> Ryan Davis
Acceleration.net
Director of Programming Services
2831 NW 41st
> street, suite B
Gainesville, FL 32606

Office: 352-335-6500 x 124
Fax:
> 352-335-6506
>
>
> Erik Huelsmann wrote:
> David,

On Sun, Jul 6, 2008 at 1:22 PM, David Lichteblau
> <david at lichteblau.com> wrote:

> Quoting Burguz Omonov (burguzomo at hotmail.com):

>  (#S(CL-XMPP::SLOW-STREAM
 :TARGET #)).

> http://common-lisp.net/pipermail/cl-xmpp-devel/2007-September/000089.html
> I was looking at the mailing list archives this morning when I tried
to
> answer the question by Burguz. I found that you have a git
repository with a
> mirror of cl-xmpp and some fixes to adjust it to
modern cxml.

Would you
> mind me asking for the commit-bit on the project, copying
over your changes
> to the CVS repository and also committing my usocket
change. Then, I could
> create a new _lastest.tgz release file. It might
actually help the project
> get back to life (or at least I hope so!).

Anybody else here with an
> opinion on the matter? Julian seems to have
maintained the project for a
> while, however hasn't done anything for
> a
while...

Bye,

Erik.
_______________________________________________
cl-xmpp-devel
> mailing
> list
cl-xmpp-devel at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-xmpp-devel

>
> _______________________________________________
> cl-xmpp-devel mailing list
> cl-xmpp-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-xmpp-devel
>
>


From ryan at acceleration.net  Wed Jul  9 13:52:19 2008
From: ryan at acceleration.net (Ryan Davis)
Date: Wed, 09 Jul 2008 09:52:19 -0400
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>	
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>	
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>	
	<20080706112225.GA29844@radon>	
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>	
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
Message-ID: <4874C293.2030309@acceleration.net>


Erik Huelsmann wrote:
> Could you explain a bit more what it is that you're looking for from
> your perspective? I mean, a more lively project has 2 components: (1)
> a committer/maintainer and (2) visible/engaged users [who provide
> feedback regarding what they're missing].
>
> Does anybody here have anything they're missing, or are you just
> experimenting with the library and running into problems so fast that
> you're abandoning it immediately?
>   
>
I've mostly been in the "abandoning it immediately" camp so far, 
spending a half day reading code trying to work through different bugs 
before having other obligations cut my investigations short.

Some things I'd like to use cl-xmpp for:

    * Personally:
          o home-automation that's remote controllable via XMPP (eg:
            download a file, what's the temperature, etc)
          o harasser/nagger chat-bot to help me get my chores done (eg:
            "Hey, it's been X days since you cleaned the damn litter
            box, suck it up")
          o get my growing collection of EEEpcs communicating with each
            other via XMPP  (possibly for experiments in erlang style
            distributed computing)
    * Professionally:
          o chat bot for the office chatroom (something like #lisp's
            minion over XMPP)
          o send notifications from our lisp intranet app to the office
            chatroom (eg: "payment added by Ryan: [link]", "contact info
            edited by Ryan [link]")

Currently I know of two things that have been issues for me:

   1. cl-xmpp and ejabberd not working well together (looks to be a
      patch here:
      http://common-lisp.net/pipermail/cl-xmpp-devel/2007-October/000098.html)
   2. figuring out the right combination of xmpp:connect-tls /
      xmpp:connect and :mechanism to connect to the office xmpp server,
      OpenFire
      (http://www.igniterealtime.org/projects/openfire/index.jsp).  This
      is a combination of my ignorance about the OpenFire config and
      lack of cl-xmpp documentation.
   3. The example on http://common-lisp.net/project/cl-xmpp/ doesn't
      work, uses "connection" where it means "*connection*".  This is a
      small thing, but I see it causing confusion on the mailing list
      every so often.

I would be happy in the visible/engaged users bit, possibly submitting 
documentation patches or small bug fixes depending on how my time goes.

Thanks,
Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-xmpp-devel/attachments/20080709/64403d46/attachment.html>

From kcrosbie at ravenpack.com  Wed Jul  9 14:30:25 2008
From: kcrosbie at ravenpack.com (Kevin Crosbie)
Date: Wed, 09 Jul 2008 16:30:25 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
Message-ID: <4874CB81.7060308@ravenpack.com>

Erik Huelsmann wrote:

> Well, I've contacted the original author and my c-l.net account should
> be set up now to include the cl-xmpp commit bit. So, we can start
> working on a more lively project now.
>
> Could you explain a bit more what it is that you're looking for from
> your perspective? I mean, a more lively project has 2 components: (1)
> a committer/maintainer and (2) visible/engaged users [who provide
> feedback regarding what they're missing].
>
> Does anybody here have anything they're missing, or are you just
> experimenting with the library and running into problems so fast that
> you're abandoning it immediately?
>   

I contributed some code that hasn't made it's way into the main codebase 
yet:
http://common-lisp.net/pipermail/cl-xmpp-devel/2007-December/000111.html

I've had quite a lot of success using cl-xmpp with ejabberd, we're 
currently using the latest version of the server with a few patches applied:
http://common-lisp.net/pipermail/cl-xmpp-devel/2007-October/000097.html

Kevin.




From ehuels at gmail.com  Wed Jul  9 21:20:50 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Wed, 9 Jul 2008 23:20:50 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <4874CB81.7060308@ravenpack.com>
References: <4874CB81.7060308@ravenpack.com>
Message-ID: <aea328ab0807091420x367ae9bene98d206d8906b31@mail.gmail.com>

On Wed, Jul 9, 2008 at 4:30 PM, Kevin Crosbie <kcrosbie at ravenpack.com> wrote:
> Erik Huelsmann wrote:
>
>> Well, I've contacted the original author and my c-l.net account should
>> be set up now to include the cl-xmpp commit bit. So, we can start
>> working on a more lively project now.
>>
>> Could you explain a bit more what it is that you're looking for from
>> your perspective? I mean, a more lively project has 2 components: (1)
>> a committer/maintainer and (2) visible/engaged users [who provide
>> feedback regarding what they're missing].
>>
>> Does anybody here have anything they're missing, or are you just
>> experimenting with the library and running into problems so fast that
>> you're abandoning it immediately?
>>
>
> I contributed some code that hasn't made it's way into the main codebase
> yet:
> http://common-lisp.net/pipermail/cl-xmpp-devel/2007-December/000111.html

I found your changes and committed them into the CVS repository as
well as the 2 changes in David's Git repository.

After committing your patches verbatim (except for the conflicts which
I needed to resolve), I tweaked a defconstant into a defparameter.
Generally it's considered bad form to declare strings as constants: it
doesn't work cross implementation without specific precautions.


> I've had quite a lot of success using cl-xmpp with ejabberd, we're currently
> using the latest version of the server with a few patches applied:
> http://common-lisp.net/pipermail/cl-xmpp-devel/2007-October/000097.html

That's great to hear!

Regards,

Erik.


From ehuels at gmail.com  Wed Jul  9 21:26:06 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Wed, 9 Jul 2008 23:26:06 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <4874C293.2030309@acceleration.net>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<4874C293.2030309@acceleration.net>
Message-ID: <aea328ab0807091426v11d92e42j1713888230532eea@mail.gmail.com>

Hi Ryan,

> I've mostly been in the "abandoning it immediately" camp so far, spending a
> half day reading code trying to work through different bugs before having
> other obligations cut my investigations short.

That's too bad. Which (lisp) implementation do you use? I checked
today's commits using SBCL.

> Some things I'd like to use cl-xmpp for:
>
> Personally:
>
> home-automation that's remote controllable via XMPP (eg: download a file,
> what's the temperature, etc)
> harasser/nagger chat-bot to help me get my chores done (eg: "Hey, it's been
> X days since you cleaned the damn litter box, suck it up")
> get my growing collection of EEEpcs communicating with each other via XMPP
> (possibly for experiments in erlang style distributed computing)

Nice :-)

> Professionally:
>
> chat bot for the office chatroom (something like #lisp's minion over XMPP)
> send notifications from our lisp intranet app to the office chatroom (eg:
> "payment added by Ryan: [link]", "contact info edited by Ryan [link]")
>
> Currently I know of two things that have been issues for me:
>
> cl-xmpp and ejabberd not working well together (looks to be a patch here:
> http://common-lisp.net/pipermail/cl-xmpp-devel/2007-October/000098.html)

Yes, I need to look into this one, because not everybody may have
control over the jabber server they're using. One of the messages in
that thread contains a fix for ejabberd (not cl-xmpp...).

> figuring out the right combination of xmpp:connect-tls / xmpp:connect and
> :mechanism to connect to the office xmpp server, OpenFire
> (http://www.igniterealtime.org/projects/openfire/index.jsp).  This is a
> combination of my ignorance about the OpenFire config and lack of cl-xmpp
> documentation.

If you could be more elaborate about what you'd like to see or know, I
can probably explain what cl-xmpp is doing.

> The example on http://common-lisp.net/project/cl-xmpp/ doesn't work, uses
> "connection" where it means "*connection*".  This is a small thing, but I
> see it causing confusion on the mailing list every so often.

Ok. Fixed that, should be on the website correctly now. (Except that I
named the variable 'connection' because that was a smaller change...)

> I would be happy in the visible/engaged users bit, possibly submitting
> documentation patches or small bug fixes depending on how my time goes.

That would be absolutely great!

Code contributions as examples or test-cases are also extremely welcome, btw.

Regards,

Erik.


From ehuels at gmail.com  Wed Jul  9 21:28:42 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Wed, 9 Jul 2008 23:28:42 +0200
Subject: [cl-xmpp-devel] New cl-xmpp release
Message-ID: <aea328ab0807091428q188caf89u65753222a01906ff@mail.gmail.com>

Tonight I moved over the fixes from David Lichtblau and my usocket
patch into CVS and made a release based on it.

Hopefully, this one works better for some of you, please provide me
with your experiences!

After doing the release, I committed the Ravenpack.com patch. If you
want to test the extended APIs, please check out CVS.

Regards,

Erik.


From kcrosbie at ravenpack.com  Thu Jul 10 08:11:34 2008
From: kcrosbie at ravenpack.com (Kevin Crosbie)
Date: Thu, 10 Jul 2008 10:11:34 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807091420x367ae9bene98d206d8906b31@mail.gmail.com>
References: <4874CB81.7060308@ravenpack.com>
	<aea328ab0807091420x367ae9bene98d206d8906b31@mail.gmail.com>
Message-ID: <4875C436.9050908@ravenpack.com>

Erik Huelsmann wrote:
> I found your changes and committed them into the CVS repository as
> well as the 2 changes in David's Git repository.
>
> After committing your patches verbatim (except for the conflicts which
> I needed to resolve), I tweaked a defconstant into a defparameter.
> Generally it's considered bad form to declare strings as constants: it
> doesn't work cross implementation without specific precautions.
>   
Great!   I definitely agree with the change you made.
Thanks, it's nice to see this project revived.

Kevin


From burguzomo at hotmail.com  Fri Jul 11 03:57:13 2008
From: burguzomo at hotmail.com (Burguz Omonov)
Date: Fri, 11 Jul 2008 03:57:13 +0000
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net> 
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
Message-ID: <BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>



>
> Well, I've contacted the original author and my c-l.net account should
> be set up now to include the cl-xmpp commit bit. So, we can start
> working on a more lively project now.
>
> Could you explain a bit more what it is that you're looking for from
> your perspective? I mean, a more lively project has 2 components: (1)
> a committer/maintainer and (2) visible/engaged users [who provide
> feedback regarding what they're missing].

Something that I'd love to see on the project page would be a list of tested platforms/environments (i.e. compiler + libraries combination). Also maybe compatible, or incompatible servers. I am still testing the recent update. 

I think it'd be good to have some sort of "getting started" sections on the project web page for different environments too. I'd be willing to contribute some of my experience here. 

> Does anybody here have anything they're missing, or are you just
> experimenting with the library and running into problems so fast that
> you're abandoning it immediately?
>

To me is closer to the 2nd point, with the only difference that I hope to get it working one day, because otherwise you'd need to integrate lisp with other languages, which can provide working xmpp support, and that'd be opening another jug of worms.  :)

 So far I've been testing cl-xmpp with clisp and sbcl. With clisp I simply can't get the stuff to run (cuz asdf-install is also broken under clisp, and I was having problems simply installing and loading package properly). with sbcl, which i am more familiar with, I am able to get to the point that the package compiles properly, but as I mentioned in my earlier message (forgot to cc it to the list), the script still spits error during the authentication phase.

clxmppclxmppresssup
debugger invoked on a CL-XMPP:SERVER-DISCONNECT:
  Document not well-formed: Bad nesting. "stream:stream" / (:EOF)

That's been my experience so far :) I'll keep it posted, if I manage to get somehow better results.


_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us


From ehuels at gmail.com  Fri Jul 11 09:13:18 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Fri, 11 Jul 2008 11:13:18 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
Message-ID: <aea328ab0807110213o2eb5cb34s9d7f4d39f8f52164@mail.gmail.com>

> > Could you explain a bit more what it is that you're looking for from
> > your perspective? I mean, a more lively project has 2 components: (1)
> > a committer/maintainer and (2) visible/engaged users [who provide
> > feedback regarding what they're missing].
>
> Something that I'd love to see on the project page would be a list of tested platforms/environments (i.e. compiler + libraries combination). Also maybe compatible, or incompatible servers. I am still testing the recent update.

Well, that's a very limited list for now, but if you're here willing
to help extend the list (by means of testing in your setup(s)) that'd
be great!

> I think it'd be good to have some sort of "getting started" sections on the project web page for different environments too. I'd be willing to contribute some of my experience here.

That would be much appreciated. If you have any text to donate, I can
put it up on the webpage. If you get involved more, it should be
possible to arrange commit access for you as well.

> > Does anybody here have anything they're missing, or are you just
> > experimenting with the library and running into problems so fast that
> > you're abandoning it immediately?

> To me is closer to the 2nd point, with the only difference that I hope to get it working one day, because otherwise you'd need to integrate lisp with other languages, which can provide working xmpp support, and that'd be opening another jug of worms.  :)

Well, I think we should be able to make it work, especially when this
is taken up as a shared effort.

>  So far I've been testing cl-xmpp with clisp and sbcl. With clisp I simply can't get the stuff to run (cuz asdf-install is also broken under clisp, and I was having problems simply installing and loading package properly). with sbcl, which i am more familiar with, I am able to get to the point that the package compiles properly, but as I mentioned in my earlier message (forgot to cc it to the list), the script still spits error during the authentication phase.

> clxmppclxmppresssup
> debugger invoked on a CL-XMPP:SERVER-DISCONNECT:
>  Document not well-formed: Bad nesting. "stream:stream" / (:EOF)

What would be interesting is: did the remote close the connection? And
if so, what was sent over the stream that may cause cl-xmpp to think
the input was not well formed? Could you record the connection session
and put a transcript of it online? That would save me a lot of time.

> That's been my experience so far :) I'll keep it posted, if I manage to get somehow better results.

Well, together we should be able to get to better results than that
:-) That's rather useless.


Bye,

Erik.


From kcrosbie at ravenpack.com  Fri Jul 11 09:45:14 2008
From: kcrosbie at ravenpack.com (Kevin Crosbie)
Date: Fri, 11 Jul 2008 11:45:14 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>	<20080706112225.GA29844@radon>	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
Message-ID: <48772BAA.7070407@ravenpack.com>

Burguz Omonov wrote:
> clxmppclxmppresssup
> debugger invoked on a CL-XMPP:SERVER-DISCONNECT:
>   Document not well-formed: Bad nesting. "stream:stream" / (:EOF)
>
> That's been my experience so far :) I'll keep it posted, if I manage to get somehow better results.
>
>   
We fixed that problem by patching ejabberd. Have you tried that?
http://common-lisp.net/pipermail/cl-xmpp-devel/2007-October/000097.html

Basically the patch removes the XML tag from the start of the stream.

I'm not sure that this is the ultimate solution, the guys at ejabberd
suggest that the cl-xmpp should be handling this properly, but the patch
is an intermediate solution at least:
https://support.process-one.net/browse/EJAB-455?focusedCommentId=17503#action_17503

Kevin


From ehuels at gmail.com  Fri Jul 11 11:21:24 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Fri, 11 Jul 2008 13:21:24 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <48772BAA.7070407@ravenpack.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
	<48772BAA.7070407@ravenpack.com>
Message-ID: <aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com>

On 7/11/08, Kevin Crosbie <kcrosbie at ravenpack.com> wrote:
> Burguz Omonov wrote:
> > clxmppclxmppresssup
> > debugger invoked on a CL-XMPP:SERVER-DISCONNECT:
> >   Document not well-formed: Bad nesting. "stream:stream" / (:EOF)
> >
> > That's been my experience so far :) I'll keep it posted, if I manage to get somehow better results.
> >
> >
> We fixed that problem by patching ejabberd. Have you tried that?
> http://common-lisp.net/pipermail/cl-xmpp-devel/2007-October/000097.html
>
> Basically the patch removes the XML tag from the start of the stream.

Well, when looking at the output in the bugreport mentioned below,
there is a difference: in the output reported by Burguz, there's an
:EOF (end-of-stream), whereas in your bugreport I can see the XML
processing instruction to set the xml version number. So, while the
error looks very much alike, they may be different issues.


> I'm not sure that this is the ultimate solution, the guys at ejabberd
> suggest that the cl-xmpp should be handling this properly, but the patch
> is an intermediate solution at least:
> https://support.process-one.net/browse/EJAB-455?focusedCommentId=17503#action_17503

Thanks for the pointer!

Bye,

Erik.


From david at lichteblau.com  Fri Jul 11 12:08:56 2008
From: david at lichteblau.com (David Lichteblau)
Date: Fri, 11 Jul 2008 14:08:56 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
	<48772BAA.7070407@ravenpack.com>
	<aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com>
Message-ID: <20080711120856.GF29115@radon>

Quoting Erik Huelsmann (ehuels at gmail.com):
> Well, when looking at the output in the bugreport mentioned below,
> there is a difference: in the output reported by Burguz, there's an
> :EOF (end-of-stream), whereas in your bugreport I can see the XML
> processing instruction to set the xml version number. So, while the
> error looks very much alike, they may be different issues.

Yeah, that sounds like a plain end-of-file situation, where the server
closed the connection.

That's why it's not very helpful to see just the error message.  Please
show complete test code, so that errors in that code can be pointed out.

For example, the code on the web page uses DEFVAR rather than
DEFPARAMETER, meaning that a second attempt to run the same code will
actually continue to use the old *connection* value, which will usually
have died due to a timeout by then.

> > I'm not sure that this is the ultimate solution, the guys at ejabberd
> > suggest that the cl-xmpp should be handling this properly, but the patch
> > is an intermediate solution at least:
> > https://support.process-one.net/browse/EJAB-455?focusedCommentId=17503#action_17503
> 
> Thanks for the pointer!

No, as I already pointed out to Erik in PM, the git archive (and by now
presumably CVS, too) has the right fix for this.  Please ignore the
bogus ejabberd change.  I'm not aware of any remaining stream reset
issues in current cl-xmpp that would affect ejabberd.


d.


From burguzomo at hotmail.com  Fri Jul 11 18:49:29 2008
From: burguzomo at hotmail.com (Burguz Omonov)
Date: Fri, 11 Jul 2008 18:49:29 +0000
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <20080711120856.GF29115@radon>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807031400t79a37f2ckb38148466b00645c@mail.gmail.com>
	<BAY135-W511C6C36104C8012055092AF950@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
	<48772BAA.7070407@ravenpack.com>
	<aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com> 
	<20080711120856.GF29115@radon>
Message-ID: <BAY135-W25639102617A5C150076FCAF900@phx.gbl>


Hi guys,
 Sorry, the hotmail broke the xml content in my previous messages. I posted the full execution log and the packet content as it was posted over the wire, here:
 
http://paste.lisp.org/display/63550
 
I tested it both with jabber server (the ID and password inside the script are actual ID and password that I used) and local ejabber server, and I am getting the same output in both cases.
 
For some reason the server responds with error code 503/service unavailable to authentication request with the script, while I am able to successefully login using regular jabber client or a small client that I wrote using gloox library.  I'll probably need to compare how different the actual requests look on the wire..
 
> Yeah, that sounds like a plain end-of-file situation, where the server> closed the connection.> > That's why it's not very helpful to see just the error message. Please> show complete test code, so that errors in that code can be pointed out.
(require :cl-xmpp)(defparameter *connection* (xmpp:connect :hostname "jabber.org"))(xmpp:auth *connection* "clxmpp" "clxmpp" "res")(xmpp:message *connection* "fygrave at gmail.com" "ssup")(xmpp:receive-stanza-loop *connection*)
I used both defparameter and defvar here. Doesn't change the situation much.
 
_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-xmpp-devel/attachments/20080711/c4880c66/attachment.html>

From ehuels at gmail.com  Fri Jul 11 22:47:22 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Sat, 12 Jul 2008 00:47:22 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <BAY135-W25639102617A5C150076FCAF900@phx.gbl>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<20080706112225.GA29844@radon>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
	<48772BAA.7070407@ravenpack.com>
	<aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com>
	<20080711120856.GF29115@radon>
	<BAY135-W25639102617A5C150076FCAF900@phx.gbl>
Message-ID: <aea328ab0807111547i3f313d70gbef71f4dc804624e@mail.gmail.com>

On Fri, Jul 11, 2008 at 8:49 PM, Burguz Omonov <burguzomo at hotmail.com> wrote:
> Hi guys,
>  Sorry, the hotmail broke the xml content in my previous messages. I posted
> the full execution log and the packet content as it was posted over the
> wire, here:
>
> http://paste.lisp.org/display/63550
>
> I tested it both with jabber server (the ID and password inside the script
> are actual ID and password that I used) and local ejabber server, and I am
> getting the same output in both cases.
>
> For some reason the server responds with error code 503/service unavailable
> to authentication request with the script, while I am able to successefully
> login using regular jabber client or a small client that I wrote using gloox
> library.  I'll probably need to compare how different the actual requests
> look on the wire..
>
>> Yeah, that sounds like a plain end-of-file situation, where the server
>> closed the connection.
>>
>> That's why it's not very helpful to see just the error message. Please
>> show complete test code, so that errors in that code can be pointed out.
>
> (require :cl-xmpp)
> (defparameter *connection* (xmpp:connect :hostname "jabber.org"))
> (xmpp:auth *connection* "clxmpp" "clxmpp" "res")
> (xmpp:message *connection* "fygrave at gmail.com" "ssup")
> (xmpp:receive-stanza-loop *connection*)
>
> I used both defparameter and defvar here. Doesn't change the situation much.

No, the problem is with the protocol that cl-xmpp uses to get you
authenticated: looking at the output, it's using an auth2 tag, but
when reading rfc3920 there definitely is no auth2 tag; also, the rfc
requires the use of SASL for actual authentication, whereas your code
(and the library) don't.

However, using (require :cl-xmpp-sasl) alone doesn't do the trick. So,
I'm now trying to figure out how the SASL code is meant to be used.

One problem I spotted already is the fact that the allowed
auth-mechanisms are not cached/remembered anywhere, meaning that
actually choosing one (versus hard-coding) isn't possible now. I
believe that the connection APIs may need to be rewritten to support
the RFC completely.

I hope that explains a bit why you're seeing these problems.

Bye,

Erik.


From ehuels at gmail.com  Sat Jul 12 06:24:38 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Sat, 12 Jul 2008 08:24:38 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807111547i3f313d70gbef71f4dc804624e@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<aea328ab0807061425w43ebad73na4b96215117cf7bb@mail.gmail.com>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
	<48772BAA.7070407@ravenpack.com>
	<aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com>
	<20080711120856.GF29115@radon>
	<BAY135-W25639102617A5C150076FCAF900@phx.gbl>
	<aea328ab0807111547i3f313d70gbef71f4dc804624e@mail.gmail.com>
Message-ID: <aea328ab0807112324m70d5543fq2ce9cdde1a7526a1@mail.gmail.com>

On Sat, Jul 12, 2008 at 12:47 AM, Erik Huelsmann <ehuels at gmail.com> wrote:
> On Fri, Jul 11, 2008 at 8:49 PM, Burguz Omonov <burguzomo at hotmail.com> wrote:
>> Hi guys,
>>  Sorry, the hotmail broke the xml content in my previous messages. I posted
>> the full execution log and the packet content as it was posted over the
>> wire, here:
>>
>> http://paste.lisp.org/display/63550

Well, by using

(require :cl-xmpp-sasl)
...
(xmpp:auth *connection* "clxmpp" "clxmpp" "res" :mechanism :sasl-plain)

instead of what you have in the paste, I got further, but that's not
to say that I got there. Now I actually got to the point where CXML
reports a stream-non-conformance, just as reported before.

Given the fact that I ported all of David's changes from his Git
archive, I don't understand yet why I see that error. However, to get
full grasp I have to do further reseach for which there's no time
today. I'll keep you posted.

Bye,

Erik.


From ehuels at gmail.com  Sat Jul 12 08:26:53 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Sat, 12 Jul 2008 10:26:53 +0200
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807112324m70d5543fq2ce9cdde1a7526a1@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
	<48772BAA.7070407@ravenpack.com>
	<aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com>
	<20080711120856.GF29115@radon>
	<BAY135-W25639102617A5C150076FCAF900@phx.gbl>
	<aea328ab0807111547i3f313d70gbef71f4dc804624e@mail.gmail.com>
	<aea328ab0807112324m70d5543fq2ce9cdde1a7526a1@mail.gmail.com>
Message-ID: <aea328ab0807120126m41ac57d3x3ce882f8496a9362@mail.gmail.com>

On Sat, Jul 12, 2008 at 8:24 AM, Erik Huelsmann <ehuels at gmail.com> wrote:
> On Sat, Jul 12, 2008 at 12:47 AM, Erik Huelsmann <ehuels at gmail.com> wrote:
>> On Fri, Jul 11, 2008 at 8:49 PM, Burguz Omonov <burguzomo at hotmail.com> wrote:
>>> Hi guys,
>>>  Sorry, the hotmail broke the xml content in my previous messages. I posted
>>> the full execution log and the packet content as it was posted over the
>>> wire, here:
>>>
>>> http://paste.lisp.org/display/63550
>
> Well, by using
>
> (require :cl-xmpp-sasl)
> ...
> (xmpp:auth *connection* "clxmpp" "clxmpp" "res" :mechanism :sasl-plain)
>
> instead of what you have in the paste, I got further, but that's not
> to say that I got there. Now I actually got to the point where CXML
> reports a stream-non-conformance, just as reported before.

I found the problem: if you use CVS HEAD, then the problem is gone. (I
was testing with 0.8.0...)

Looks like one of the fixes I *thought* to have resolved with 0.8.0
will need a 0.8.1 release to really fix it.

Bye,

Erik.


From ehuels at gmail.com  Sat Jul 12 17:04:06 2008
From: ehuels at gmail.com (Erik Huelsmann)
Date: Sat, 12 Jul 2008 19:04:06 +0200
Subject: [cl-xmpp-devel] Website updated and 0.8.1 released
Message-ID: <aea328ab0807121004x21d00181t47960fc80696bb55@mail.gmail.com>

As it turned out, 0.8.0 missed one essential fix which would cause
CXML errors when using cl-xmpp-sasl. This fix is now included in
0.8.1.

Also, I updated the website to give an example with jabber.org which
works if used with the right password and user settings (instead of
the old one which doesn't work with jabber - not even with the right
password and username).

Bye,

Erik.


From burguzomo at hotmail.com  Sun Jul 13 05:14:20 2008
From: burguzomo at hotmail.com (Burguz Omonov)
Date: Sun, 13 Jul 2008 05:14:20 +0000
Subject: [cl-xmpp-devel] Website updated and 0.8.1 released
In-Reply-To: <aea328ab0807121004x21d00181t47960fc80696bb55@mail.gmail.com>
References: <aea328ab0807121004x21d00181t47960fc80696bb55@mail.gmail.com>
Message-ID: <BAY135-W123439865F9367FDCC5305AF920@phx.gbl>


Sorry for silly question - were the patches committed to CVS? because I am cvs-up'ing the CVS tree and I don't see any changes compared to the code that I sync'ed on Jul 10th.  
 
I saw the updated example thu, I am going to run my test code with xmpp-sasl now.> Date: Sat, 12 Jul 2008 19:04:06 +0200> From: ehuels at gmail.com> To: cl-xmpp-devel at common-lisp.net> Subject: [cl-xmpp-devel] Website updated and 0.8.1 released> > As it turned out, 0.8.0 missed one essential fix which would cause> CXML errors when using cl-xmpp-sasl. This fix is now included in> 0.8.1.> > Also, I updated the website to give an example with jabber.org which> works if used with the right password and user settings (instead of> the old one which doesn't work with jabber - not even with the right> password and username).> > Bye,> > Erik.> _______________________________________________> cl-xmpp-devel mailing list> cl-xmpp-devel at common-lisp.net> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-xmpp-devel
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-xmpp-devel/attachments/20080713/ded0d419/attachment.html>

From burguzomo at hotmail.com  Sun Jul 13 06:51:25 2008
From: burguzomo at hotmail.com (Burguz Omonov)
Date: Sun, 13 Jul 2008 06:51:25 +0000
Subject: [cl-xmpp-devel] cl-xmpp with usocket patch
In-Reply-To: <aea328ab0807120126m41ac57d3x3ce882f8496a9362@mail.gmail.com>
References: <BAY135-W891E1461B6619B2D2C300AF980@phx.gbl>
	<48723BFC.7080108@acceleration.net>
	<aea328ab0807090431k62c172a3m5956de8c43789834@mail.gmail.com>
	<BAY135-W3327D67ABA77CFCD730E4BAF900@phx.gbl>
	<48772BAA.7070407@ravenpack.com>
	<aea328ab0807110421l19499d3u67b87d9eef9299cb@mail.gmail.com>
	<20080711120856.GF29115@radon>
	<BAY135-W25639102617A5C150076FCAF900@phx.gbl>
	<aea328ab0807111547i3f313d70gbef71f4dc804624e@mail.gmail.com>
	<aea328ab0807112324m70d5543fq2ce9cdde1a7526a1@mail.gmail.com> 
	<aea328ab0807120126m41ac57d3x3ce882f8496a9362@mail.gmail.com>
Message-ID: <BAY135-W38E93E2B56CF8BC7562D88AF920@phx.gbl>


> > instead of what you have in the paste, I got further, but that's not> > to say that I got there. Now I actually got to the point where CXML> > reports a stream-non-conformance, just as reported before.> > I found the problem: if you use CVS HEAD, then the problem is gone. (I> was testing with 0.8.0...)> 
 
ooops.. ok, this answers the question in my previous email. (sorry, been reading the posts backwards). Testing the code now!
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-xmpp-devel/attachments/20080713/2c36cd88/attachment.html>