Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Official 5.4 Beta Discussion Thread
thanks Dean, I confirm the fix. All is good!
Reply
Version 5.3.928 is posted. The sole purpose of this one is to introduce a new capability, which is be able to mark triggered events as 'serialized'. This means that, if one trigger comes in and causes the event to be run, and another comes in while that is going on, that second one is not immediately run. It is held off until the first instance completes.

And so on for any others that come in while one is currently running. This can sometimes help prevent weird issues, because the event server has multiple threads that service incoming triggered events as they show up, and if multiples come in at once, they are likely going to be processed as the same time. This keeps the event server responsive even if people in multiple locations in the house are triggered events.

But, sometimes, this may be a problem. For instance you want to do something on button press and then release, both trigger the same event, and internally you look at which is is and do something accordingly. But if the first one takes more than a second or some to do its thing, and you release the button, the release version of the event can start running before the press has time to complete. Marking such an event as serialized will force the release processing to wait until the press processing is done.

Keep in mind though that, if you have the same event being triggered from multiple location sin the house, they will all be serialized, so if you press and release and right after that someone else in another room presses and releases, theirs will not run until both of yours complete. So for optimal throughput, in some cases you may need to deal with such things yourself to some degree.

Maybe later we could provide some means for more of the incoming trigger info to be used as serialization criteria, but for now it's just the event path only. So, if /User/MyEvents/ShockBubba is marked as serialized, then any triggering of that event will be run one at a time.


This required some fairly substantial reworking of the structure of the event server. I cleaned up and improved the code a lot while in there, but of course I might have introduced some glitch or another that we'll have to address.
Dean Roddey
Explorans limites defectum
Reply
Version 5.3.932 is posted, which is mostly just to tweak some issues a couple folks reported, and given them a chance to see if they are taken care for real. Probably no reason for anyone else to grab these unless you are seeing one of the things tweaked.
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Official 5.4 Beta Release Thread Dean Roddey 31 2,851 01-19-2019, 03:06 PM
Last Post: Dean Roddey
  Official 5.3 Beta Discussion Thread Dean Roddey 815 112,004 07-05-2018, 12:44 PM
Last Post: Dean Roddey
  Official 5.3 Release Thread Dean Roddey 27 5,888 07-05-2018, 12:44 PM
Last Post: Dean Roddey
  Official 5.2 Beta Discussion Thread Dean Roddey 244 74,884 10-14-2017, 07:57 PM
Last Post: Dean Roddey
  Official 5.2 Beta Release Thread Dean Roddey 13 7,437 10-09-2017, 06:49 PM
Last Post: Dean Roddey
  Official 5.1 Beta Discussion Thread Dean Roddey 453 170,784 05-16-2017, 03:45 PM
Last Post: Dean Roddey
  Official 5.1 Beta Release Thread Dean Roddey 28 17,096 05-12-2017, 05:44 PM
Last Post: Dean Roddey
  Official 5.0 Beta Discussions Dean Roddey 2,019 439,866 11-09-2016, 04:34 PM
Last Post: Dean Roddey
  Official 5.0 Beta Release Thread Dean Roddey 15 12,147 11-01-2016, 10:32 AM
Last Post: Dean Roddey
  How to obtain Beta versions? willsauter 3 3,142 07-15-2016, 04:57 PM
Last Post: willsauter

Forum Jump:


Users browsing this thread: 1 Guest(s)