Pages: 1 [2] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 20 post(s) |
Karbowiak
4M-CORP Raiden.
89
|
Posted - 2013.02.04 09:21:00 -
[31] - Quote
CCP Prism X wrote:Squizzy is, sadly, right. And so are most other complaints here. There are numerous eccentricities with the return XMLs of the API. The lack of typeIDs returned with ownerIDs forcing extra calls, that may or may not error depending on the call and owner type and a complete lack of KillMail caching are probably the two most problematic issues at the moment. There are also numerous idiocies in the backend. There is no caching on erronous input so that every erronous request incurrs the full overhead of raising an exception, over and over again. Just the fact that the application keeps raising errors is a very bad decision that needs to be rethrough. And this is not acceptable for a live service that provides our customers with useful tools we do not seem to find the resources to develop. Sadly we're now in the situation, again, where we cannot find resources to maintain the API either. There is a short meeting later today where we'll go over the situation and I will be pushing for this situation to be amended rather than swept under the rug. Hopefully something will come out of that. And we are terribly sorry for the excessive disruption over the past few days. Sometimes you just need to rock the boat a fair bit more than usual to draw attention to the leak.
Here's to building an entirely new boat, instead of plugging the holes!
Anyways, hope you guys can figure something out, and hope you can keep us informed of the result |
Marcel Devereux
Aideron Robotics
200
|
Posted - 2013.02.04 11:38:00 -
[32] - Quote
Karbowiak wrote:CCP Prism X wrote:Squizzy is, sadly, right. And so are most other complaints here. There are numerous eccentricities with the return XMLs of the API. The lack of typeIDs returned with ownerIDs forcing extra calls, that may or may not error depending on the call and owner type and a complete lack of KillMail caching are probably the two most problematic issues at the moment. There are also numerous idiocies in the backend. There is no caching on erronous input so that every erronous request incurrs the full overhead of raising an exception, over and over again. Just the fact that the application keeps raising errors is a very bad decision that needs to be rethrough. And this is not acceptable for a live service that provides our customers with useful tools we do not seem to find the resources to develop. Sadly we're now in the situation, again, where we cannot find resources to maintain the API either. There is a short meeting later today where we'll go over the situation and I will be pushing for this situation to be amended rather than swept under the rug. Hopefully something will come out of that. And we are terribly sorry for the excessive disruption over the past few days. Sometimes you just need to rock the boat a fair bit more than usual to draw attention to the leak. Here's to building an entirely new boat, instead of plugging the holes! Anyways, hope you guys can figure something out, and hope you can keep us informed of the result
A new boat? I think you meant spaceship ;-)
|
Desmont McCallock
285
|
Posted - 2013.02.04 18:08:00 -
[33] - Quote
Silk daShocka wrote:I've read teh document that was linked to on the Eve-Kill site.
EveMon has an option in settings that appears to access the "Combat Log" every hour (I believe that's the default setting). Could this be causing EveKill to be getting errors as well? I have turned this option off entirely, since I don't use it myself.
If this setting in Evemon is causing issues for the killboards perhaps the EveMon developers could be contacted to have this feature removed since I don't think anyone really uses it.
Anyways, I really hope this can be sorted out so that Eve-Kill can operate as it has to this day. If I, by adding the "Combat Log" monitor in EVEMon, am the cause of all this, then I should be praised and not be blamed, for exposing the faults of the 'accursed' API call. And I really don't understand your logic of 'arm hurts, cut arm', on blaming EVEMon and asking for the feature to be removed, when those issues are common knowledge to all killboard site devs and are happening for years. To tell you the truth I avoided adding that feature for years now, knowing the side effects it may cause. I finally decided to add it, under CCP's concept that we are the 'Enablers' and that CCP should adjust to our needs and not we to CCP's.
It's about time CCP gives some love to the API.
Edit: Currently, I have 'high esteem ' only for CCP PrismX among the CCP staff. (Although I admit that CCP Puncturis is my second favorite). |
Squizz Caphinator
Happy Endings
81
|
Posted - 2013.02.04 18:42:00 -
[34] - Quote
Desmont,
I noticed when you added the combat log to EveMon and I remember thinking "oh yay, more 119's!", but I don't fault you for it. You're only adding a feature that your users would like to see :)
Silk daShocka,
EveMon very well could be causing some of the errors, and that would explain why I've noticed a pattern in 119's on an hourly basis: Higher during EU and US prime timezones, whereas Chinese/Russian prime timezones tend to have fewer 119's. I can only speculate that more people (e.g. English speakers) have their machines turned on with EveMon running which then forces competition for the KillLog request during those hours where 119 errors are peaking.
The biggest competition, however, isn't with EveMon. It is between zKB/Eve-Kill and Battleclinic. Users who have provided their keys to each killboard merely wants to see their kills in each website. Can't really blame the user for this as they expect the API to "Just Work (TM)." Various projects I enjoy putting my time into: http://eve-kill.net | http://zkillboard.com | http://evewho.com | http://evechatter.com | http://skillq.net |
Lorren Canada
Sniggwaffe YOUR VOTES DON'T COUNT
248
|
Posted - 2013.02.05 11:11:00 -
[35] - Quote
Fucking nerds |
Squizz Caphinator
Happy Endings
82
|
Posted - 2013.02.05 14:13:00 -
[36] - Quote
Lorren Canada wrote:Fucking nerds
damn right! Various projects I enjoy putting my time into: http://eve-kill.net | http://zkillboard.com | http://evewho.com | http://evechatter.com | http://skillq.net |
Barakkus
1859
|
Posted - 2013.02.06 03:34:00 -
[37] - Quote
I'll fix it. :)
http://youtu.be/yytbDZrw1jc |
Latino lover
Nu shtiu ROMANIAN-LEGION
1
|
Posted - 2013.02.06 06:22:00 -
[38] - Quote
ok , I'm a noob , I don't understand why are they banned... I didn't change my api or done anything with it since you introduced api custimizsation ... and now aftere 2 years i'm trying to introduce it on a killboard and a I get this "Your IP address has been temporarily blocked because it is causing too many errors. See the cacheUntil timestamp for when it will be opened again. IPs that continually cause a lot of errors in the API will be permanently banned, please take measures to minimize problematic API calls from your application." |
Tonto Auri
Vhero' Multipurpose Corp
25
|
Posted - 2013.02.10 12:29:00 -
[39] - Quote
CCP Prism X wrote:Squizzy is, sadly, right. And so are most other complaints here. There are numerous eccentricities with the return XMLs of the API. The lack of typeIDs returned with ownerIDs forcing extra calls, that may or may not error depending on the call and owner type and a complete lack of KillMail caching are probably the two most problematic issues at the moment. There are also numerous idiocies in the backend. There is no caching on erronous input so that every erronous request incurrs the full overhead of raising an exception, over and over again. Just the fact that the application keeps raising errors is a very bad decision that needs to be rethrough. And this is not acceptable for a live service that provides our customers with useful tools we do not seem to find the resources to develop. Sadly we're now in the situation, again, where we cannot find resources to maintain the API either. There is a short meeting later today where we'll go over the situation and I will be pushing for this situation to be amended rather than swept under the rug. Hopefully something will come out of that. And we are terribly sorry for the excessive disruption over the past few days. Sometimes you just need to rock the boat a fair bit more than usual to draw attention to the leak. Told you, just set up nginx in front of your API servers. You won't need to worry about caching any longer. At least the continuous feeds, that are not time-critical, like kill logs, can be safely front-ended by it, or other caching server. |
Aineko Macx
Royal Amarr Institute Amarr Empire
247
|
Posted - 2013.03.02 10:56:00 -
[40] - Quote
cachedUntil is a misnomer, an euphemism at best, until CCP actually start caching (and returning cached) results. |
|
Galmas
United System's Commonwealth R.E.P.O.
86
|
Posted - 2013.03.02 17:23:00 -
[41] - Quote
Caius Sivaris wrote:Writing that as a CEO, not a direct API user.
Is there a supported way for me to have my corp kill log fed to both BC and eve-kill without getting one alt with director rights to create the API for the second killboard?
If Squizz, is right, and I've little doubt he is, and if I understand him correctly, that's not possible.
Is that acceptable, I don't think so, kill feed is the poster child for something a memcached deployment would improve drastically and those limitation don't shed a good light on CCP Engineering.
Sorry for spamming this in here but i havnt found any really 100% proper resource that explains how to overcome the "two killboards one corp/alliance" problem.
Does that alt with killlog rights need to be on a different account or doest it work when it is just a different character's api key of the same game account?
Thanks, Regards Gal |
Ydnari
Estrale Frontiers Project Wildfire
159
|
Posted - 2013.03.02 17:41:00 -
[42] - Quote
Galmas wrote:Caius Sivaris wrote:Writing that as a CEO, not a direct API user.
Is there a supported way for me to have my corp kill log fed to both BC and eve-kill without getting one alt with director rights to create the API for the second killboard?
If Squizz, is right, and I've little doubt he is, and if I understand him correctly, that's not possible.
Is that acceptable, I don't think so, kill feed is the poster child for something a memcached deployment would improve drastically and those limitation don't shed a good light on CCP Engineering. Sorry for spamming this in here but i havnt found any really 100% proper resource that explains how to overcome the "two killboards one corp/alliance" problem. Does that alt with killlog rights need to be on a different account or doest it work when it is just a different character's api key of the same game account? Thanks, Regards Gal
different account |
Vicata Heth
Corporate Scum Test Friends Please Ignore
41
|
Posted - 2013.03.02 21:06:00 -
[43] - Quote
Cache your results CCP, or GTFO. |
|
|
|
Pages: 1 [2] :: one page |
First page | Previous page | Next page | Last page |