Well my secret is my little library in c++.
After 90 apps, i've done about all kind of games, so the major part is already done.
I port my piece of codes from my older apps and this is the reason i'm faster.
Maybe the sprite/text/buttons/controller manager i done in the begin is the key.
I done it in a way that maybe i didn't know that was the best way to do it.
Maybe luck.
Anyway, IMHO, i think i'm a fast coder.
@Markus -
I already asked Paul to do the test and he don't get the timeout, but he only called the main page on the site.
My server side work in this way:
- Web Page get the HTTP request
- It send the request to a socket on the server where there is a process waiting
- The server calculate the response
- The web page get the response
- The web page answer to HTTP
Some times, i have 2000 connections at the same time on my server, and this is why, until it get the "keepalive" first response, it got 10 sec to answer.
The consecutive answer are 0.45 (for the keepalive feature)
Paul did only the page calling, but the real message is crypted, and after my crypt function, is Base64, and sent to web page.
Now i can't give my crypt function to anyone, so how would test it?
Can be my Nexus 5? No, i tried from a S4 too, and is the same.
Now, if with OBJ C i got 0.45, always, why on Android i have always get the timeout?
I think there is something doesn't go in the LIBCURL (if Paul use it).
@ Van B-
The duel is online, so when the match start (simultaneously) they can see the challenger in the 2nd board. And when you delete some lines, it send a missile or lines or other things, to the challenger.
Playing together on the same device is impossible, lack of space for fingers.
Long life to Steve!
