Message-ID: <fd14267e0905180032u2c3389c0y9995f2d40c1ddc45@mail.gmail.com>
Date: 2009-05-18T07:32:15Z
From: Aval Sarri
Subject: newbie: closing unused connection + readline
In-Reply-To: <8b356f880905161315w47211083m5da7f4bdf8f9cbea@mail.gmail.com>
> I don't understand why read.table would have a problem reading
> directly from a socket instead of a textConnection. ?Is this a bug?
> Some subtlety in the semantics of socketConnection as opposed to
> textConnection? ?Incorrect parameters when opening the
> socketConnection?
No problem with socketConnection and read.table. I want to read a line
at a time but when I use
read.table (socketConnection) then it waits till client socket
connection is closed; and entire data comes in as one big chunk. I am
reading a line at a time since data will be available after every few
seconds and I can process and obtain results of already generated
data.
Should I use some (eof) character in data so that read.table returns
without client closing socket connection and I can read a line too?
Thanks for your time sir(s).
Regards
-Aval.