[asterisk-bugs] [Asterisk 0011887]: [patch] new REALTIME_STORE() and REALTIME_DESTROY() functions
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Feb 1 01:34:55 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11887
======================================================================
Reported By: sergee
Assigned To: otherwiseguy
======================================================================
Project: Asterisk
Issue ID: 11887
Category: Functions/func_realtime
Reproducibility: always
Severity: feature
Priority: normal
Status: feedback
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 101373
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 01-31-2008 06:15 CST
Last Modified: 02-01-2008 01:34 CST
======================================================================
Summary: [patch] new REALTIME_STORE() and REALTIME_DESTROY()
functions
Description:
This patch adds new dialplan functions, which utilize store&destroy RT API.
REALTIME_STORE(family,field)=value
creates a new record in the RT storage, and sets field to value specified
on the right.
SET(XXX=${REALTIME_DESTROY(family,field,value)})
acts in the same way as REALTIME(), except that it removes matched record
from RT storage.
======================================================================
----------------------------------------------------------------------
sergee - 02-01-08 01:34
----------------------------------------------------------------------
otherwiseguy, i wrote documentation before the function itself :)
when i start to code i realized 2 things:
1. There is no way to generate va_list during runtime, so we can't have
variable list of parameters in dialplan function, unless we change an API
and remove all references to va_list structures.
2. Asterisk doesn't provide a method for returning a value in this style:
Set(RESULT=${MYFUNC(a,b,c)=d})
I suppose that parser simply is not capable of handling such
constructions, however i'm not sure here.
i fixed documentation in this patch. As of other changes: i've read on
mailing list that smaller commits are preferable, so if you won't mind -
i'll open a separate issue for API changes (which are required to enable
support for variable argument list in REALTIME*() functions).
Issue History
Date Modified Username Field Change
======================================================================
02-01-08 01:34 sergee Note Added: 0081563
======================================================================
More information about the asterisk-bugs
mailing list