These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Information Portal

 
  • Topic is locked indefinitely.
123Next pageLast page
 

Dev blog: API spring cleaning

First post
Author
Previous Topic Next Topic
CCP Gargant
C C P
C C P Alliance
#1 - 2012-09-19 14:39:51 UTC  |  Edited by: CCP Navigator
CCP Illurkall has a new dev blog available for your viewing pleasure which details the changes coming to the API system this fall. Illurkall is the overseer of the API for the foreseeable future and will make sure it is up to snuff.

You can read all about it here

We would be delighted to receive your (constructive) feedback in this thread.

CCP Gargant | EVE Universe esports Coordinator
ChromeStriker
Sebiestor Tribe
Minmatar Republic
#2 - 2012-09-19 14:43:43 UTC  |  Edited by: ChromeStriker
First

Edit: o/ hi n welcome CCP Gargant

No Worries
Peter Powers
Terrorists of Dimensions
#3 - 2012-09-19 14:45:21 UTC
CCP Gargant wrote:
CCP Illurkall has a new dev blog available for your viewing pleasure which details the changes coming to the API system this fall. Illurkall is the overseer of the API for the foreseeable future and will make sure it is up to snuff.

You can read all about it here

We would be delighted to receive your (constructive) feedback in this thread.

can CCP Illurkall please post in this thread so we can LIKE his post?

3rdPartyEve.net - your catalogue for 3rd party applications
Ferria
Outsourced Manufacturing
#4 - 2012-09-19 14:49:44 UTC
any news on Crest?
CCP Atlas
C C P
C C P Alliance
#5 - 2012-09-19 14:59:42 UTC
Ferria wrote:
any news on Crest?


Here's a recent update from CCP Seagull
Chribba
Otherworld Enterprises
Otherworld Empire
#6 - 2012-09-19 14:59:54 UTC
Sweepin' in with DUST!

★★★ Secure 3rd party service ★★★

Visit my in-game channel 'Holy Veldspar'

Twitter @ChribbaVeldspar
Captain Thunk
Explode. Now. Please.
Alliance. Now. Please.
#7 - 2012-09-19 15:01:07 UTC
CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.
iskflakes
#8 - 2012-09-19 15:06:19 UTC  |  Edited by: iskflakes
Captain Thunk wrote:
CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.


Doesn't seem like a big problem to me -- just make 4 CAKs. How often do you have 3 different corporation directors on a single account anyway?

I am pleased to see this dev blog change. There is no reason to support legacy systems forever and plenty of time has passed now. Also, as member of the HTTPS fanclub it's great to see you requiring it going forward.

If any API developers read this, could we maybe get a relaxation of the cache time on the assets API? For my particular application I would like to request asset data more frequently than once every 6 (?) hours. The long cache time is probably the single biggest source of complaints amongst my users.

-
Promiscuous Female
GBS Logistics and Fives Support
#9 - 2012-09-19 15:09:19 UTC
Captain Thunk wrote:
CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.

read: "Even though months and months have passed I have been too lazy to update our software; now that the plug is getting pulled I am shitting myself continuously at the prospect of having to rewrite all my code in the span of 2 weeks"
Tork Norand
Perkone
Caldari State
#10 - 2012-09-19 15:12:43 UTC
What? No pretty pictures or graphs?

Not even one showing something like....how many new keys were generated from the time they were offered? Cry

--Tork. CEO and Herder of Cats.
Captain Thunk
Explode. Now. Please.
Alliance. Now. Please.
#11 - 2012-09-19 15:15:46 UTC
Promiscuous Female wrote:
Captain Thunk wrote:
CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.

read: "Even though months and months have passed I have been too lazy to update our software; now that the plug is getting pulled I am shitting myself continuously at the prospect of having to rewrite all my code in the span of 2 weeks"


It takes about 3 lines to make use of new keys. The reason I haven't done so is because, guess what, like I said in my first post - CAKs are not as good as a full legacy key.
iskflakes
#12 - 2012-09-19 15:16:34 UTC  |  Edited by: iskflakes
Tork Norand wrote:
What? No pretty pictures or graphs?

Not even one showing something like....how many new keys were generated from the time they were offered? Cry


I created a key a moment ago and it gave me the ID: 1327730. The lowest ID I've seen personally is ~5000, and I have observed that creating keys in quick succession gives them consecutive key IDs. So, it's pretty easy to estimate the number of keys ever created at about 1.3 million. Not bad!

-
CCP illurkall
C C P
C C P Alliance
#13 - 2012-09-19 15:20:53 UTC
Hey

