What you're talking about is simply 'protocol'. As you control both sides of the communication, you can use any protocol you like - making one up to suit your needs would probably be as easy as bending another (HTTP, SOAP etc) to fit.
If, for instance, you're wanting to send a number of encrypted key-value pairs, this could be as simple as
use Crypt::Simple;
print MYSOCKET encrypt(join(":",map {"$_=$vals{$_}"} keys %vals));
...and a quick split/map/decrypt on the other end will reproduce the hash.
RPC (and thus SOAP) is more often used where you're sending 'objects' back and forth, allowing a client to perform Remote Procedure Calls...overkill for simply sending
'data'.
Having just knocked out a moderately-sized wxWindows app btw, I can (charitably) say that the documentation gives you just enough (with a couple of very minor errors / omissions), and I'd definitely use it again for all my advanced GUI needs. :)
Cheers, Ben.
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.