flexd
commented
9 years ago Hi,
I kind of agree with you. Currently there is no caching here, but if it is implemented I want to make it so that the caching bit is swappable and the default is no caching at all.
I was talking to @nightexcessive about writing a client last fall, and he ended up showing me that he was working on at the same time. We kind of agreed to collaborate a bit on a client, but I we have not really spoken since then. I think his approach is better since it uses some reflection to handle rowsets dynamically, but I have not though of a good way to handle those few API endpoints that return results without rowsets yet.
You can find his code here, https://github.com/nightexcessive/eve
I recently unsubscribed my accounts since I have not been playing EVE lately, and since I have had no time to work on any EVE related projects.
Hello,
I've been looking at several implementations of eve api in different languages, and I want to suggest removing caching from the api layer. The caching implementation should be on the user of the library, because everyone has different usage and may want to change caching backend, and similar things, the library should only provide easy way of interfacing it with this chache.
Lukas