You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 21, 2019. It is now read-only.
The messages sent over STOMP are updates, and if some updates are missing the data does not reflect the reality.
Adding a way to parse the darwin logs from FPT given a start timestamp would help address this issue.
The messages taken from the logs need to be sent over to the listener implemented by the client (user of this library) just as the STOMP messages, and the order should be as they were sent from Darwin. This makes all the complicated logic of going to FTP, downloading XMLs, and then connecting to STOMP transparent to the client.
Maybe an extra, optional argument on the on_*_message methods to indicate the source would be nice.
The messages sent over STOMP are updates, and if some updates are missing the data does not reflect the reality.
Adding a way to parse the darwin logs from FPT given a start timestamp would help address this issue.
The messages taken from the logs need to be sent over to the listener implemented by the client (user of this library) just as the STOMP messages, and the order should be as they were sent from Darwin. This makes all the complicated logic of going to FTP, downloading XMLs, and then connecting to STOMP transparent to the client.
Maybe an extra, optional argument on the
on_*_messagemethods to indicate the source would be nice.