[jcifs] Problem reading multiple writes from named pipe

[Michael B.Allen]

On Thu, 17 Apr 2003 08:49:18 -0400
"Eric Sword" <ericsword at grouplogic.com> wrote:

> That matches the behavior I saw prior to switching to just the
> PIPE_TYPE_RDWR constant.  The only problem is that our existing
> application does, in fact, read and write twice to a transact named
> pipe.  That's why I had to deal with this screwy protocol to begin with;
> I didn't just make it up for grins. ;-)  It's been working great this
> way for about 5 years now.  As I mentioned previously, the PipeTalk
> application seems to function fine talking to the pipe in our main
> application (and my pipe_project tester), except when it tries to read a
> very large amount of data (>5K-10K), even though the data does not
> exceed the side of the buffer given.
> 
> In any case, thanks for the help.  This is a side project that I will
> return to as I am able.  If I discover anything new, I will post it.

Well jCIFS Named Pipes should behave the same as Win32 named pipes so
if you are really writing separately to a server side Transact named
pipe then by all means send me a packet capture of it and I'll mimic
that behavior.

Mike

-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived.