Re: is it reasonable to use the core, CBEEP.c, to embed into a scripting language?

What Darren said :)  You can look at the wrapper stuff to get an
idea of how to do it, the code is separated out so that the IO, 
threading and core BEEP protocol stuff are relatively independant.

Also, there is at least one bad deadlock bug in the C wrapper
on channel close, so my logic was in error there.

-bill

On Wed, Dec 06, 2006 at 12:40:17AM -0800, Sam Roberts wrote:
> I know the project is dead, but I don't want the multi-threaded server
> framework, just an implementation of the core protocol, so that I can
> embed it into lua and ruby.
> 
> Both these languages are very hostile to C libraries that require use of
> O/S threads, though green threads can be built on top of multiplexed I/O
> within or above their interpreters.
> 
> 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?
> 
> Thanks,
> Sam
> 
> 
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Beepcore-c-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/beepcore-c-users

-------------------------------------------------------------------------
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