Re: [prosody-dev] events
On 21 January 2016 at 01: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 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 opinion, must be an asynchronous > operation. Prosody's HTTP client API, net.http, provides an asynchronous HTTP post. Documentation is here: https://prosody.im/doc/developers/net/http Regards, Matthew -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at https://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
Re: [prosody-dev] events
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 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 opinion, must be an asynchronous > operation. > > Your help will be much appreciated. > > Thanks > Harsha > > On Wednesday, January 20, 2016 at 3:26:44 PM UTC-5, Matthew Wild wrote: >> >> 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 events are queued? >> > >> > There is no queue - module:fire_event() d >> >> Sorry, hit send somehow too early. >> >> There is no queue - module:fire_event() does not return until the >> handler has finished. >> >> Handlers should never take long to execute, they should return >> instantly. If you're having trouble with slow handlers, they need >> fixing (we can help you figure out how, if you need). >> >> Regards, >> Matthew > > -- > You received this message because you are subscribed to the Google Groups > "prosody-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to prosody-dev+unsubscr...@googlegroups.com. > To post to this group, send email to prosody-dev@googlegroups.com. > Visit this group at https://groups.google.com/group/prosody-dev. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at https://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
Re: [prosody-dev] events
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 opinion, must be an asynchronous operation. Your help will be much appreciated. Thanks Harsha On Wednesday, January 20, 2016 at 3:26:44 PM UTC-5, Matthew Wild wrote: > > 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 events are queued? > > > > There is no queue - module:fire_event() d > > Sorry, hit send somehow too early. > > There is no queue - module:fire_event() does not return until the > handler has finished. > > Handlers should never take long to execute, they should return > instantly. If you're having trouble with slow handlers, they need > fixing (we can help you figure out how, if you need). > > Regards, > Matthew > -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at https://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
Re: [prosody-dev] events
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 events are queued? > > There is no queue - module:fire_event() d Sorry, hit send somehow too early. There is no queue - module:fire_event() does not return until the handler has finished. Handlers should never take long to execute, they should return instantly. If you're having trouble with slow handlers, they need fixing (we can help you figure out how, if you need). Regards, Matthew -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at https://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
Re: [prosody-dev] events
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() d -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at https://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
[prosody-dev] events
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 "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at https://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
