2009/3/14 Chun Tian (binghe) :
> 0.4.x branch act the same as trunk. I don't see any different when running
> hunchentoot.
Thank you! Erik, if you could release usocket, it'd be great.
Cheers,
Hans
___
usocket-devel mailing list
usocket-devel@common-l
0.4.x branch act the same as trunk. I don't see any different when
running hunchentoot.
(I don't have any real applications on hunchentoot)
On 2009-3-14, at 19:56, Hans Hübner wrote:
> Hi Binghe,
>
> thank you for testing, but what we need is someone who tests
> Hunchentoot with usocket 0.4.
>
Hi Binghe,
thank you for testing, but what we need is someone who tests
Hunchentoot with usocket 0.4.
-Hans
2009/3/14 Chun Tian (binghe) :
> Hi, Hans
>
> I just took a little time testing Hunchentoot 1.0 on SBCL (1.0.25) and CCL
> (1.3 RC1, 64-bit), both running on Mac OS X.
>
> It seems that Hu
Hi, Hans
I just took a little time testing Hunchentoot 1.0 on SBCL (1.0.25) and
CCL (1.3 RC1, 64-bit), both running on Mac OS X.
It seems that Hunchentoot works well under usocket trunk, and all
hunchentoot tests except the ("Easy" handler example) has been passed.
I believe the one not pas
On Sat, Mar 14, 2009 at 09:32, Erik Huelsmann wrote:
> Should I release 0.4.2?
Before doing that, I'd like to know whether Hunchentoot 1.0 runs with
it. I don't have the time to do that right now, so if anyone would
like to volunteer, it'd be great. I'd be satisfied to see the
Hunchentoot conf
On Sat, Mar 14, 2009 at 7:58 AM, Hans Hübner wrote:
> On Sat, Mar 14, 2009 at 07:56, Hans Hübner wrote:
>> This problem is fixed in usocket-trunk, but has not made it into the
>> 0.4 release branch. I will update the ediware version to include it.
>
> In fact, the ediware repository already pull
On Fri, Mar 13, 2009 at 21:45, Andrei Stebakov wrote:
> When executing
> (let ((*break-on-signals* 'error))
> (usocket:socket-connect "lisp.org" 80))
>
> I have an error:
> junk in string "org"
> BREAK was entered because of *BREAK-ON-SIGNALS* (now rebound to NIL).
> [Condition of type SIMPLE-C
On Sat, Mar 14, 2009 at 07:56, Hans Hübner wrote:
> This problem is fixed in usocket-trunk, but has not made it into the
> 0.4 release branch. I will update the ediware version to include it.
In fact, the ediware repository already pulled usocket-trunk, so by
checking out either
svn://common-lis
When executing
(let ((*break-on-signals* 'error))
(usocket:socket-connect "lisp.org" 80))
I have an error:
junk in string "org"
BREAK was entered because of *BREAK-ON-SIGNALS* (now rebound to NIL).
[Condition of type SIMPLE-CONDITION]
Restarts:
0: [CONTINUE] Return from BREAK.
1: [REASSIGN
