Hi, Terje
USOCKET Support on MCL (at least RMCL) is already in my plan. There're some higher priority tasks on USOCKET side, like full support of SBCL and ECL on win32, etc., and every USOCKET maintainer is busy working on other projects (ABCL, BKNR, ...). So if MCL users can wait, I promise the MCL backend of USOCKET will be coming in *no later than a month*, or if someone here is interested in helping us, patches are most welcome.
--binghe
> Does somebody know of an MCL backend for the USOCKET portable tcp/ip
> socket interface?
>
> http://common-lisp.net/project/usocket/
>
> -- Terje Norderhaug
> terje(a)in-progress.com
>
>
>
>
> _______________________________________________
> info-mcl mailing list
> info-mcl(a)clozure.com
> http://clozure.com/mailman/listinfo/info-mcl
Hi, there
I just built out a ECL binary on MSVC, now I'm starting looking into this issue. ECL team maintains a really good code base on all supported platforms ...
--binghe
> Ive actually done that and hunchentoot displays nothing on the simple test
> website. Oh well... Let me know how your test of the 'patch' goes...
>
> -----Original Message-----
> From: Chun Tian (binghe) [mailto:binghe.lisp@gmail.com]
> Sent: Tuesday, December 29, 2009 2:33 AM
> To: Seth Burleigh
> Subject: Re: [usocket-devel] ECL and MSVC
>
> As I know these test code never been used for long time, we're working on
> bring them back ...
>
> I think you should use a real networking package which built upon USOCKET,
> i.e. hunchentoot
>
> --binghe
>
> 在 2009-12-29，01:43， Seth Burleigh 写道：
>
>> Perhaps im doing these tests wrong since I really have never used sockets.
>> All I did was load the usocket-test.asd and go (usocket:run-usocket-tests)
>> If im reading the code right, it attempt to make a connection on 127.0.0.0
>> at port 15213 for the first test. Surely there has to be something
> listening
>> for it in order for it to receive it correctly? Using commview and the
>> loopback sniffer, no activity is reported at 127.0.0.0.
>>
>>
>> -----Original Message-----
>> From: Chun Tian (binghe) [mailto:binghe.lisp@gmail.com]
>> Sent: Monday, December 28, 2009 10:19 AM
>> To: Seth Burleigh
>> Subject: Re: [usocket-devel] ECL and MSVC
>>
>> Hi, Seth
>>
>> Thanks for these tests. I suggest you using WireShark (or something else
>> eq. to "tcpdump") to try to capture if there's really IP packets sent out
> by
>> USOCKET functions. If USOCKET really send them, things should be easier
>> then.
>>
>> --binghe
>>
>> 在 2009-12-28，23:26， Seth Burleigh 写道：
>>
>>> Hmm.. I tried testing it on clisp and ecl. On ecl it failed 13/15 times.
>> On
>>> clisp , currently, it has failed the first 3 tests with timeout errors.
> I
>>> even had clisp running with admin rights. Maybe it’s the firewall or my
>>> win7 operating system. I"ll have to look into this deeper.
>>>
>>> -----Original Message-----
>>> From: Chun Tian (binghe) [mailto:binghe.lisp@gmail.com]
>>> Sent: Monday, December 28, 2009 8:48 AM
>>> To: Seth Burleigh
>>> Cc: usocket-devel(a)common-lisp.net
>>> Subject: Re: [usocket-devel] ECL and MSVC
>>>
>>> Hi, Seth
>>>
>>> Sorry for the delay response. I still doesn't have a chance to try build
> a
>>> MSVC-based ECL by myself and test USOKET on it, but I think you're right.
>>> However, after searching in MSDN, I found a better presentation:
>>>
>>> #include <time.h>
>>>
>>> That is, <time.h> instead of "time.h", better followed C programming
>> style.
>>>
>>> Please give me two days try it by myself, and I'll merge it soon.
>>>
>>> Regards,
>>>
>>> Chun Tian (binghe)
>>>
>>> 在 2009-12-28，06:20， Seth Burleigh 写道：
>>>
>>>> So I searched for it, it looks like you just
>>>> #+(and :ecl :msvc) #include “time.h”
>>>> For a msvc build, I think, instead of just including “sys/time.h”
>>>>
>>>> Though im not sure, it builds, but I haven’t tried any tests.
>>>> _______________________________________________
>>>> usocket-devel mailing list
>>>> usocket-devel(a)common-lisp.net
>>>> http://common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel
>>>
>>>
>>
>>
>
>
