<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Named pipes</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>I have posted a few messages concerning named pipes without any response so I guess people just don't use them. I have managed to figure out the issues so far and all turned out to be my mistake. Unfortunately I now have some issues reading (rather than writing which works fine now).</FONT></P>
<P><FONT SIZE=2>On the experiments I have done the following seems to be the case.</FONT>
</P>
<P><FONT SIZE=2>1. As Squeak is single threaded reading an empty pipe locks up Squeak. This was not unexpected and I need to be able to do a fcntl(stream, fcntl.F_SETFL, os.O_NDELAY). But I don't know how to do this in Squeak. I would also want to run this in a separate thread and AsyncFile looks useful for this.</FONT></P>
<P><FONT SIZE=2>2. FileStream atEnd always returns true regardless of how much data is in the pipe. This means everything that uses atEnd such as next: and things that use next: don't work either. In fact the only way to read data is to use next with no way to know when you are at the end of file.</FONT></P>
<P><FONT SIZE=2>3. FileStream size always returns a huge number that is always the same.</FONT>
</P>
<P><FONT SIZE=2>Any help with this would be much appreciated.</FONT>
</P>
<P><FONT SIZE=2>Thanks</FONT>
<BR><FONT SIZE=2>Bob </FONT>
</P>
<P><STRONG>*** Confidentiality Notice ***</STRONG>
Proprietary/Confidential<BR>Information belonging to CGI Group Inc. and its
affiliates<BR>may be contained in this message. If you are not a
recipient<BR>indicated or intended in this message (or responsible
for<BR>delivery of this message to such person), or you think for<BR>any reason
that this message may have been addressed to you<BR>in error, you may not use or
copy or deliver this message<BR>to anyone else. In such case, you should
destroy this<BR>message and are asked to notify the sender by reply
email.</P>
</BODY>
</HTML>