So as not to hijack Germain’s thread anymore.
This is a request to create a ‘event driven’ or ‘on change’ scan class for history and tag processing.
The requirement would be to completely process any change for a tag that was entered into the system using the timestamp attached to the change. ie: field time not processing time.
Hi,
Yes, I definitely think we can do something like this. Of course, you’re still building on top of the whole tag subscription system, so ultimately there will be timing involved somewhere, but at least on-change history processing would remove one more timer.
I’ve been meaning to send you a message in general lately, because it seems you’ve been running into a number of cases where small changes could probably help a lot. We can do that separately or on the phone, but I just wanted to let you know that I’m interested in seeing what things can be quickly improved (allowing for the fact that we’re in the middle of a few different things right now).
Regards,
I’ll give you a call next week.