Pages: [1] 2 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Jone Sad
The Scope Gallente Federation
5
|
Posted - 2017.01.10 00:49:50 -
[1] - Quote
Simple question - is it gonna to die in next year\two? Don't want to spent time if it will be deprecated in a year.
And where is full description of it? A lot of changes were done i've use it before.
PS: Is there any another alternative except 'access token'? Access tokens (i means requests with headers the worst solution in internet ever) not best solution same as oauth for eve. =\ |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
6360
|
Posted - 2017.01.10 03:02:47 -
[2] - Quote
Jone Sad wrote:Simple question - is it gonna to die in next year\two? Don't want to spent time if it will be deprecated in a year.
And where is full description of it? A lot of changes were done i've use it before.
PS: Is there any another alternative except 'access token'? Access tokens (i means requests with headers the worst solution in internet ever) not best solution same as oauth for eve. =\
Yes, it's going to die within the next 16 months or so.
No, it's not going to change from using oauth. So that's access tokens, and refresh tokens to create them at will.
Bear in mind, it's pretty much the same as the vcode and key.
Woo! CSM XI!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
Jone Sad
The Scope Gallente Federation
5
|
Posted - 2017.01.10 10:38:28 -
[3] - Quote
It's bad, ccp killing simple "play" with api. This oauth really annoying thing... |
Jone Sad
The Scope Gallente Federation
5
|
Posted - 2017.01.10 10:41:26 -
[4] - Quote
But hey, does the crest or sso cover all xml api? Cannot find how to get using it corp data. Where is description? |
Messenger Of Truth
Butlerian Crusade
79
|
Posted - 2017.01.10 12:51:23 -
[5] - Quote
No, CREST/ESI do not cover all of the XML API. But they cover a lot of it.
The calls are completely different. (The format is JSON rather than XML, for example).
Trade Hub Price Checker: stop.hammerti.me.uk/pricecheck
Visit "Haulers Channel" in game for all matters courier-related.
Structure name/system API: stop.hammerti.me.uk/api
|
Jone Sad
The Scope Gallente Federation
5
|
Posted - 2017.01.10 13:08:48 -
[6] - Quote
Messenger Of Truth wrote:No, CREST/ESI do not cover all of the XML API. But they cover a lot of it.
The calls are completely different. (The format is JSON rather than XML, for example).
If they don't - it's useless at all. That crest/esi is useless, hate already it. =\
Really? Common man, there is no difference at all, json or xml.... But realization of that oauth and xml api (simple get) - role.
By api you could do everything, simple and quick. Now about 80% all already written eve-api software will be disabled because "omg wtf is this, how can i retrieve simple data?".
In next year (if ccp will disable its xml api) only developers (I mean real developers) can use their "smart" api... And without real money as payment yeah? That means that all community will do software only for themself in private repositories and if they have such developer. who will spent his time, not payed time.
GOOD LUCK CCP, YOU DO THE SAME AS ALWAYS, BROKING...
PS: You spent SOOOOOOOOOOOOOO many time to create new oauth and api but... Did you count queries required now for any data call? Hello access tokens.... What next? Payed limit for queries? AHAHAHAHAH...
|
Blacksmoke16
Resilience.
38
|
Posted - 2017.01.10 14:22:28 -
[7] - Quote
Someone is butt hurt. |
Jone Sad
The Scope Gallente Federation
5
|
Posted - 2017.01.10 14:46:19 -
[8] - Quote
Blacksmoke16 wrote:Someone is butt hurt. Yep, because every monkey want "social login" (oauth) on its site, but don't know how developers suffer about it. =\ |
Blacksmoke16
Resilience.
38
|
Posted - 2017.01.10 15:00:29 -
[9] - Quote
Personally, yes it is a bit more in dept than just doing a GET request to an endpoint to get data.
BUT, being able to use tokens for the XML API, being able to open windows using ESI and being able to do things that developers could only dream of with only the XML makes it all worth it.
The convenience of just having people log in like they would into the game and boom have data is much better than having to make an API key, give it to someone and manage all of them.
In addition, dealing with JSON from the ESI/CREST endpoints are much easier to work with than the XML API. XML API by industry standards itself is pretty old. You can read up more on why they decided to do it here: https://community.eveonline.com/news/dev-blogs/introducing-esi/
Personally you are the only one that is against the OAuth that i have come across. |
Jone Sad
The Scope Gallente Federation
5
|
Posted - 2017.01.10 16:20:06 -
[10] - Quote
Blacksmoke16 wrote:Personally, yes it is a bit more in dept than just doing a GET request to an endpoint to get data. BUT, being able to use tokens for the XML API, being able to open windows using ESI and being able to do things that developers could only dream of with only the XML makes it all worth it. The convenience of just having people log in like they would into the game and boom have data is much better than having to make an API key, give it to someone and manage all of them. In addition, dealing with JSON from the ESI/CREST endpoints are much easier to work with than the XML API. XML API by industry standards itself is pretty old. You can read up more on why they decided to do it here: https://community.eveonline.com/news/dev-blogs/introducing-esi/ Personally you are the only one that is against the OAuth that i have come across.
XML is only file format. So as I said there is no real point between xml\json even txt... I don't think you do realize it. So oauth and json is not connected. XML api can be changed EASILY to json if ccp will want. It's only output data. Ok? Ok...
You are saying that CREST is good, ok, what it can, that i cannot do using xml api? What this crest adds to api? Nothing, it return same data but now in another (harder) way.
Next one, for those who is not understand - SSO is way to get keyID\vCode simplier. So if you use it now - you will not ask members of your corp create new api, it would be enought ask them login. Nothing new! You realize it? Is it easier? For member - yes, but what about developer? Now you use accessToken against keyID\vCode. But now this accessToken should be obtain in hard way (hello oauth).
ESI or what ever... Same! Same data as prev. xml api, no? New Features? For whom? As I said, old XML api gives us everything player\developer need in easy way. Now, developer need create sites with authenticatoin + oauth (what for!?!) to get some data. And i won't say about refresh token call count.
So, to clearfy this. What this new CREST and ESI can? For what it was created, can someone describe? With real examples, not just "it's cooler"... =\ |
|
Blacksmoke16
Resilience.
38
|
Posted - 2017.01.10 20:49:41 -
[11] - Quote
ESI/CREST allows you to:
Open windows within the client from your app Save/read fittings from your app Invite people, add wings, kick people, read fleet data etc from your app Add/edit contacts from your app Update the vulnerability times on structures from your app Create/delete mail labels and send/edit/delete mails from your app
Plus whatever will be added in the future.
So please tell me how I can do this stuff with the XML API.
|
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
6361
|
Posted - 2017.01.10 22:52:32 -
[12] - Quote
Blacksmoke16 wrote:ESI/CREST allows you to: Open windows within the client from your app Save/read fittings from your app Invite people, add wings, kick people, read fleet data etc from your app Add/edit contacts from your app Update the vulnerability times on structures from your app Create/delete mail labels and send/edit/delete mails from your app Set/change destination from your app Update calendar events from your app Read current location/ship in nearly real time from your app Plus whatever will be added in the future. So please tell me how I can do this stuff with the XML API.
ding ding ding, we have a winner.
CREST interacts with Eve at the same level as the client/ the XML api is a nasty behind the scenes hack which interacts with the database directly, so can't touch game state. It's also read only, where as CREST is read/write
Woo! CSM XI!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
Nacoya Acoma
Republic Military School Minmatar Republic
0
|
Posted - 2017.01.11 05:49:58 -
[13] - Quote
Is there a matrix or something along those lines that shows developers where the parity short falls are with Swagger/CREST are to help guide traffic towards the "new" way.
Also does this mean the whole Key/ValidationCode system is redundant going forward completely?
|
Japetus
Mors et Tributum The DNA Conglomerate
0
|
Posted - 2017.01.11 06:45:02 -
[14] - Quote
I know the original API is going, and Im fine with that... I just need to learn some things I didnt know before and I'm all for that... This is just a game, but the stuff I learn while writing things for that game can be carried into rl so yeah Im fine with the changes.
However my question is this... ppl are talking about the API going, which I get but on the other side they are talking about converting to Crest/ESI as in both are staying
Correct me if Im wrong but arent the original API, Crest, and Swagger all separate entities? And didn't they say they were eliminating all but swagger?
I only ask cause I'll use CREST some more if its staying around but I have been trying to stick to just the new stuff on the assumption that the other 2 were going to be eliminated
Thanks |
Zad Murrard
Frozen Dawn Inc Frozen Dawn Alliance
46
|
Posted - 2017.01.11 07:33:08 -
[15] - Quote
Personally I see nothing bad with the current xml API.
It serves a different purpose. No reason to remove the API unless it causes some really strong technical challenges in CCP side. |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
6361
|
Posted - 2017.01.11 13:14:52 -
[16] - Quote
Japetus wrote:I know the original API is going, and Im fine with that... I just need to learn some things I didnt know before and I'm all for that... This is just a game, but the stuff I learn while writing things for that game can be carried into rl so yeah Im fine with the changes.
However my question is this... ppl are talking about the API going, which I get but on the other side they are talking about converting to Crest/ESI as in both are staying
Correct me if Im wrong but arent the original API, Crest, and Swagger all separate entities? And didn't they say they were eliminating all but swagger?
I only ask cause I'll use CREST some more if its staying around but I have been trying to stick to just the new stuff on the assumption that the other 2 were going to be eliminated
Thanks
You're correct. The final goal is just ESI, not CREST or the XML API.
There's some structural issues with the latter two, which are being eliminated with ESI.
(However, bear in mind that the goal date for elimination is 15 months away or so. And there won't be feature parity until closer to that date)
Woo! CSM XI!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
Jone Sad
The Scope Gallente Federation
5
|
Posted - 2017.01.11 17:25:20 -
[17] - Quote
More uncomplete apis! CCP have only one hired developer for API? LOL
CCP killing desire to use their apis... New means good? Don't think so...
At this moment we have x3 apis (methodic)? Am I wrong? So flexible, but what for!?!?! There is no total\full working manuals for them. Only links for official methods how should it work in internet (hello oauth)..
And ppl should "learn more", nice, rly... And what about that who don't want? Yes - he won't use your api. XML API was simple - even in simple script anyone could receive data. Common, he even can ask friends do this one (who not playing eve) because it was easy. But now... You ask then create real software for free....
Best move ever. XD
Sad one that you cannot stop! There was xml api and it was (and still) good. Then came crest... Then came sso... Now coming ESI. Common! Stop this! When will be a point with "all works and have full manual"? My children has grew up and you cannot do your job. You know what is deadline? XD And you ask use latest... Never - latest is not good, latest means - uncomplete. |
Mr Twinkie
Black Serpent Technologies The-Culture
46
|
Posted - 2017.01.11 18:12:20 -
[18] - Quote
Zad Murrard wrote:Personally I see nothing bad with the current xml API.
It serves a different purpose. No reason to remove the API unless it causes some really strong technical challenges in CCP side.
This... API is a reliable proven system for getting information in an easy manner. Yes ESI/CREST have some cool PUT abilities but the majority of developers are just looking for info not trying to make your map pop up and flash dickbutt patterns at you.
MAMBA/The-Culture Head of IT
Dramiel - An EVE Bot for Discord
!!Hosted Dramiel Service!!
|
Nacoya Acoma
Republic Military School Minmatar Republic
0
|
Posted - 2017.01.12 02:16:57 -
[19] - Quote
- Industry, in general, is moving towards Swagger because of its self-documenting approach.
- Any time you depend on a 3rd party for your API needs, you always bake in assumption fails. Whether it be verbs in the endpoints or data coming back, you always layer in abstraction to self-guard your domain. For example, CCP uses "int" for their ID system, whereas I use GUIDs ..I absorb the int and catch it but in my own relational model, I rely on my own.
- CCP need to learn how to finish what they start, maybe the ESI is the answer to that but from what I've seen so far its "shiny object syndrome" development.
- I'm fine with the deprecation of code, provided you can establish a map out of where we are today to where will be tomorrow. Alongside some healthy actual roadmap.
- The implementation of Swagger at the moment relies heavily on multiple "_" to break up the verb(s). In most tooling right now with swagger they typically prefer it to be verb_action (one) so already they're likely to run up against code-gen tooling etc.
- Single Sign On is unnecessary. There is again no point to linking a user(s) actual in-game credentials to 3rd party app development. It encourages security failing(s) for one and it's like asking for your driver's license to buy a carton of milk. The Key/AuthCode approach was actually more realistic and encourages the end-users to monitor their allocation of data to 3rd party apps in a centralised fashion (constancy and consistency in one with an emphasis on strengthening behaviour not weakening it - as the user continues to approve/reject in the one spot. SSO fragments the user's cognitive intelligence by requiring them to take a position without context to other applications - moreover - you can also encourage the user to compartmentalise their authority groupings by letting them define their own taxonomy). SSO also is harder for developer(s) to utilise outside a web-only solution than a simple credential based one found in the current XML way.
|
Whitney Aubaris
AWOLGamers
2
|
Posted - 2017.01.13 14:07:54 -
[20] - Quote
I am cool with the idea of the new codes although it would be nice if they kept the old simple API keys for the newbs like me who can only just scrape by with the little code we know.
I just spent a week building my self a vary good looking fully detailed site that runs off just API grabs and now I hear they are going to change how we get the info. Makes me wish I didn't wast my time with any of it.
C.orporate C.ontrol P.ointing
E.veryone's V.ision E.lsewhere
Fly Safe everyone o7 |
|
Jone Sad
The Scope Gallente Federation
7
|
Posted - 2017.01.13 15:06:42 -
[21] - Quote
Whitney Aubaris wrote:I am cool with the idea of the new codes although it would be nice if they kept the old simple API keys for the newbs like me who can only just scrape by with the little code we know.
I just spent a week building my self a vary good looking fully detailed site that runs off just API grabs and now I hear they are going to change how we get the info. Makes me wish I didn't wast my time with any of it.
C.orporate C.ontrol P.ointing
E.veryone's V.ision E.lsewhere
Fly Safe everyone o7
Your time wasted, same as any developer that will do any software now. :(
Lest look closer.
You need sso. Then you should use latest 'good' api it's seems like CREST !?!? But it's not full! So... You will use XML API, that will be deprecated in a year, mb more. And what now you think "wtf then what i should use?". Everyone say use ESI new and cool! But... ESI same as CREST - has not full api calls that REALLY needed. It's like have titan but you have no injected skills for it. You forgot about BASIC things. People use api first of all for CORPORATION, not for single use...
FOR CCP: First of all you HAVE TO implement wallets (corp\char), assets (corp\char), mails\notifcations (corp\char) and ONLY after that do you want. Without it it's not api - it something useless...
BTW only XML API (vCode + keyID) was done completely. All others cannot be used standalone from other apis (crest\esi\sso). It's means that I should learn ALL that thrash (uncomplete) that you did to create own working well application and use several api types. NICE. And noone know, what api will be deprecated next...
PS: My butt hurt doesn't know the end.... XD |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
6371
|
Posted - 2017.01.13 18:02:15 -
[22] - Quote
Whitney Aubaris wrote:I am cool with the idea of the new codes although it would be nice if they kept the old simple API keys for the newbs like me who can only just scrape by with the little code we know.
I just spent a week building my self a vary good looking fully detailed site that runs off just API grabs and now I hear they are going to change how we get the info. Makes me wish I didn't wast my time with any of it.
C.orporate C.ontrol P.ointing
E.veryone's V.ision E.lsewhere
Fly Safe everyone o7
Uhhh, you spent time building something, without taking a look at what CCP were going to do? CREST has been out for a fair time now. ESI was announced 2 months ago.
And it's CCP's fault?
Woo! CSM XI!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
Jone Sad
The Scope Gallente Federation
7
|
Posted - 2017.01.14 00:23:54 -
[23] - Quote
Steve Ronuken wrote:Whitney Aubaris wrote:I am cool with the idea of the new codes although it would be nice if they kept the old simple API keys for the newbs like me who can only just scrape by with the little code we know.
I just spent a week building my self a vary good looking fully detailed site that runs off just API grabs and now I hear they are going to change how we get the info. Makes me wish I didn't wast my time with any of it.
C.orporate C.ontrol P.ointing
E.veryone's V.ision E.lsewhere
Fly Safe everyone o7 Uhhh, you spent time building something, without taking a look at what CCP were going to do? CREST has been out for a fair time now. ESI was announced 2 months ago. And it's CCP's fault?
ESI same *hit as CREST... Something is doing but will it has the working end? Nobody knows... LOL
|
CowRocket Void
Angelus.Mortis Fidelas Constans
31
|
Posted - 2017.01.14 02:00:16 -
[24] - Quote
The "mostly code illiterate" folks (me) who do "stuff"(also me) with the current XML api got a big kick in the junk with ESI.
bleeding shadow darkness > did i just saw a red procurer? :P
|
Whitney Aubaris
AWOLGamers
2
|
Posted - 2017.01.14 20:53:32 -
[25] - Quote
Steve Ronuken wrote:Whitney Aubaris wrote:I am cool with the idea of the new codes although it would be nice if they kept the old simple API keys for the newbs like me who can only just scrape by with the little code we know.
I just spent a week building my self a vary good looking fully detailed site that runs off just API grabs and now I hear they are going to change how we get the info. Makes me wish I didn't wast my time with any of it.
C.orporate C.ontrol P.ointing
E.veryone's V.ision E.lsewhere
Fly Safe everyone o7 Uhhh, you spent time building something, without taking a look at what CCP were going to do? CREST has been out for a fair time now. ESI was announced 2 months ago. And it's CCP's fault?
CCP's fault? Yes. Now on the other hand If they keep the API system running and keep it updated then I have no problem with new systems coming out and CCP would not need to take any blame. Just keep API's active and running until the end of EVE so newbs like me can make stuff happen.
Being a CSM I would hope you had the guts to bring it up in a meeting and even push hard for it as the majority of the EVE players have little to no knowledge in code.
Another thing to do seeing that you guys want to get rid of API so badly would be to provide tutorials (in full detail) on how the new codes are to be setup/built so newbs like my self can follow along and learn a few things.
Final note and anyone here that plays some of the newer games that have been released in the past 4ish years would likely agree with me. Most of the games being released the past few years are incomplete games full of bugs and interest killers. Now look at CCP they are starting to look just like everyone else. Adding new things to the game and to the coding groups that are incomplete and broken. The players are not your beta testers unless its on the beta server only. When the project is complete then you can release your final product. If you have to push the release date back so be it. Don't be an artist that tries to sale his/her art before your done with it. |
Jone Sad
The Scope Gallente Federation
7
|
Posted - 2017.01.15 14:56:13 -
[26] - Quote
Whitney Aubaris wrote:Steve Ronuken wrote:Whitney Aubaris wrote:I am cool with the idea of the new codes although it would be nice if they kept the old simple API keys for the newbs like me who can only just scrape by with the little code we know.
I just spent a week building my self a vary good looking fully detailed site that runs off just API grabs and now I hear they are going to change how we get the info. Makes me wish I didn't wast my time with any of it.
C.orporate C.ontrol P.ointing
E.veryone's V.ision E.lsewhere
Fly Safe everyone o7 Uhhh, you spent time building something, without taking a look at what CCP were going to do? CREST has been out for a fair time now. ESI was announced 2 months ago. And it's CCP's fault? CCP's fault? Yes. Now on the other hand If they keep the API system running and keep it updated then I have no problem with new systems coming out and CCP would not need to take any blame. Just keep API's active and running until the end of EVE so newbs like me can make stuff happen. Being a CSM I would hope you had the guts to bring it up in a meeting and even push hard for it as the majority of the EVE players have little to no knowledge in code. Another thing to do seeing that you guys want to get rid of API so badly would be to provide tutorials (in full detail) on how the new codes are to be setup/built so newbs like my self can follow along and learn a few things. Final note and anyone here that plays some of the newer games that have been released in the past 4ish years would likely agree with me. Most of the games being released the past few years are incomplete games full of bugs and interest killers. Now look at CCP they are starting to look just like everyone else. Adding new things to the game and to the coding groups that are incomplete and broken. The players are not your beta testers unless its on the beta server only. When the project is complete then you can release your final product. If you have to push the release date back so be it. Don't be an artist that tries to sale his/her art before your done with it. PS: Your not the only one out there that needs to do some coding Fuzzworks. There shouldn't be a monopoly on the coding market for anyone making EVE apps, sites, etc.
CSM is useless position in CCP. CCP doesn't listen it at all. ;) CSM is some kind of "throughts collector". When he\she collects thoughts he announce them to CCP. And that's all.
I aggree with you man. As I said earlier they doing api such way that only developer (in rl) can handle their API (FOR FREE, you cannot ask real money for it!). And in the end - their api will die. It's dieing now...
We need ready api with full manual or just close all uncomplete branches - what for are they? They confuse anyone who tries to create something... They only shows that ccp pay someone money to create new some api and then fire it.
I see it in this way. Was a person group that creates XML API (hello old school! you are great). Then came new group that creates CREST... But wait! Lest create SSO! Another group of devs came? LOL And now new (afaik) came to develop that ESI....
So CCP spent their money ... For what!? LOL
Your problem that you hiring wrong guys, and I think not for "free"...
PS: When you work developer a lot, you know how it goes in another companies.
PS2: CSM is a regular person, don't rely on him\her, he cannot affect at all, he\she can only suggest. And mostly CCP refuse suggestion. I talked to CSM guys a lot, it's only fiction that you can change something, it's same like you post your thought on this forum. |
Farmer Johnson's Daughter
United Federation Of Space Dealers
16
|
Posted - 2017.01.15 18:24:05 -
[27] - Quote
One of the things that drives me nuts is this sso crap. Everyone points to the docs with endpoints and says "its all there" , you know...except and actual working friggen example for php.
A full, complete example to check any authenticated endpoint with this sso garbage. Laravel support?. Anything. One simple example. Show me the light :)
Phealng is great but how long will crest be around? 16months? |
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
6377
|
Posted - 2017.01.15 18:24:54 -
[28] - Quote
Hate to tell you this, but your suppositions on _why_ the new APIs happens is wrong. Which is fairly obvious to anyone who interacts with the wider Eve third party community. Where the developers involved are actually pretty responsive.
Will there be a full manual for the API? I seriously doubt it. There's documentation now, with ESI. That's a bonus from the way they're doing it. Swagger pretty much means that there is some documentation.
The XML api has _severe_ limitations, mostly stemming from how it interacts with Eve. (It talks directly to the database. Which doesn't contain full state)
Crest was primarily created for the Dust integration, allowing for some limited interaction with game state.
CREST has some other limits, and wasn't suitable for the mobile app, which is the main driver for ESI. There are devs who have some and gone in that time, but that's just people moving from companies. It happens. Not people being fired.
As for why some things are taking longer to port than you might expect: Eve's complicated. And this is trying to graft functionality which was never designed into it. Assumptions which made perfect sense when they were made, no longer do, and cause problems. One of the big problems is sessions. Eve was designed for a single session per user. The API (other than XML, but that can't actually do anything which would need one) would need a second. Which breaks things. so fun for everyone involved
Woo! CSM XI!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
Steve Ronuken
Fuzzwork Enterprises Vote Steve Ronuken for CSM
6377
|
Posted - 2017.01.15 18:37:24 -
[29] - Quote
Farmer Johnson's Daughter wrote:One of the things that drives me nuts is this sso crap. Everyone points to the docs with endpoints and says "its all there" , you know...except and actual working friggen example for php.
A full, complete example to check any authenticated endpoint with this sso garbage. Laravel support?. Anything. One simple example. Show me the light :)
Phealng is great but how long will crest be around? 16months?
https://github.com/fuzzysteve/fleetTracker
is a crest example.
(rename secret.php.example to secret.php, and give it the details from your app on the dev site)
ESI is pretty much the same as crest from an auth perspective. You hand the auth header in the same way.
Auth is OAUTH2. An industry standard.
https://esi.tech.ccp.is/latest/ has all the endpoints, and has the option to do lookups with it, for example.
Woo! CSM XI!
Fuzzwork Enterprises
Twitter: @fuzzysteve on Twitter
|
Farmer Johnson's Daughter
United Federation Of Space Dealers
16
|
Posted - 2017.01.15 18:48:23 -
[30] - Quote
Steve Ronuken wrote:https://github.com/fuzzysteve/fleetTracker is a crest example. (rename secret.php.example to secret.php, and give it the details from your app on the dev site) ESI is pretty much the same as crest from an auth perspective. You hand the auth header in the same way. Auth is OAUTH2. An industry standard. https://esi.tech.ccp.is/latest/ has all the endpoints, and has the option to do lookups with it, for example.
Thanks steve but this is what im talking about, you showed me a crest example, not a esi example, then referenced the esi latest again which is useless as it doesn't show me how to actually use it with php from my local testing environment.
Example: how do i, from scratch, simply get the wallet of my own character.
for example, i have this so far, and that's it, where the hell do i start lol. I know its a lot to ask but so frustrating without a clear example for less experienced devs. I can work laravel pretty well but cant figure out this sso crap to save my life
"$authorization = "Authorization: Bearer how the hell do i get this, from where, what process"; $ch = curl_init("https://esi.tech.ccp.is/latest/characters/{character_id}/wallets//?datasource=tranquility"); curl_setopt($ch, CURLOPT_HTTPHEADER, array( $authorization, )); // curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST"); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); // curl_setopt($ch, CURLOPT_POSTFIELDS,$authorization); // curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1); // curl_setopt($ch, CURLOPT_POST,false); $result = curl_exec($ch); //dd($result); curl_close($ch); return $result;"
hopefully someone will whip up a CLEAR laravel package :) |
|
|
|
|
Pages: [1] 2 :: one page |
First page | Previous page | Next page | Last page |