Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Zeta Zhul
Caldari Preemptive Paranoia
|
Posted - 2011.06.22 00:48:00 -
[1]
Edited by: Zeta Zhul on 22/06/2011 00:49:15 You have to be kidding me on this.
$99/year for fail? Man you haven't heard screaming until people start having to pay for this crap.
|
Slow Poke
Dreddit
|
Posted - 2011.06.22 01:10:00 -
[2]
Did you even bother to read the patch notes?
API
* MarketOrders - orderID is now a 64-bit integer instead of 32-bit, and typeID is now a 32-bit integer instead of 16-bit. * WalletTransactions - transactionID is now a 64-bit integer instead of 32-bit. This applies to both char/ and corp/ pages, .csv and .xml. * MarketOrders should now only return a list of active and non-expired orders. * If you or your corporation produced more than a certain number of transactions between cache refreshes, the WalletTransactions page will only give you the oldest of those. On the other hand, the API will give you the latest number of transactions and you can page back to get the rest of them. * Error Throttling û the API will start to throttle third-party applications that generate a high number of preventable errors in a short period of time. This means better quality of service for everyone using the API.
|
INDUSTRON 3
|
Posted - 2011.06.22 01:24:00 -
[3]
Does anyone know if this means that OrderIDs will now be unique?
|
Zeta Zhul
Caldari Preemptive Paranoia
|
Posted - 2011.06.22 02:04:00 -
[4]
Originally by: Slow Poke Did you even bother to read the patch notes?
API
* MarketOrders - orderID is now a 64-bit integer instead of 32-bit, and typeID is now a 32-bit integer instead of 16-bit. * WalletTransactions - transactionID is now a 64-bit integer instead of 32-bit. This applies to both char/ and corp/ pages, .csv and .xml. * MarketOrders should now only return a list of active and non-expired orders. * If you or your corporation produced more than a certain number of transactions between cache refreshes, the WalletTransactions page will only give you the oldest of those. On the other hand, the API will give you the latest number of transactions and you can page back to get the rest of them. * Error Throttling û the API will start to throttle third-party applications that generate a high number of preventable errors in a short period of time. This means better quality of service for everyone using the API.
What precisely is the point? I read the dev blogs but didn't see anywhere that they were making any of these changes. There aren't any APIs set up on Sisi so we can't test anything.
|
Wendi Watson
Organization Too Secret To Know
|
Posted - 2011.06.22 02:59:00 -
[5]
http://www.eveonline.com/devblog.asp?a=blog&bid=924
|
Zeta Zhul
Caldari Preemptive Paranoia
|
Posted - 2011.06.22 03:59:00 -
[6]
Originally by: Wendi Watson http://www.eveonline.com/devblog.asp?a=blog&bid=924
I stand corrected. *shrug* meh. I really can't care much after seeing the failscade that is Incarna.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |