[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Brian Schroeders chat example on windows

Robert Feldt

11/4/2004 11:47:00 AM

Hi again,

Has anyone been able to run the chat example from Brian Schroeders "A
Ruby a day" course on Windows (latest one-click)? My students say it
does not work (no info is communicated over the socket) while when I run
it on linux it works fine. They say they already tried disabling the
firewall so shouldn't be that... ;)

Anyone run into similar problems?

/Robert
4 Answers

Brian Schröder

11/4/2004 7:18:00 PM

0

Hello Robert,

nice to hear, that you are using the course. In my course there was one person with a windows system, and his problem was, that the console only drew the received text, when he hit return. So not usable as a chat client. cmd seems to cache printed text while it is reading with gets.

Regards,

Brian

On Thu, 4 Nov 2004 20:47:06 +0900
Robert Feldt <Robert.Feldt@htu.se> wrote:

> Hi again,
>
> Has anyone been able to run the chat example from Brian Schroeders "A
> Ruby a day" course on Windows (latest one-click)? My students say it
> does not work (no info is communicated over the socket) while when I run
> it on linux it works fine. They say they already tried disabling the
> firewall so shouldn't be that... ;)
>
> Anyone run into similar problems?
>
> /Robert
>
>


--
Brian Schröder
http://www.brian-sch...

gabriele renzi

11/5/2004 1:27:00 AM

0

Brian Schröder ha scritto:
> Hello Robert,
>
> nice to hear, that you are using the course.
> In my course there was one person with a windows system,
> and his problem was, that the console only drew the received text,
> when he hit return. So not usable as a chat client.
> cmd seems to cache printed text while it is reading with gets.
>
> Regards,
>
> Brian

isn't this an example of the know threading issues on windows?
(basically, IO on non-sockets objects like the console is blocking).

Robert Feldt

11/5/2004 7:07:00 AM

0

gabriele renzi wrote:

> Brian Schröder ha scritto:
>
>> Hello Robert,
>>
>> nice to hear, that you are using the course.
>
> > In my course there was one person with a windows system,
> > and his problem was, that the console only drew the received text,
> > when he hit return. So not usable as a chat client.
> > cmd seems to cache printed text while it is reading with gets.
>
>>
>> Regards,
>>
>> Brian
>
>
> isn't this an example of the know threading issues on windows?
> (basically, IO on non-sockets objects like the console is blocking).
>
Yep, that's it. Thanks to both of you for your answer.

Brian: Yes, I used parts I and III of your slides and provided pointers
to some other parts. Great material. I will send an url to this list
when I've cleaned up the info I used.

Thanks,

Robert

Mark Hubbart

11/5/2004 7:20:00 AM

0

On Fri, 5 Nov 2004 10:33:44 +0900, gabriele renzi
<rff_rff@remove-yahoo.it> wrote:
> Brian Schröder ha scritto:
>
>
> > Hello Robert,
> >
> > nice to hear, that you are using the course.
> > In my course there was one person with a windows system,
> > and his problem was, that the console only drew the received text,
> > when he hit return. So not usable as a chat client.
> > cmd seems to cache printed text while it is reading with gets.
> >
> > Regards,
> >
> > Brian
>
> isn't this an example of the know threading issues on windows?
> (basically, IO on non-sockets objects like the console is blocking).

This may be a dumb question, but if it's blocking IO that's the
problem, wouldn't IO#readpartial work, since it always returns
immediately?

hth,
Mark