I'll try to make my next DevBlog look a little bit more happy with pictures and all.Smile
The reason for doing this is mainly an effort to keep the legacy to a minimum and making it easy for us to move forward. Because if we can move forward more freely that just means more stuff for you guys in the end.
Tanaka Aiko
Ministry of War
Amarr Empire
#14 - 2012-09-19 15:27:01 UTC
I clicked on devblog link hoping for CREST news, left disappointed.
Akrasjel Lanate
Immemorial Coalescence Administration
Immemorial Coalescence
#15 - 2012-09-19 15:56:39 UTC
Cool

CEO of Lanate Industries

Citizen of Solitude
Promiscuous Female
GBS Logistics and Fives Support
#16 - 2012-09-19 16:25:27 UTC
Captain Thunk wrote:
Promiscuous Female wrote:
Captain Thunk wrote:
CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.

read: "Even though months and months have passed I have been too lazy to update our software; now that the plug is getting pulled I am shitting myself continuously at the prospect of having to rewrite all my code in the span of 2 weeks"


It takes about 3 lines to make use of new keys. The reason I haven't done so is because, guess what, like I said in my first post - CAKs are not as good as a full legacy key.

your fault for writing code that relies on a goofy edge case instead of developing a proper application

fortunately for you they aren't actually shutting down old keys, just making it impossible to generate additional legacy keys, so you probably got another couple of months before you have to get off your ass and change "3 lines" of code
Captain Thunk
Explode. Now. Please.
Alliance. Now. Please.
#17 - 2012-09-19 16:33:39 UTC
Promiscuous Female wrote:
Captain Thunk wrote:
Promiscuous Female wrote:
Captain Thunk wrote:
CAKs fail to encompass the abilities of its predecessor the legacy API key.

A full legacy key allows access to everything available with the account, with a CAK you are limited to 1 char, All chars or 1 Corp.

This means to equal 1 full legacy key you will need upto 4 CAKs per account. 1 CAK for all the chars and if there are 3 chars, each a director or CEO of a different corp then 1 CAK for each of them.

There is no reason for this backwards step, you can maintain the ~security~ CAKs are meant to achieve and still have an option to access ALL data for those that want it.

read: "Even though months and months have passed I have been too lazy to update our software; now that the plug is getting pulled I am shitting myself continuously at the prospect of having to rewrite all my code in the span of 2 weeks"


It takes about 3 lines to make use of new keys. The reason I haven't done so is because, guess what, like I said in my first post - CAKs are not as good as a full legacy key.

your fault for writing code that relies on a goofy edge case instead of developing a proper application

fortunately for you they aren't actually shutting down old keys, just making it impossible to generate additional legacy keys, so you probably got another couple of months before you have to get off your ass and change "3 lines" of code


I did the changes 12 months ago, I simply disabled it because instead of asking for multiple keys and doing the necessary checking to make sure all have been entered I could just stick to 1 legacy key as it's just much better.

It was originally written when CAK didn't exist, so your spouting about "developing a proper application" is just stupid nonsense being spewed by a kid who just collected his Basic Computing certificate last week. Shutting down legacy API at this juncture serves no purpose other than to supply reason for a devblog. It's a system that happily runs itself and no-one is planning on adding anything to the API or working on it in any manner as all efforts are concentrated on CREST.

My only crime is that I am one of the few people who actually use all of the available API which is why hoopleheads such as yourself keep spouting rubbish about "should have updated" oblivious to the limitations that CAK pose compared to their predecessor.
Sentient Blade
Crisis Atmosphere
Coalition of the Unfortunate
#18 - 2012-09-19 16:51:26 UTC
Now if only there was JSON...
Promiscuous Female
GBS Logistics and Fives Support
#19 - 2012-09-19 16:59:20 UTC
Captain Thunk wrote:

I did the changes 12 months ago, I simply disabled it because instead of asking for multiple keys and doing the necessary checking to make sure all have been entered I could just stick to 1 legacy key as it's just much better.

It was originally written when CAK didn't exist, so your spouting about "developing a proper application" is just stupid nonsense being spewed by a kid who just collected his Basic Computing certificate last week. Shutting down legacy API at this juncture serves no purpose other than to supply reason for a devblog. It's a system that happily runs itself and no-one is planning on adding anything to the API or working on it in any manner as all efforts are concentrated on CREST.

My only crime is that I am one of the few people who actually use all of the available API which is why hoopleheads such as yourself keep spouting rubbish about "should have updated" oblivious to the limitations that CAK pose compared to their predecessor.

that's an awful lot of :words: for "i'm too lazy to update my application"

also i guess you missed the locations, charactername, and contracts api stuff that they added after announcing crest
Hatsumi Kobayashi
Perkone
Caldari State
#20 - 2012-09-19 17:33:43 UTC
CCP illurkall wrote:
Hey

I'll try to make my next DevBlog look a little bit more happy with pictures and all.Smile
The reason for doing this is mainly an effort to keep the legacy to a minimum and making it easy for us to move forward. Because if we can move forward more freely that just means more stuff for you guys in the end.


CAKs are a step backward.

No sig.
123Next pageLast page