Pages: 1 2 [3] 4 5 6 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
4
|
Posted - 2012.04.14 21:05:00 -
[61] - Quote
Thanks! :)
*goes to play with the api* |
Karbowiak
Deep Core Mining Inc. Caldari State
58
|
Posted - 2012.04.14 21:55:00 -
[62] - Quote
Fixed a but where the ships id wasn't shown in the involved party list, apparently the database field was changed from shp_external_id to shp_externalid..
Checking if there are any other similar bugs, that have creeped in. But there shouldn't be (Since every other function uses standard EDK calls) |
Karbowiak
Deep Core Mining Inc. Caldari State
58
|
Posted - 2012.04.17 09:50:00 -
[63] - Quote
Upped the mail limit 500, as some people needed to have it return more mails..
The default is still 100 tho :) |
Karbowiak
Deep Core Mining Inc. Caldari State
58
|
Posted - 2012.04.19 17:39:00 -
[64] - Quote
I have added two new calls, startDate and endDate.
They are both a little weird due to the way calls are handled, so if you write YYYY-MM-DD H:i:s - only YYYY-MM-DD H is actually passed on.
Instead you should write YYYY-MM-DD H.i.s, then it works Also it cannot span months, so it only works within a month, but it can be used to help get all mails for specific pilots, corps, alliances, ship etc. better than minKLLid and maxKLLid can.
Examples: http://eve-kill.net/epic/victimCorp:Future_Corps/mask:262150/startDate:2012-04-17%2000.00.00 http://eve-kill.net/epic/victimCorp:Future_Corps/mask:262150/startDate:2012-04-01%2000.00.00/endDate:2012-04-04 http://eve-kill.net/epic/system:Jita/mask:1606910/mailLimit:250/startDate:2012-03-01/endDate:2012-03-02
Also startDate / endDate override year/week settings ;) |
Karbowiak
Deep Core Mining Inc. Caldari State
58
|
Posted - 2012.04.19 18:00:00 -
[65] - Quote
Updated the cache time of varnish, so instead of 60 minutes pr. url request, it's now 15 minutes.
Should hopefully not raise load too much (Not that many that's using it yet tho - so dunno) |
Karbowiak
Deep Core Mining Inc. Caldari State
58
|
Posted - 2012.04.20 19:31:00 -
[66] - Quote
added a new call, 'APIOnly'
Set it to true, and it does what you'd expect.
Only show mails that are API Verified! ;)
Example: http://eve-kill.net/epic/victimShipClass:Battlecruiser/onlyapi:true/mask:787423
|
Karbowiak
Deep Core Mining Inc. Caldari State
58
|
Posted - 2012.04.28 13:04:00 -
[67] - Quote
And up we go! |
Karbowiak
Deep Core Mining Inc. Caldari State
58
|
Posted - 2012.05.01 21:22:00 -
[68] - Quote
Added two new calls, NoTowers and FBPilotName.
NoTowers doesn't have a true or false statement, it's just added to the url (like onlyAPI) /epic/noTowers/stuff
And FBPilotName takes a pilots name, and uses it to sort for the final blow pilot.
Enjoy! :) |
Penny Brothers
School of Applied Knowledge Caldari State
0
|
Posted - 2012.05.07 23:37:00 -
[69] - Quote
Question on startDate and endDate formats.
If I use a URL with an underscore for the endDate date time separator then the endDate seems to be being ignored
e.g.
http://eve-kill.net/epic/mailLimit:500/system:FD-MLJ/startDate:2012-03-01_11.20.00/endDate:2012-03-19_12.20/mask:557586
returns
[{"timestamp":"2012-05-07 22:42:00","victimName":"Cpt Angus","victimShipClass":"Covert ops" ....(snip)
however if I use a space in the URL as date and time separator for the endDate then all seems to work ok
e.g.
http://eve-kill.net/epic/mailLimit:500/system:FD-MLJ/startDate:2012-03-01_11.20.00/endDate:2012-03-19%2012.20/mask:557586
returns
[{"timestamp":"2012-03-19 11:00:00","victimName":"Ilya Dahmas","victimShipClass":"Battlecruiser","solarSystemName":"FD-MLJ", ... (snip)... {"timestamp":"2012-03-10 21:58:00"
however using space as a separator in the startDate e.g. http://eve-kill.net/epic/mailLimit:500/system:FD-MLJ/startDate:2012-03-01%2011.20.00/endDate:2012-03-19%2012.20/mask:557586
returns nothing.
Is this a bug or is it by design?
|
Jack O'Connal
Merkhan Industries Rebel Alliance of New Eden
0
|
Posted - 2012.05.10 00:50:00 -
[70] - Quote
I couldn't sleep last night so I threw this together to experiment with your API.
http://www.privatepaste.com/17f9e01ee5
I'm a bit of a noob with LINQ so if you see any way to improve this code I'd love to hear about it.
|
|
Karbowiak
Deep Core Mining Inc. Caldari State
60
|
Posted - 2012.05.10 09:53:00 -
[71] - Quote
Sorry, end and startDate filters are a bit weird.
you don't _HAVE_ to add the time part tho. As for how it's made to work right now, i'll rework it so it uses unixtimestamps instead. should work a million times better than the current implementation (No . or spaces) |
Karbowiak
Deep Core Mining Inc. Caldari State
60
|
Posted - 2012.05.10 09:54:00 -
[72] - Quote
Jack O'Connal wrote:I couldn't sleep last night so I threw this together to experiment with your API. http://www.privatepaste.com/17f9e01ee5I'm a bit of a noob with LINQ so if you see any way to improve this code I'd love to hear about it.
Cool, i know nothing about LINQ, s+Ñ yeah - to me it looks good :P |
Desmont McCallock
172
|
Posted - 2012.05.10 10:08:00 -
[73] - Quote
Since .NET 3.5 there is native support for JSON. You need only to add reference to System.Web.Extensions and JavaScriptSerializer will be available for JSON serialization and deserialization.
Edit: LINQ can also be used as methods chain (with lamda expressions) for those who have difficulties understanding the syntax. |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
6
|
Posted - 2012.05.12 11:07:00 -
[74] - Quote
Built-in json serializer engine is crap, json.net is far better and will become the built-in json engine for .net.
|
Etil DeLaFuente
New Eclipse Initiative Mercenaries
6
|
Posted - 2012.05.13 13:55:00 -
[75] - Quote
Jack O'Connal wrote:I couldn't sleep last night so I threw this together to experiment with your API. http://www.privatepaste.com/17f9e01ee5I'm a bit of a noob with LINQ so if you see any way to improve this code I'd love to hear about it.
You're wasting a lot of time parsing the json.
First, create your models, classes that represent what you'll need, than just deserialize the json. The json.net API has some nice features to achieve your goals.
Since i can't post an example without getting a forum error :CCP:, you can find the full code here : http://pastebin.com/JNPid67Q |
Karbowiak
Deep Core Mining Inc. Caldari State
67
|
Posted - 2012.05.15 17:03:00 -
[76] - Quote
Interesting to watch people actually make libraries for using EPIC.
I have started work on getting EPIC put into every EDK board out there (by making it part of EDK itself). First i have to make a fetcher for EDK boards tho, but hey - easy peasy! :P |
Khorkrak
War Tribe
6
|
Posted - 2012.06.15 01:49:00 -
[77] - Quote
Nice work! I've just finished writing some code to process kill data retrieved from your epic api. Next I need to write a process to automate fetching the data as I'd like to load relatively recent kills into my killboard from it. Hopefully, this api is far less resource intensive than the idfeed one is. Still though, how often should requests be made to avoid taxing eve-kill.net too much? What's the recommendation in comparison with the idfeed one where it's 50 kill mails per half hour?
The only issues I see with the data are that it appears there's no way to get the victim faction name and id from this unless I simply missed it. Also, for POS related kills, the victim name is the moon - like 'Moon 8' instead of being an empty string with a moonID field present and filled in with a non-zero value instead akin to the EVE API based kill mails. No big deal though. This is quite nice for testing things out. Thanks!
Note: it is possible to generate the JSON results directly in the database using group_concat and case statements thus avoiding having to do any string concatenations, looping and so forth in pokey PHP. While the queries to do so would be heinous looking it would nevertheless be far more efficient overall. Extraordinary claims require extraordinary evidence |
Karbowiak
Superior Mass
67
|
Posted - 2012.06.15 16:37:00 -
[78] - Quote
Khorkrak wrote:Nice work! I've just finished writing some code to process kill data retrieved from your epic api. Next I need to write a process to automate fetching the data as I'd like to load relatively recent kills into my killboard from it. Hopefully, this api is far less resource intensive than the idfeed one is. Still though, how often should requests be made to avoid taxing eve-kill.net too much? What's the recommendation in comparison with the idfeed one where it's 50 kill mails per half hour? The only issues I see with the data are that it appears there's no way to get the victim faction name and id from this unless I simply missed it. Also, for POS related kills, the victim name is the moon - like 'Moon 8' instead of being an empty string with a moonID field present and filled in with a non-zero value akin to the EVE API based kill mails. No big deal though. This is quite nice for testing things out. Thanks! Note: it is possible to generate the JSON results directly in the database using group_concat and case statements thus avoiding having to do any string concatenations, looping and so forth in pokey PHP. While the queries to do so would be heinous looking it would nevertheless be far more efficient overall. hmm I only get 1 kill mail from this: wget -O results.dat http://eve-kill.net/epic/minKLLid:13000000/maxKLLid:13000500/mailLimit:500/mask:1607166No different if I leave off the mailLimit.
Thanks for the kind words, as for how many times, i'd say once every 30 minutes would be fine, or every 60. If you have any tips and ideas to what it lacks i'll gladly listen and see if i can't add it without alot of overhead.
Also, you should use the datetime stuff instead of minkllid / maxkllid, since the min/maxkllid stuff is rather dumb. It easily jumps over kills and ignores others for unknown reasons (the query doesn't exlude mails, but it does for some reason anyway :\) |
Khorkrak
War Tribe
7
|
Posted - 2012.06.16 14:03:00 -
[79] - Quote
Thanks that worked well:
wget -O results.dat http://eve-kill.net/epic/startDate:2012-01-01_00.00.00/endDate:2012-01-01_01.00.00/mailLimit:500/mask:1607166
Extraordinary claims require extraordinary evidence |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
9
|
Posted - 2012.06.17 11:17:00 -
[80] - Quote
I have the same problem retrieving killmails history. The order is by date descending.
So if the max kill number is reached, make another request with the same starting date and the minimum date you received . You'll have to do it as long as you reached the limit.
Would be more logical to get kills ordered by date ascending tho. |
|
Khorkrak
War Tribe
7
|
Posted - 2012.06.17 14:49:00 -
[81] - Quote
Not quite seeing that. Here's a different example - note the dates and times specified:
-- Get everything for January 2012 but limit it to 500 since I seem to be getting stuff at the end of the end anyway so lets try it > wget -O results.dat http://eve-kill.net/epic/startDate:2012-01-01_00.00.00/endDate:2012-01-31_23.59.59/mailLimit:500/mask:1607166
> python Python 2.7.3 (default, Apr 20 2012, 22:44:07) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import simplejson as json >>> kills = json.load(file("results.dat")) >>> dates = [k["timestamp"] for k in kills] >>> dates.sort() >>> dates[0] '2012-01-31 22:42:00' >>> dates[-1] '2012-01-31 23:59:00' >>>
So the earliest datetime is 2012-01-31 22:24:00 which makes sense based on the descending order you mentioned above. That's fine. Now lets set the end date to the earliest date from above and requery.
> wget -O results.dat http://eve-kill.net/epic/startDate:2012-01-01_00.00.00/endDate:2012-01-31_22.42.00/mailLimit:500/mask:1607166
> python Python 2.7.3 (default, Apr 20 2012, 22:44:07) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import simplejson as json >>> kills = json.load(file("results.dat")) >>> dates = [k["timestamp"] for k in kills] >>> dates.sort() >>> dates[0] '2012-01-31 22:42:00' >>> dates[-1] '2012-01-31 23:59:00' >>>
Now I'm perplexed, I got the same data even with a different end datetime Why are kills returned that are outside of the datetime range specified? What am I doing wrong? Seems like the time part is being ignored - maybe I'm not specifying it correctly - I'll double check the instructions. Extraordinary claims require extraordinary evidence |
Etil DeLaFuente
New Eclipse Initiative Mercenaries
9
|
Posted - 2012.06.17 22:57:00 -
[82] - Quote
Might have something to do with time. I never specify it. Maybe you should filter a bit more too, do you really need all the killmails ? |
Nomad I
University of Caille Gallente Federation
77
|
Posted - 2012.06.25 19:41:00 -
[83] - Quote
What is with the values like Pilot Efficiency, Damage Done, Damage received, Kills and losses related to a month or a year? |
Karbowiak
Superior Mass
67
|
Posted - 2012.07.12 18:39:00 -
[84] - Quote
I decided to add rawmail support, seeing as i'll be working on a feed mechanism for EDK, using EPIC rather than IDFeed.
Seeing as IDFeed is horrible..
To use it, use the mask id 2097152 Everything is serialized, gzipped and base64_encoded, to decode it and get the rawmail, in php it's done the following way.
$mail = unserialize(gzuncompress(base64_decode($rawmail)));
Anyway, have fun with it, and don't abuse it, please :) |
Shellac Brookdale
RAZOR Alliance
6
|
Posted - 2012.07.18 19:16:00 -
[85] - Quote
Any chance to provide the killmail in the same xml format idfeed uses? That would make migration from idfeed to epic much easier. |
Karbowiak
Superior Mass
67
|
Posted - 2012.07.19 18:07:00 -
[86] - Quote
Shellac Brookdale wrote:Any chance to provide the killmail in the same xml format idfeed uses? That would make migration from idfeed to epic much easier.
that'd require i translate it all into an xml sheet, which isn't gonna happen, ever.. It's json and then this pseudo gzipped thingy raw mail :) |
Karbowiak
Superior Mass
67
|
Posted - 2012.07.19 18:23:00 -
[87] - Quote
Added a new method called orderBy
It can be used with DESC and ASC.. Before everything was sorted by DESC, now it's sorted by ASC. So you might have to fix some methods for fetching stuff from EPIC now, sorry
But now the startDate and endDate methods work as expected (unless you select to use DESC, then it fails again) And minKLLid and maxKLLid also works, which was due to a bug in the else if structure (apparently it kicked kllid before minkllid, who knew!)
Now im off to code a mail fetcher for EDK using EPIC! woo |
Karbowiak
Superior Mass
67
|
Posted - 2012.07.19 21:13:00 -
[88] - Quote
another bug fixed, apparently i forgot to urldecode stuff, so it would fail on some names, that is now fixed! |
Karbowiak
Superior Mass
67
|
Posted - 2012.07.19 21:53:00 -
[89] - Quote
I have altered the space to a + instead of a _
No worries, if you havn't done it, it does it for you, aslong as CCP doesn't allow _ in names, we'll be fine |
Karbowiak
Superior Mass
67
|
Posted - 2012.07.20 15:25:00 -
[90] - Quote
im currently redoing the raw part, i'll update this post with information (apparently doing it with a raw mail was insanely horrible, who knew! ) |
|
|
|
|
Pages: 1 2 [3] 4 5 6 :: one page |
First page | Previous page | Next page | Last page |