uploaded Channel - a lib for (distributed) message passing and event dispatching to boost vault
Hello there, I just upload a updated version of my Channel library to Vault under Main/"Distributed Computing". This version contains some update for Channel to work with the latest boost distributions and change to boost license, since there are several requests for me to update and upload to Vault. A brief description: Channel procides name space for distributed message passing and event dispatching. Its major components (message IDs, routing algorithms...) are configurable as template parameters. As a namespace shared by peer threads, channels support publish/subscribe scope control, message filtering, and translation.. Thanks Yigong
----- Original Message ----- From: "Yigong Liu" <yigongliu@gmail.com> To: <boost@lists.boost.org> Cc: <boost-users@lists.boost.org> Sent: Wednesday, March 04, 2009 6:26 PM Subject: [boost] uploaded Channel - a lib for (distributed) message passingand event dispatching to boost vault
Hello there,
I just upload a updated version of my Channel library to Vault under Main/"Distributed Computing". This version contains some update for Channel to work with the latest boost distributions and change to boost license, since there are several requests for me to update and upload to Vault.
A brief description: Channel procides name space for distributed message passing and event dispatching. Its major components (message IDs, routing algorithms...) are configurable as template parameters. As a namespace shared by peer threads, channels support publish/subscribe scope control, message filtering, and translation..
Hi, Happy to hear that you decided to upload your Channel library. Do you plan to submit it for review? I'm also interested on your Join library. Have you found a Review manager? BTW on SourceForge it is announced as the release Development Status : 4 - Beta I have added a pointer to the Channel library on the Libraries under construction https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction?version=47#... Best, Vicente
Hello, Thank you for your interests in Join and Channel. Yes, I am submitting it for review, although it is not in best shape yet, i seriously needs more feedback.
I'm also interested on your Join library. Have you found a Review manager?
There is no review manager yet. Could you or somebody be kind enough to volunteer:)?
BTW on SourceForge it is announced as the release Development Status : 4 - Beta
i haven't uploaded it to my sourceforge site yet.
I have added a pointer to the Channel library on the Libraries under construction https://svn.boost.org/trac/boost/wiki/LibrariesUnderConstruction?version=47#...
Thanks a lot! Yigong
----- Original Message ----- From: "Yigong Liu" <yigongliu@gmail.com> To: <boost@lists.boost.org> Sent: Thursday, March 05, 2009 2:51 AM Subject: Re: [boost] uploaded Channel - a lib for (distributed) messagepassingand event dispatching to boost vault
Hello,
Thank you for your interests in Join and Channel. Yes, I am submitting it for review, although it is not in best shape yet, i seriously needs more feedback.
I'm also interested on your Join library. Have you found a Review manager?
There is no review manager yet. Could you or somebody be kind enough to volunteer:)?
Hi, Thanks for the offer. I would like to be the review manager of your Join library, but I'm not sure I have the theoretical knowledge to follow the discussion, your library purpose a new paradigm and the subject is a little bit complex. I would prefer to be the review manager of a library I have a deeper understanding. Hoping you find a better review manager, Vicente
Hello Vicente, Thanks for looking into the Join library and maintain the "libraries in build" wiki. I understand that "Join" looks a little bit odd (or new) from the surface. However under the hood is just the plain old message passing. Join/Jocaml (the original authors, not me:) did create unique primitives for message coordination: Join definitions and join patterns. When they integrated Join's constructs into OO languages to be more appealing to larger developer community, "channels" become async methods, join-patterns become chords and join-definitions become classes. This may look more accessible to OO developers, however it becomes more static and the real meaning of messaging may be escaping in the first look. Nowadays, the trend is reversing and people are more coming back to the message passing side. Here is a video about integrating Join into VisualBasic which you may find interesting: http://channel9.msdn.com/shows/Going+Deep/Claudio-Russo-and-Lucian-Wischik-I... BTW, the core of the Join library is about 1000 lines (port.hpp/join_base.hpp/part_of_actor.hpp), all others are just sugars. Thanks. Yigong
Thanks for the offer. I would like to be the review manager of your Join library, but I'm not sure I have the theoretical knowledge to follow the discussion, your library purpose a new paradigm and the subject is a little bit complex. I would prefer to be the review manager of a library I have a deeper understanding.
Hoping you find a better review manager, Vicente
participants (2)
-
vicente.botet -
Yigong Liu