I do not really get the meaning of:

This means that approaching 100 entries the distribution will become more and more uneven.

After:

The weight is implemented as an internal table with 100 entries. Each entry points to one dispatcher target.

Can you elaborate more. Distributing the target to a 100 array is by design, not really a limitation, same that the weights sum has to be 100. A new algorithm can be implemented if the existing ones do not suit some use cases.

From my point of view, this could be better done as a full config (starting from the one in dispatcher docs) that is placed in misc/examples/, having at the top in comments the description you added in the PR as docs. The readme for modules try to be reference documentation for what the module implementation offers.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <kamailio/kamailio/pull/4158/c2732067085@github.com>

micondamiconda left a comment (kamailio/kamailio#4158)

I do not really get the meaning of:

This means that approaching 100 entries the distribution will become more and more uneven.

After:

The weight is implemented as an internal table with 100 entries. Each entry points to one dispatcher target.

Can you elaborate more. Distributing the target to a 100 array is by design, not really a limitation, same that the weights sum has to be 100. A new algorithm can be implemented if the existing ones do not suit some use cases.

From my point of view, this could be better done as a full config (starting from the one in dispatcher docs) that is placed in misc/examples/, having at the top in comments the description you added in the PR as docs. The readme for modules try to be reference documentation for what the module implementation offers.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <kamailio/kamailio/pull/4158/c2732067085@github.com>