From reddaly at gmail.com  Fri Oct  2 01:23:01 2009
From: reddaly at gmail.com (Red Daly)
Date: Thu, 1 Oct 2009 18:23:01 -0700
Subject: [cl-twitter-devel] Unwind-protect to close sockets
Message-ID: <f6700f0c0910011823y709af86cyf139fcbb42474f47@mail.gmail.com>

this patch adds unwind-protect around the socket code to prevent a bunch of
loose sockets if there are exceptions.

-red
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-twitter-devel/attachments/20091001/d9b1576f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: red-unwind-protect-cl-twitter.patch
Type: application/octet-stream
Size: 3911 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/cl-twitter-devel/attachments/20091001/d9b1576f/attachment.obj>

From eslick at media.mit.edu  Mon Oct  5 17:06:03 2009
From: eslick at media.mit.edu (Ian Eslick)
Date: Mon, 5 Oct 2009 13:06:03 -0400
Subject: [cl-twitter-devel] Updates
Message-ID: <8D74343E-835D-4266-A114-BDCDAAE3D5CD@media.mit.edu>

I pushed two patches, one from Red Daly that ensures sockets get  
closed, and one from me which supports the new location fields and  
trending API.  There are a number of API change that the library  
hasn't tracked, I can provide pointers if anyone would like to update  
the API (should only be an hour or two).  Another great project would  
be to integrate cl-twitter with Leslie Polzer's oauth library.

Ian



From reddaly at gmail.com  Mon Oct  5 17:32:01 2009
From: reddaly at gmail.com (Red Daly)
Date: Mon, 5 Oct 2009 10:32:01 -0700
Subject: [cl-twitter-devel] Updates
In-Reply-To: <8D74343E-835D-4266-A114-BDCDAAE3D5CD@media.mit.edu>
References: <8D74343E-835D-4266-A114-BDCDAAE3D5CD@media.mit.edu>
Message-ID: <f6700f0c0910051032u32ce53eagdbbb49d1f6d5529b@mail.gmail.com>

I have also added support for OAuth authentication.  However, it uses a
custom version of cl-oauth so it might be messy to include this in the
official release.  I also have not merged with the latest tree, but I will
send a patch in at some point.

Red

On Mon, Oct 5, 2009 at 10:06 AM, Ian Eslick <eslick at media.mit.edu> wrote:

> I pushed two patches, one from Red Daly that ensures sockets get
> closed, and one from me which supports the new location fields and
> trending API.  There are a number of API change that the library
> hasn't tracked, I can provide pointers if anyone would like to update
> the API (should only be an hour or two).  Another great project would
> be to integrate cl-twitter with Leslie Polzer's oauth library.
>
> Ian
>
> _______________________________________________
> cl-twitter-devel mailing list
> cl-twitter-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-twitter-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-twitter-devel/attachments/20091005/128fd8d7/attachment.html>

From sky at viridian-project.de  Mon Oct  5 18:53:51 2009
From: sky at viridian-project.de (Leslie P. Polzer)
Date: Mon, 5 Oct 2009 20:53:51 +0200
Subject: [cl-twitter-devel] Updates
In-Reply-To: <f6700f0c0910051032u32ce53eagdbbb49d1f6d5529b@mail.gmail.com>
References: <8D74343E-835D-4266-A114-BDCDAAE3D5CD@media.mit.edu>
	<f6700f0c0910051032u32ce53eagdbbb49d1f6d5529b@mail.gmail.com>
Message-ID: <20091005185351.GB25749@viridian-project.de>

On Mon, Oct 05, 2009 at 10:32:01AM -0700, Red Daly wrote:
> I have also added support for OAuth authentication.  However, it uses a
> custom version of cl-oauth so it might be messy to include this in the
> official release.  I also have not merged with the latest tree, but I will
> send a patch in at some point.

Is there a special reason your custom changes to cl-oauth cannot be
merged into upstream?

  Leslie



From reddaly at gmail.com  Wed Oct  7 19:59:01 2009
From: reddaly at gmail.com (Red Daly)
Date: Wed, 7 Oct 2009 12:59:01 -0700
Subject: [cl-twitter-devel] Updates
In-Reply-To: <20091005185351.GB25749@viridian-project.de>
References: <8D74343E-835D-4266-A114-BDCDAAE3D5CD@media.mit.edu>
	<f6700f0c0910051032u32ce53eagdbbb49d1f6d5529b@mail.gmail.com>
	<20091005185351.GB25749@viridian-project.de>
Message-ID: <f6700f0c0910071259l989abex11f5e96076f176da@mail.gmail.com>

On Mon, Oct 5, 2009 at 11:53 AM, Leslie P. Polzer
<sky at viridian-project.de>wrote:

> On Mon, Oct 05, 2009 at 10:32:01AM -0700, Red Daly wrote:
> > I have also added support for OAuth authentication.  However, it uses a
> > custom version of cl-oauth so it might be messy to include this in the
> > official release.  I also have not merged with the latest tree, but I
> will
> > send a patch in at some point.
>
> Is there a special reason your custom changes to cl-oauth cannot be
> merged into upstream?
>
> No, you can have them all.  I just have not finished with the changes yet.



>  Leslie
>
>
Red

_______________________________________________
> cl-twitter-devel mailing list
> cl-twitter-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/cl-twitter-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/cl-twitter-devel/attachments/20091007/852fbfdc/attachment.html>