[asterisk-bugs] [Asterisk 0010424]: Allow realtime members on non realtime queues/A member with priorty < 0 is logged out

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10424 
====================================================================== 
Reported By:                irroot
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   10424
Category:                   Applications/app_queue
Reproducibility:            N/A
Severity:                   trivial
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.10  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-10-2007 02:18 CDT
Last Modified:              08-20-2007 17:04 CDT
====================================================================== 
Summary:                    Allow realtime members on non realtime queues/A
member with priorty < 0 is logged out
Description: 

hi there some trivial patches extending on the recent changes (adding
update_realtime_members) it seems to make logic sence to allow realtime
agents on non realtime queues (ive been doing this for over a year
already).

ive also been setting the priorty field in SQL to a negitive value as
opposed to deleteing the agent to log them off and then back to there
existing value to log them on again.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 08-20-07 17:04  
---------------------------------------------------------------------- 
After discussing things on #asterisk-dev, it was decided to go ahead and
put the capability of having realtime members for static queues in 1.4 as
well as trunk.

After looking into things a bit more, I realize why it is that nothing
ever gets written to realtime in app_queue. The reason is that members are
identified by both the queue they belong to and their interface. The
realtime API only allows one keyfield to be used when updating something.

Because of this, there are two ways around this.

1. Change the API to accommodate multi-columnn primary keys. This would
not be trivial since it would mean potentially changing a lot of existing
code to use this new API.

2. Force users of realtime members to use a single unique identifier in
their table to identify a specific member of a specific queue (similar to
what realtime voicemail requires). This would require no change to the API
but would require that users of queues with realtime members possibly
change their table structure.

Using http://bugs.digium.com/view.php?id=2 is my preference since it is less
invasive than http://bugs.digium.com/view.php?id=1 and since we
already have a precedent (realtime voicemail) we should stick with this.

That being said, whatever patch I put up here will be written under the
assumption that the user has defined such a unique id field. Details will
come after I've written the patch. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-20-07 17:04  putnopvut      Note Added: 0069119                          
======================================================================