I am about to do some socket programming with the universe socket API
(universe 10.2.x and aix 5.3.x), are there any
gotchas/advice/suggestions anyone would care to share?
thanks!
dougc
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug
Just had a big issue with sockets. Make sure your DNS is set up
correctly or you are going to have a delay in opening and closing of
sockets. This did not seem to be an issue in AIX just Windows.
Heather A. Bickers
Director of Client Services
Cypress Business Solutions
678.494.9353 x1409
hbic
In my experience its best to use non-blocking sockets..
It's can be a bit of a pain depending on the situation, but with some
careful "wait until x unless received y bytes" type loops you can cater
for pretty much any scenario.. In the scenarios where I have control
over both sides of the connect
Aren't simple protocols, even custom ones, great! ;) I almost always
write code using non-blocking functions so that there is true control. You
gain more control over the data and you can build more responsive
applications since you're not letting the network subsystem control the flow
of your a
For anyone currently using Message Queues - please switch to sockets - I
speak from personal experience that the performance and throughput gains
were huge.
Regards
JayJay
-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of
John,
Be aware that sockets are a "stream" based protocol and not a "message"
based protocol. When you send data to a socket it may arrive in one or
more pieces (packets). On a LAN this may never occur, but over a WAN or
the internet your data packets will almost surely be broken up into
smaller
Kevin, aren't you describing UDP communication, not TCP? Packets can be
fragged and move through any number of different channels w/ UDP, but
they're reassembled as a part of being received through TCP. If you sent a
1024 packet over UDP I would expect exactly what you've stated. Send a 1024
pac
The issue is that if you send a 1024 byte message through a TCP socket, you
may eventually get 1024 bytes out the other end, but you may not get them
all at once. The message may be broken up into lots of pieces, i.e. if you
do a read(), you may get 1024 bytes, or you may get a lot less, and have t
I will be out of the office starting 10/04/2009 and will not return until
20/04/2009.
I will respond to your message when I return.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/