EVE Technology Lab

Hey people,

We have started to gather metrics on the usage of the IGB JS callbacks. You can see the first 24 hours of this here: https://imgur.com/a/DtJSj

The first few hours are actually blank as we were fixing something after DT with our metrics intake.

I will of course let this run for a while longer before making any decisions but I thought these were both interesting graphs to look at and to make sure that if anyone is using the JS callbacks that I currently have being reported as not used you can tell me my **** is broken.

No. It was decided to remove the IGB without looking at these at all. These are to help focus our efforts in what we prioritize replacing before we remove the IGB.

HEY, Potatoes are valid platform for highly sophisticated systems

Yeah as I understand it, most things heavily using the IGB right now are the tools that rely on it being open when changing systems. These tools will lose a lot of functionality once the IGB is taken out back and double tapped in the head.

These aren't shown in the metrics you've given.

I'm wondering the meaning of IGB JS Callback ? Is it crest api request ?

I'm entirely for the removal of the IGB and ingame links linking to the OOG browser ASAP... I'm tired of having to dumb down code just to make it work in game.

I was under the impression it was Chromium, and it simply had not been updated.

To my mind I think one of the best options available would be to run an extremely lightweight http server in the background with privileged access to IPC with the EVE clients.

Have it reject any connections not from localhost, serve up an appropriate crossdomain policy, and local web browsers could fire requests at it all day long to both push/pull JSON to/from the clients.

It would be possible to build straight into the main game executable, but as almost everyone multiboxes, that would present its own problems... likely some need to open a URL from in-browser which passes details on which port/auth to use for that particular game instance.

and where is that going to be then? CREST?

Currently i am working on a tracking tool, so when i jump from system to system it will tell me the info i need to know about that System (sometimes even before i finish the jump since the headers will sometimes update fast).
When you move this to CREST we will have to do a lot off calls to the server to keep track off where the player is.
This means a lot off calls to a server what is not necessary to do.. (so more stress on the server to).
And since it will have a cache timer... it wont be accurate any more...

And then we have the removal off the JavaScript functions...

I can see this work whit CREST.. we just send the correct information to it and it will pop up a window in the players screen.
but whit that you probably gone have to have a API key.. otherwise you will a lot off random screens pop up everywhere..
and whit that you also have the problem.. you gone need the API key.. before you didn't need that.. only to be trusted.

There are other options possible.

Without committing CCP to anything (as I like my legs unbroken), possibillities include a long poll based system or something Websocket based, so you get a notification when the client changes system.

Doesn't matter. the web socket or long poll would be talking to CCP's servers. nothing to do with the client.