I added two methods for exposing some more information from the eNet server. I found this by snooping the traffic between browser and eNet server. It contains the modification date of the setup which I would like to use when implementing the cached files (speeding up startup time and load on eNet server).
Do you envision the eNet library to be on this level or would you go for a "higher" level. Instead of these two methods returning the JSON, it could also be methods like "get_last_modification_time()" and "get_server_version()". Or of course both.
Hello Magnus,
I added two methods for exposing some more information from the eNet server. I found this by snooping the traffic between browser and eNet server. It contains the modification date of the setup which I would like to use when implementing the cached files (speeding up startup time and load on eNet server).
Do you envision the eNet library to be on this level or would you go for a "higher" level. Instead of these two methods returning the JSON, it could also be methods like "get_last_modification_time()" and "get_server_version()". Or of course both.
How do you envision this?
Regards,
Marcel