[Spread-users] Spread implementation and C API

Shashank Yaduvanshi hyaduvanshi at gmail.com
Fri Oct 16 14:41:24 EDT 2009

On Fri, Oct 16, 2009 at 11:44 PM, Daniel F. Savarese <dfs at savarese.org> wrote:
> In message <508727630910161055ha328aa1l52abfd52bd2b4045 at mail.gmail.com>, Shasha
> nk Yaduvanshi writes:
>>Thanks for the quick and helpful reply. So does that mean that a
>>receive/multicast busy waits when it blocks? Also, is there any way to
> No busy waiting.  The client API blocks in recv(), so the process
> sleeps until the kernel wakes it up on account of data arriving or
> an error.
Thanks. That will solve the purpose.
>>use SPREAD when one does not know which machines are connected in the
>>SPREAD network, nor their ip addresses?
> Client programs don't need to know anything about IP addresses (except
> perhaps if you're connecting to a remote spread daemon instead of a
> local one), daemons do (in order to configure spread.conf).  Client
> programs communicate via group names.
Right. I think I should have framed my question more appropriately. I
am developing a generic library (.dll) that has to do communication
between all the machines that run that library at various points of
time. At different times, different set of machines might be connected
and running the library.In that case, its not possible to know what
all ip addresses will be involved in the communication? So, its not
possible to specify the ip addresses in the .conf file. Is there any
way around that? How do I make sure that all the participating
machines at any point of time are part of the network?
> daniel
> o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o o-o-o-o-o-o-o-o-o-o-o-o-o-o
>                                                     s a v a r e s e
>                                                    software research
>                                                 http://www.savarese.com/
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users

More information about the Spread-users mailing list