I think the Indy components are usually the ones recommended for the kind of
situation you're describing. You might want to look at them again.

If you have certain needs (cross-platform, lower-level or custom protocols,
etc. etc. etc.), need to get "closer to the metal," or just prefer its style
of operation, Synapse has a lot of good points (and I far prefer it, even
with some problems), but it sounds like you'd prefer some of the
"sub-models" of working that Indy provides. It's been too long, and I'm
switching a few too many tasks right now... but I think they are called
"Command Handlers" (or at least used to be).

Note also that something like that (or pretty darn close) may well be
provided in some of the Synapse examples. In fact, it shouldn't be too hard
to cook up... given specs... and the right developer... and a little time...
At the core, the communication principles are the same, but certain
implementations will make certain applications, or efforts, easier in one
model than another.

When you need to get deeper, more functionality (with less cruft), etc. (and
even a "cleaner" learning experience--from my point of view) you might want
to take another look at Synapse. Getting your current job done quickest,
probably means Indy...

But that's only from as far as I can see...   (and I'm one who chose not to
investigate ICS very far due to structural decisions... and I like & need
threads...)

[Aside: You might think you only need a few quick things ("routines") to
create something... but in comms that often comes back to bite you where it
hurts. Keep an eye out for that, and if your code depends on TCP... try to
learn more about it over time.]


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public

Reply via email to