Anyway, if you are writing a local socket application, then you would not have this problem, since it wouldn't have any IE dependancy. I tend to use local sockets and network oriented design techniques for IPC because they transition cleanly to networked applications when the need arises. Also they are very portable, as compared to something like memory mapped files, which are a Linux/Unix thing. Another option (maybe, depending on how you like the complexity, might be
POE)
One thing you have to watch for (not in this case I'm sure), though is whether a user running an application on the same machine (i.e. Linux remote users and/or Windows terminal server) can't play with the app. Local sockets bridge user boundaries, and hence can be dangerous if you don't build in the right protocols.
Nice SG1 quote by the way, but IMHO nothing can beat Tealc's "Untamed equines couldn't drag me away..."
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.