Sending a HTTP request with net.http takes a callback.
It's fine if you kick off the HTTP request from the event.
On 21 January 2016 at 12:15, Harsha Bellur wrote:
> Hi Mathew,
>
> Perhaps I should not be using fire_event().
> What I am attempting to do is capture all "muc_events" (such as join
Hi Mathew,
Perhaps I should not be using fire_event().
What I am attempting to do is capture all "muc_events" (such as join room,
leave room...) in a MUC room and send it via HTTP.
I have written a module that incorporates a handler which does a HTTP post
of the events received. This, in my o
On 20 January 2016 at 20:24, Matthew Wild wrote:
> On 20 January 2016 at 19:13, Harsha Bellur wrote:
>> Hi
>>
>> In situations where events (same event_name) are getting fired
>> (module:fire_event()) quicker than the handler function (defined in
>> module:hook()), is it safe to assume that the e
On 20 January 2016 at 19:13, Harsha Bellur wrote:
> Hi
>
> In situations where events (same event_name) are getting fired
> (module:fire_event()) quicker than the handler function (defined in
> module:hook()), is it safe to assume that the events are queued?
There is no queue - module:fire_event(
Hi
In situations where events (same event_name) are getting fired
(module:fire_event()) quicker than the handler function (defined in
module:hook()), is it safe to assume that the events are queued?
Thanks
Harsha
--
You received this message because you are subscribed to the Google Groups
