You should make an HTML language
Will there be Net Neutrality?
I've finally done it.
I fixed most of the problems with SmileNet and have achieved reliable formatted messaging between the PC side and the 3ds Side, and also have more insight as to how I need to code the SmileNet platform on the PC side to get properly compliant responses.
It's looking like SmileNet could be good for games that are turn based as well as games or applications such as chat applications.
SmileNet is also looking like it would be good for file transfer from PC to 3ds though how reliably I don't know yet, but we can definitely set something up.
Further interpretation on the SmileBasic side of your packets is required for SmileNet to be of any use.
I still need to modify some flags and such, for the Base SmileNet program to be fully usable but it's looking more and more like real time online multiplayer networking is achievable.
I don't know if there will be any lag, but it should still be quick despite small lag spikes, I have not tested this with larger data streaming but there is no reason why it won't or can't work.
Again, I've gotten rid of all the soft locks and bugs now and it's possible to send your choice data from SmileBasic over SmileNet.
Here's how it will most likely work.
Step 1: You will fill your send buffer with data, and then turn the variable in the Array which will be something like index 257, to a value of 32 to indicate that the send buffer is ready for reading.
Step 2: After the read is completed, you will in your loop somewhere be waiting for the SmileNet process to poke a ram value inside Smilebasic (probably the array index 269) and have that set to another value.
Step 3: Once that's set to another value, you the programmer will know it's safe to change the ram value 257 to an off state (Causing the SmileNet process to read it as "no data on send buffer")
Step 4: Once you know SmileNet is not getting any data from YOUR send Buffer on the PC side, it is safe to go ahead, and change data in the Send Buffer once more, then set the SendBuffer flag back on so SmileNet once again sends your send buffer out over the network.
Step 5: One more thing, SmileNet is always recieving data from the PC side, so it can be as real-time as possible. You, the SmileBasic programmer will have to make sure the data coming into your recieve buffer is also handled.
Since it's as real time as it can be, you'll have to prioritize data coming in ASAP, before you deal with sending data back out.
So in summary: Recieving data is fast.
Sending data back out is slightly slower but no less reliable.
Lastly, You the SmileBasic programmer will also have to ensure that you are formatting your outgoing and incoming data packets in a way that once they reach another 3DS, the program on that 3DS will know what to do with them.
So you'll still have to set up your own kind of messaging format within SmileNet, and find yourself dealing with the raw data yourself. But more or less, The process is automatic.
You fill the send buffer, set a flag, and POOF POOF data goes OUT.
You check the recieve buffer, AND POOF, data that came in is right there ready for you to work with in your program.
The only hassle is that sometimes SmileNet can hang or take a while to accept a connection from the PC side.
Lastly, I still have to set up a proper server, and a non blocking TCP/IP system in C# that allows multiple communications between SmileNet Clients.
A great example of how to format your send buffer would be to set it up so that the first 4-5 bytes represent a client ID, all 3ds will recieve all data for all clients.
The 3ds should ignore data that isn't for itself and should know it's own Client ID.
The 3ds should format outgoing messages, either for all clients, or for only some clients.
The next few bytes of your message should include details about what type of message it is.
Message typing is up to you. Entirely. You could choose to always put the same type of data in your messages or you could choose to put different data following an identifier token for the data type.
IE MAPDATA VS TRADE_DATA. or whatever. You'd have to convert those chars to their corresponding byte values first, send them over the network and convert them back on the other 3ds.
HUZZAH after nearly 8 months of development (with alot of long breaks and tons of headaches)
SMILENET almost lives!!
I look foreward to any questions, and to giving help and advice on how to develop applications that are internet-enabled with SmileBasic from here on out.
Expect a release soon, but not too soon.
