Re: is it reasonable to use the core, CBEEP.c, to embed into a scripting language?
Darren New <[email protected]> Wed, 06 Dec 2006 08:48:02 -0800
| Newsgroups | gmane.network.beep.beepcore.c.general |
|---|---|
| Message-ID | <[email protected]> |
Sam Roberts wrote:
> This is the only BEEP implementation I've seen that claims to be useful
> in a thread-less environment, but before I waste too much time, could
> anybody confirm its in a reasonable state to use, or definitively warn
> me away from using it?
There are two parts to the C libraries. One is what I called "the core",
which does the parsing and memory management and such. A higher layer
lets you write profile implementations that are based on threading, but
the "core" part does everything with callbacks. It lets you queue up
messages to a channel and lets you pull frames and messages off the channel.
If you're going to integrate BEEP into some other language with its own
memory management, threading, etc., that's probably a decent place to start.
Alternately, look at the Tcl implementation, which does all this stuff
without threads. Of course, you would need to either rewrite that or
link the Tcl interpreter into your own code, but it'll show you how to
handle the protocol without needing threads.
--
Darren New / San Diego, CA, USA (PST)
Scruffitarianism - Where T-shirt, jeans,
and a three-day beard are "Sunday Best."
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV