| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Named pipes |
On Nov 28 15:10 174, Craig Swanson of 1:202/354 wrote:
CS> The new problem report on OS/2 3.0 is PMR 0x807,PSY.
CS> The new problem report on OS/2 3.0 is PMR 0x818,PSY.
I have not experienced any of these problems, and I can't
understand why I have not experienced the PMR 0x807 if it is there.
But knowing how long you have worked with OS/2 and how good you are
at it, I don't doubt that these problems really exists.
CS> 3) Client to server messages writes of longer than about 4196
CS> bytes (the exact cutoff seems to vary a few bytes) are fragmented
CS> into two sections. For example, if the client writes a message
CS> that is 4600 bytes long, the server side might get back 180
CS> bytes of a message from the first DosRead() call and the
CS> remaining 4420 bytes of the message in the second DosRead()
CS> call.
Just to make sure, you have set both server/client to run in message
mode? I have used Named Pipes a long time for my own projects, and are
often trying them in "local mode" (and a lot of my customers are
also using the NPs in "local mode"). I am using message mode
pipes and the writes often are vvery large, up to 32000 bytes. The only
difference I can see, is that in my case it is the server that writes these
large messages, while the client only write very small messages. Also, I
am still keeping to the 16-bit API.
CS> this point,it looks like perhaps TCP/IP or DSOM would also work.
CS> But I really don't want to have to rewrite code that was working
CS> well and hadn't been changed in months. Thus I'm very nervous
CS> and anxious about all the troubles I am having with named pipes.
If you really think TCP/IP would work for you, I wouldn't worry about
the work required to switch from NP to TCP/IP. I think TCP/IP
stream-sockets are really very easy to use. The only problem with
stream-sockets (that I am having) is that they don't seem to support
"messages" (I haven't found any mechanism for this anyhow), so I
had to build a packaging mechanism too (easy enough).
Mvh / Mikael Wahlgren
--- LoraBBS-OS/2 v2.40b3 (Eval.)
* Origin: OS2You Support BBS +46 31 196406 (2:203/302.5)SEEN-BY: 12/2442 54/54 620/243 624/50 632/348 640/820 690/660 711/409 410 413 SEEN-BY: 711/430 807 808 809 934 942 949 712/353 623 713/888 800/1 @PATH: 203/302 200 201/300 201 2104 109/347 2 7 3615/50 229/2 @PATH: 12/2442 711/409 54/54 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.