Closed BryceStevenWilley closed 2 years ago
Should be added in https://github.com/SuffolkLITLab/EfileProxyServer/commit/e6386b665ac4b1aa1ad4f6af29f9f815d96a9306. Slight improvement could be to use the policy cacher from the Scheduled task to download the codes, but that's still to pass it around threads.
This should still be resolved; as long as the server doesn't restart, we cache the results of GetPolicy. But for completeness, here's the text from our communications with Tyler, on how their side works.
We’re not going to make any changes or updates to anything with the codes or GetPolicy in the middle of the day. That takes a full system refresh on our end and potentially causes the system to go down for period of time, we can’t have downtime in production at all during filing hours. Our cache runs nightly around midnight and vendors are instructed to pull their codes in the early morning hours typically 2-3am; at least sometime before you believe your filers will start using the system the next day. Additionally, we don’t make changes during the day as that could cause some EFSP vendors to not have the latest data and cause filing errors if those codes are not in sync with the EFM.
Some choices to be made: do we store it in the database as well, and if so how? If not do we store in memory / serialize an XML file that can be read on startup?