[QUOTE=deloc;27609264]i want to ask compwhizii why the api design is totally fucked up and utterly worthless.[/QUOTE]
[QUOTE=Catdaemon;27609603]This. What kind of API requires you route the application through your own servers? It's pointless and insecure.[/QUOTE]
come up with a better solution to protect your API key once you distribute your application AND/OR limit access to the API via some token then
[editline]23rd January 2011[/editline]
[QUOTE=CarlBooth;27609567]you sort of answered your own question there[/QUOTE]
another excellent carlbooth post
limiting access lol
[editline]eat shit, bitch[/editline]
per-app keys in general lol
[QUOTE=compwhizii;27612032]another excellent carlbooth post[/QUOTE]
I get the impression you don't like me
[QUOTE=CarlBooth;27612322]I get the impression you don't like me[/QUOTE]
not known for liking people who have a long history of rude remarks
I love how people default to being total dicks on the internet. :sigh:
If it's necessary to keep your API key a secret, then it's not an option to distribute it in any form with the application. I would like to hear a better way to do this than what Overv is doing, because I can't think of any. If that's the only way to do it, then this API is really not worth the trouble.
[QUOTE=compwhizii;27612437]long history of rude remarks[/QUOTE]
How do you work that out?
[QUOTE=compwhizii;27612437]not known for liking people who have a long history of rude remarks[/QUOTE]
Eh? Have I missed something? I always thought Carl was one of the... ahem, better posters in WAYWO.
I haven't been able to post much because I've been debugging on my phone instead of the emulator, which runs at 1-2fps now, instead of ~45 on my HTC Aria.
75 hours to the deadline. Already got a basic level laid out, bouncing physics are working over half the time, the other half, we get a division by 0... We're definitely going to make the deadline, but we'll be cutting it very close. Probably within an hour if we spend some time really polishing it.
[QUOTE=compwhizii;27612032]come up with a better solution to protect your API key once you distribute your application AND/OR limit access to the API via some token then[/QUOTE]
github seems to manage just fine with API tokens. :colbert:
[QUOTE=Chandler;27613199]github seems to manage just fine with API tokens. :colbert:[/QUOTE]
But I need to control who can access the API.
Are all the requests going through overv's server as a proxy?
Instead why not have overv's server use its api key to request a list of single-use (or time limited) keys. Overv's server then distributes them to the clients using his app whenever they need them and can get new keys by calling your API again?
That way no-one can have their data intercepted by overv and you keep the permanent api keys private. Shoot me down in flames if this is a bad idea but I can't see any obvious flaws with it.
[QUOTE=eXeC64;27613560]Are all the requests going through overv's server as a proxy?[/QUOTE]
Yes, my script replicates the proxy, except the API key isn't needed as a parameter.
[QUOTE=eXeC64;27613560]Instead why not have overv's server use its api key to request a list of single-use (or time limited) keys. Overv's server then distributes them to the clients using his app whenever they need them and can get new keys by calling your API again?
That way no-one can have their data intercepted by overv and you keep the permanent api keys private. Shoot me down in flames if this is a bad idea but I can't see any obvious flaws with it.[/QUOTE]
That is a good idea, but makes the process more tedious.
[QUOTE=eXeC64;27613560]Are all the requests going through overv's server as a proxy?
Instead why not have overv's server use its api key to request a list of single-use (or time limited) keys. Overv's server then distributes them to the clients using his app whenever they need them and can get new keys by calling your API again?
That way no-one can have their data intercepted by overv and you keep the permanent api keys private. Shoot me down in flames if this is a bad idea but I can't see any obvious flaws with it.[/QUOTE]
That's not a bad idea.
I could also accept keys hashed together with a timestamp and some other secret that are retrieved through an external server. It would then be the application developers job to make sure keys weren't handed out without verification.
Garry: I checked out the latest version of GWEN and built it then the OpenGL renderer and finally the OpenGL test. I get this error:
[quote]Unhandled exception at 0x00428386 in OpenGLSample.exe: 0xC0000005: Access violation reading location 0x00000001.[/quote]
Now, why is ScrollControl's m_InnerPanel 0x00000001?
ScrollControl's m_InnerPanel is not 0x00000001, it is at the address 0x00000001 and that'll be because the offending ScrollControl is at 0x00000000.
[QUOTE=ZeekyHBomb;27614769]ScrollControl's m_InnerPanel is not 0x00000001, it is at the address 0x00000001 and that'll be because the offending ScrollControl is at 0x00000000.[/QUOTE]
Which probably wants to say that you have a NULL pointer somewhere.
[QUOTE=esalaka;27614971]Which probably wants to say that you have a NULL pointer somewhere.[/QUOTE]
I'm using GWEN. Garry wrote it.
Working on a QR Code Generator...
what is the point of access control in the api via keys? it's pointless for preventing abuse.
Doesn't the API have it's own sub-sub-forum for this kind of talk? Assuming that's what you're still talking about.
[QUOTE=John.Lua;27615480]I'm using GWEN. Garry wrote it.[/QUOTE]
Okay, then Garry has a null pointer somewhere.
Look for it and debug it yourself.
[QUOTE=compwhizii;27612032]
another excellent carlbooth post[/QUOTE]
compdramaii
[QUOTE=thelinx;27617513]was that really the best you could come up with[/QUOTE]
yea :( I really wracked my brain too.
I have som problem with std::string... When I call lenght() the function return a random number like 24353455. I'm doing this in a class function which is in a lib... I'm totally locked.
So I've decided to write a copy of GWEN (Similar in some aspects). So I've got my self Windower.dll, Contexter.dll and Gui.dll. In Gui.dll I am drawing the GUI. But I've hit a little problem with perspective rendering in OpenGL. The GUI does draw the rectangle but, it seems my projection matrix is off; the rectangle is draw half the size (320 x 240). I thought the Z component was messing it up but it doesn't seem to be the cause.
TL; DR: In OpenGL my rectangle is half the size, I'm using perspective (glFrustrum).
I bet I'm missing something simple.
Not using perspective?
Aren't you supposed to use glOrtho or what ever it's called for non-3D stuff?
Sorry, you need to Log In to post a reply to this thread.
