10 Aug
2005
10 Aug
'05
10:53 a.m.
Daniel-Constantin Mierla wrote:
Probably on each request, as the database would be updated behind SER's
back by the monitoring process.
On 08/09/05 13:51, Alistair Cunningham wrote:
That would be fine. Any idea when this will be implemented?
I've considered adding a call to
ds_select_dst() to call
ds_destroy_list(); ds_load_list() on each request with file locking.
It looks like it should work. Has anyone implemented this? Does it
work? Does it have a significant impact on performance?
there is on the todo list to add support to reload the destination list
upon a fifo command or other external event. Destroying and reloading
the list for each request will have quite big performance impact, so it
is better to do it only when needed.
I'd also be open to having the other process write to a database
table, which then SER reads. I'm not sure what's the best mechanism
within SER to look up the table - perhaps avpops? I'd even be willing
write a new module to do it - 'dispatcher_db' perhaps, but this
wouldn't be in the short future.
Do you want a db lookup for each request, or when the server starts and
then use a cache?