| Author |
Thread Statistics | Show CCP posts - 6 post(s) |
|
CCP Fallout
   |
Posted - 2011.01.26 13:56:00 -
[1]
HTTPS has been enabled for the API, and CCP Stillman has all the details in his newest dev blog.
Fallout
Associate Community Manager
CCP Hf, EVE Online
Contact us |
|
|
CCP Stillman
|
Posted - 2011.01.26 14:16:00 -
[2]
 Originally by: Amarrchick009
Originally by: Velonad Tyldamere
Free (B)Ander.
Originally by: Velonad Tyldamere
Free (B)Ander.
Originally by: Lee Dalton
Free Ander.
Freeing a person's IP involves a petition. API petitions don't take priority over internet spaceships, so please be patient.
|
|
|
CCP Adida
C C P
C C P Alliance
|
Posted - 2011.01.26 14:28:00 -
[3]
Removed spam posts
Adida
Community Rep
CCP Hf, EVE Online
|
|
|
CCP Stillman
|
Posted - 2011.01.26 15:53:00 -
[4]
Originally by: Stella Enallan
Is that the reason why EVEMon is no longer updating the data on my computer ?
Does a new version have to be released ?
No, EVEMon should still work correctly.
We're aware of another issue which causes the charactersheet to fail, which would affect EVEMon. We're fixing that as a part of Incursion 1.1.2, which is being deployed tomorrow.
|
|
|
CCP Stillman
|
Posted - 2011.01.27 13:40:00 -
[5]
Originally by: Wollari
Edited by: Wollari on 27/01/2011 13:24:40
Edited by: Wollari on 27/01/2011 13:16:56
Quote:
If you're an API developer: You should update your application to access the API using HTTPS. The overhead of HTTPS is not that big, even on mobile devices. Due to this, we will turn off normal HTTP access to the API in the future. When a specific date is decided for when this to happen we will make sure to give you appropriate advance warning
No ... SSL doesn't have an impact on your application :-)
Querying 25k Corporations (loop with 25k corpIDs, one by one)
with HTTP: 0:45 (h:mm)
with HTTPS: 1:15
Average query time (25k Corporations)
with HTTP: 0.9873s
with HTTPS: 1.6796s
I don't wanna go multithreaded to start a DoS on your API servers. I hope that you can keep the non-ssl connection open for public APIs. Apart from that requests with multiple corporationID_s_ would be nice.
If you're going to be doing large batches, you're obviously going to see a linear increase in time as a result of having to do a SSL handshake for each request.
It's advisable to limit SSL handshakes if you are going to do large queries like that. In those scenarios, there's nothing to stop you from creating a handful of persistent connections and pooling those for requests.
|
|
|
CCP Stillman
|
Posted - 2011.01.29 19:28:00 -
[6]
See PrismX's dev-blog for our plans when to stop supporting HTTP.
|
|
| |
|