[asterisk-bugs] [JIRA] (ASTERISK-26422) [patch] Force calendars to do new fetch after module reload

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232462#comment-232462 ] 

Asterisk Team commented on ASTERISK-26422:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> [patch] Force calendars to do new fetch after module reload
> -----------------------------------------------------------
>
>                 Key: ASTERISK-26422
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26422
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_calendar/NewFeature
>    Affects Versions: 13.9.1
>            Reporter: Ludovic Gasc (Eyepea)
>            Severity: Minor
>
> Hi,
> We use a lot res_calendar, we are very happy with that, especially because you use libical, the almost alone opensource library that supports really ical format with all types of recurrency.
> Nevertheless, some features are missed for our business use cases.
> This first patch adds a new option in calendar.conf: fetch_again_at_reload
> Be my guest for a better name.
> If it's true, when you'll launch "module reload res_calendar.so", Asterisk will download again the calendar.
> The business use case is that we have a WebUI with a scheduler planner, we know when the calendars are modified.
> For now, we need to define 1 minute of timeout to have a chance that our user doesn't wait too long between the modification and the real test.
> But it generates a lot of useless HTTP traffic.
> I'm putting the very small patch in Gerrit.
> Have a nice Astricon.



--
This message was sent by Atlassian JIRA
(v6.2#6252)