I am planning on making a game using my Spark Core, but am not sure the best way to go about it. Originally I was planning on making a webpage with several buttons and when clicked would send an ajax post to the spark core where it would react accordingly. However, I am worried that this method may result in delay, a situation I am trying to avoid. Do you guys have any other suggestions on how to handle this?
If you can, direct TCP/UDP sockets / communication on a local network will always be the fastest. If you’re doing a POST request and you’re not on the same network, you can send it to the API and do a spark function instead, which might save you some processing time. A POST request directly to the core might be a lot of overhead, unless that’s something Webduino can do?
what do you think the best way to do a tcp connection would be? a cgi script possibly? not too familiar with the web side of things, more familiar with the embedded side… it will be on the local network
Maybe if I explained it better it would help… I want to make a website hosted on my rpi where I can have a website with a simple left and right button. When these are clicked, I want to send some kind of AJAX message to where I can get a message like “Player 1 : Left” to the Spark Core with the least amount of latency. I’ve looked at Webduino a bit, but I’m not sure if it’s exactly what I’m looking for
@peekay123 would you mind elaborating? originally i was planning on making an ajax post through jquery where it would call my function, but im not sure if this will be fast enough… i do have a tcp client/server i wrote for my rpi to where i could send messages through that, but not sure exactly how i would do that through the website. maybe a cgi script?
In theory, if you made the AJAX request directly to the Spark Cloud (without any sort of proxy to hide the access token), it would take one less hop than if you sent that AJAX request to the server hosting the web page (the RPi?) which then proxies the request onto the Spark Cloud. The Spark Cloud still has to send a request (for Spark.variable() or Spark.function()) to your Core and back through the whole round trip again. The whole thing could take a second or two to complete.
If you ran it off a local cloud on the same network, then you’ll eliminate the dozens of hops across whatever networks it takes to get from your browser to your Core and back again. If they’re on the same subnet or same local network, a local cloud request would take much less time.
If that’s still too slow, you’ll have to communicate from your web browser directly to your Core. There are a few options that are web-browser friendly, but they may not be easy to implement:
I know the HTTP server can be done on the Core now, and there are a couple of libraries floating around that can get you up and running quick. The other three are options that are browser-friendly but don’t have any sort of library yet (that I know of), so that implementation would be entirely up to you.
If you have the resources like an extra computer or Raspberry Pi (or similar), I would try the local cloud first since it would be similar to what you’re already used to using. If that doesn’t work, try running an HTTP server directly on the Core.
@lbruder The problem you have is not on the Spark but on your web browser side to create TCP or UDP sockets.
If you can manage to spend a couple of hours on learning node.js then you could have:
Node HTTP Server on the RPi for the website (http, express, socket libraries)
This handles the user-interface
Node TCP/UDP Client on the RPi to communicate with the Spark (net, dgram libraries)
This handles communication to the spark when there is user action
TCP/UDP Server on the Spark
This handles receiving messages from the node server.
If you can keep the TCP Connection open for as long as your game lasts, then you would have almost next to nothing latency, but its a challenge running a TCP server on the spark if you have too many clients connect to it.
If you use UDP server on the spark, you will “most likely” have a consistently low latency, but there is a good chance that you will have packet loss, which you can counter by sending multiple duplicate packets (not a great practice). UDP server implementation on the spark is fairly simple and almost always without issues.
@nitred Thanks for the response! Let’s say I go the node.js HTTP server route. How would I be able to respond to a button click without loading a new page? Would this be doable via C? I have much more experience with writing an HTTP server and have already written a threaded TCP client in C, but am not sure how to do the web side of things… I want to be able to use an iphone as a game controller for each person, but want to avoid reloading the web page each time incase a button has to be pressed multiple times in one second
I think the benefit of something like voodoospark is that you’re skipping a roundtrip out to the cloud and back, which depending on your internet connection can save you a lot of latency if you’re doing something like driving a robot / game. I would recommend using the cloud connection to advertise an IP address / socket, and send messages directly that way. I think voodoospark essentially does this, it just requires you’re on the same wifi network as your device.
This feature works today-you can use publish and subscribe to get your router’s public IP address.
Then what? If you have an open port on the router that your Core/Photon is listen to, you can connect. But for some people that will not be an option due to IT or security constraints.
A better plan might be to connect from the Core/Photon to the other host since most routers are not configured to block outgoing requests, but this requires a server on the web that is listening for your device.
Do you @bko know if the local IP can be assigned? At home I can match my MAC address to an IP and then open a port (port forward) for that IP, but at work I already have a local IP assigned to an external IP with several open ports. Any suggestions how to use that.
@bko The external server is a good idea, do you know of anyone trying it? Any ideas @peekay123 ? I have seen some really easy Nodejs chat servers that work really well and fast. If the core or photon could be a TCP client connected to a chat server that could be hacked to have buttons instead of typing commands then this might be comparable to voodooSpark but internet capable not confined to a local network.
If you login to cloud9 https://c9.io the default Nodejs demo program is a chat server. If the core TCP client can receive any text from that server the problem would almost be solved. Anyone familiar with chat servers?
Oops, on second thought this will probably never work. I need a Cross Domain chat server that browsers can log into, and probably better if the core TCP client can leave the connection open so that we don’t have to do polling.