Re: int16 and int32 declaration conflict
John Schultz <[email protected]>
| Newsgroups | gmane.network.spread.user |
|---|---|
| Message-ID | <[email protected]> |
MAX_SEGMENTS defines how many spread segments (i.e. - LANs) you can have in a configuration. MAX_PROCS_SEGMENT defines how many spread daemons you can have in one segment (i.e. - a LAN). Typically though, a configuration will only be stable if you keep the # of daemons less than 60 or so. Typically, a single daemon (e.g. - Linux) can handle hundreds of clients. I think the #define is something like MAX_FD_EVENTS. The bigger problem you will have with such a large group is that the memberships won't fit in a single message. I'm not sure what Spread will do in that case even if you turn off membership reporting for all your clients. Cheers! ----- John Lane Schultz Spread Concepts LLC Phn: 301 830 8100 Cell: 443 838 2200 On Aug 30, 2011, at 8:03 AM, Jiva bagale wrote: Hi, May I ask you something in general about Spread. I am writing a program where potentially hundreds of devices will join same spread group and send/receive messages using multicast. I found in Spread manual that maximum spread daemons (MAX_SEGMENTS) is 20 and number of clients in each daemon (MAX_PROCS_SEGMENT) is 128. So does it mean I can only have 128*20 = 2560 clients to join same group using multiple daemons? Is there any workaround if I want to connect lets say 5000 clients to same group. Regards Jiva _______________________________________________ Spread-users mailing list [email protected] http://lists.spread.org/mailman/listinfo/spread-users
smime.p7s
(application/pkcs7-signature, 3.7 KB) - not displayed