![]() |
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Advanced & Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| UNIX Message Queues vs. Sockets | zen29sky | UNIX for Advanced & Expert Users | 2 | 03-21-2007 01:56 PM |
| add linux to NIS (unix) domain | legato | UNIX for Dummies Questions & Answers | 1 | 04-14-2005 10:00 PM |
| fd passing between Independent processes using unix domain sockets | Debasisb2002 | HP-UX | 2 | 03-14-2005 01:59 AM |
| UNIX in MS Win2003 Domain | Teamplay | UNIX for Dummies Questions & Answers | 4 | 07-09-2004 06:41 PM |
| Unix Domain | vibhory2j | IP Networking | 1 | 04-20-2004 07:28 PM |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
UNIX domain sockets vs FIFOs
Is there a performance advantage of one of these over the other? Obviously, it makes no sense to use normal TCP sockets or UDP sockets w/ the overhead they carry. But what about UNIX domain sockets vs FIFOs? I'd think they'd be very similar, in terms of performance and in terms of how they're manipulated.
I plan on doing non-blocking I/O on these and using select to decide when to read an interface. Thanks, Matt Gessner |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|