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 Technology Lab

 
  • Topic is locked indefinitely.
 

API Server and Front End - Development Edition
Author
Previous Topic Next Topic
Zress
Draken Industries
#1 - 2011-09-14 15:56:32 UTC
I would like to request CCP releasing a Development version of the API server with a "working" front end to create different types of API Keys. This will let developers to install it on their local XAMPP installation or web server, use it to development API retrieval systems without fear of pounding the real API server to death. This will also allow those of us who can't always develop online to work and test locally while traveling.

This may be a pipe dream, but i think it will help some of the developers and maybe take some strain off the live API system.

Thoughts, comments, file uploads?
Desmont McCallock
#2 - 2011-09-14 17:53:52 UTC
That's why CCP has also the API test server.
Zress
Draken Industries
#3 - 2011-09-15 03:55:28 UTC
Desmont McCallock wrote:
That's why CCP has also the API test server.

The main reason behind this is to be able to code offline with no internet. While the API test server is great myself, and probably some other developers, who can't check their code until they are able to get back online which hinders development.
Johnathan Roark
Quantum Industries
#4 - 2011-09-15 05:06:43 UTC
If your trying to check parsing, what I normally do is loaded a cached file. It really depends on what your trying to accomplish. A standalone system isn't going to have access to the database and something like xampp wont act like ccp's api servers. Maybe modify an install of a local caching proxy? But even that will have differences.

EVEVERIFY - A recruiting API Verification and Audit Tool

Also try out Yapeal for your php api needs
MrWhitei God
Sebiestor Tribe
Minmatar Republic
#5 - 2011-09-15 12:51:03 UTC  |  Edited by: MrWhitei God
Make your own version of the api interface.

Copy all the names for each API and store them in your own server.
You could then just access each API e.g http://localhost/char/CharacterSheet.xml.aspx

which would return a sample XML that you obtained from your own api details.

A couple simple IF statements to check if you have posted all the required fields to return the valid XML or return an error notification

EDIT:

forgot to mention you can add this to a .htaccess file so the aspx pages are run as php

AddType application/x-httpd-php .php .aspx
Zress
Draken Industries
#6 - 2011-09-15 15:00:39 UTC
MrWhitei God wrote:
Make your own version of the api interface.

Copy all the names for each API and store them in your own server.
You could then just access each API e.g http://localhost/char/CharacterSheet.xml.aspx

which would return a sample XML that you obtained from your own api details.

A couple simple IF statements to check if you have posted all the required fields to return the valid XML or return an error notification

EDIT:

forgot to mention you can add this to a .htaccess file so the aspx pages are run as php

AddType application/x-httpd-php .php .aspx


This may work, only question I have is how do I tell the local copies what permissions are required to access them? For example you need to have an access mask of 2 to access the assetlist.xml.aspx.
MrWhitei God
Sebiestor Tribe
Minmatar Republic
#7 - 2011-09-15 20:30:22 UTC
Zress wrote:

This may work, only question I have is how do I tell the local copies what permissions are required to access them? For example you need to have an access mask of 2 to access the assetlist.xml.aspx.


unfortunately, this is the part you have to put effort into.

simplest way:
you could just make 2 fake keys to use during testing.

1 key would be used as if it had the correct access mask, and the other as if you didnt have the right permissions

e.g.
if (accessKey=='KEY_WITH_PERMISSION')
{
output XML;
}
else if (accessKey=='KEY_WITHOUT_PERMISSION')
{
output UNAUTHORISED XML;
}
else
{
output INVALID KEY;
}