[asterisk-dev] Proposal to deprecate 'roundrobin' strategy in app_queue

[Jon Gabrielson]

On Tuesday 30 May 2006 23:31, Adam Goryachev wrote:
> Well, I would personally think there is a reasonable sized use case for
> roundrobin as-is in smaller installations. ie, single sales person,
> single accounts person, single manager. You want a sales queue with
> plain roundrobin, so the sales guy always gets first preference, but you
> also want your sales queries handled quickly, so it then rolls over to
> the accounts person, and then to the manager.

As I understand it, what you are describing is not what roundrobin 
currently does. From the way I understand it, roundrobin and 
rrmemory both have "memory"  rrmemory continues after the last 
person who answers while roundrobin continues after the last person 
it started with. Neither one to my knowledge start at the 
beginning of the list each time, for that weights are the best solution.




>
> Of course, the same configuration can be achieved with using the agent
> priority/weight, so perhaps it is not relevant.
>
> Perhaps the best solution is to change roundrobin to rrnomemory and
> leave rrmemory as-is ??
>
> This will stop people from blindly picking "roundrobin" because the
> config option sounds right, and they will spend the extra 3 seconds to
> read the description in the sample config file...
>
> Basically, I don't see the advantage in removing a feature, that
> someone, somewhere, might be using...
>
> Regards,
> Adam
>
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev