Ok. I recently discovered LBDBT (Low Bandwidth Drop Box Transfer Servers). Ok. Some of you might not know how it works, or what it even means. Ill split it up.
Low Bandwidth: Low Bandwidth literally means it doesn't take up much room.
DropBox: DropBox. We use it to host the server.
Transfer: We use a server which is limited to temporarily store the info, then our server picks it up and transfers it to itself, where it can be read.
So. It uses Panther to host and connect. Pro's and Con's
Pro's
Low Bandwidth
Simple
Easy to setup
Unlimited Space (2GB (more than enough) if using the free dropbox plan!)
100% customizable
Cons
Information may not be received (1 in 1,000,000!!)
Server is not ideal for interactions when being ran. (Although it's possible, bit laggy though!)
Information retrieval time is around 0.5-2 seconds.
The cons aren't really that bad, however, with more users, another 0.5-2 seconds to retrieval time is added.
I cant release yet, It was meant to be for SeptimusHeap, but I dropped out, joined (anonymous!)'s collab, and I made the server there!
Offline
Does it use raw sockets, the HTTP protocol, or some other method of communication? Can you code the server to receive a packet then send it to everyone connected?
Offline
Magnie wrote:
Does it use raw sockets, the HTTP protocol, or some other method of communication? Can you code the server to receive a packet then send it to everyone connected?
Yes. It uses the server Kabam used temporarily. Here's how it works:
The Host basically picks up the packets of info in the server which have been compiled. Those packets CANNOT be read. Then, the host transfers the information to the suitable text file on Dropbox. The normal client connects to dropbox and gets the info.
Offline
Servine wrote:
Magnie wrote:
Does it use raw sockets, the HTTP protocol, or some other method of communication? Can you code the server to receive a packet then send it to everyone connected?
Yes. It uses the server Kabam used temporarily. Here's how it works:
The Host basically picks up the packets of info in the server which have been compiled. Those packets CANNOT be read. Then, the host transfers the information to the suitable text file on Dropbox. The normal client connects to dropbox and gets the info.
So the method is HTTP? Or Dropbox's file transfer method?
Well, that method is insecure, cause the user could just look for any file and get it directly without creating a file of their own. The server needs to validate the connection.
Offline
Magnie wrote:
Servine wrote:
Magnie wrote:
Does it use raw sockets, the HTTP protocol, or some other method of communication? Can you code the server to receive a packet then send it to everyone connected?
Yes. It uses the server Kabam used temporarily. Here's how it works:
The Host basically picks up the packets of info in the server which have been compiled. Those packets CANNOT be read. Then, the host transfers the information to the suitable text file on Dropbox. The normal client connects to dropbox and gets the info.So the method is HTTP? Or Dropbox's file transfer method?
Well, that method is insecure, cause the user could just look for any file and get it directly without creating a file of their own. The server needs to validate the connection.
Yes, you see, that's the trick. (dropbox file transfer method). What happens if even if the user tries to hack, the server picks it up because it checks how the client validates it. Also, the hackers have one chance to edit info and change it, when it's in the que. They only have 2-3 secs though!
Offline
Servine wrote:
Magnie wrote:
Servine wrote:
Yes. It uses the server Kabam used temporarily. Here's how it works:
The Host basically picks up the packets of info in the server which have been compiled. Those packets CANNOT be read. Then, the host transfers the information to the suitable text file on Dropbox. The normal client connects to dropbox and gets the info.So the method is HTTP? Or Dropbox's file transfer method?
Well, that method is insecure, cause the user could just look for any file and get it directly without creating a file of their own. The server needs to validate the connection.Yes, you see, that's the trick. (dropbox file transfer method). What happens if even if the user tries to hack, the server picks it up because it checks how the client validates it. Also, the hackers have one chance to edit info and change it, when it's in the que. They only have 2-3 secs though!
Is that on the client or the server? Cause if it's on the client, people could easily just remove the blocks that stop them from doing that.
Offline
Magnie wrote:
Servine wrote:
Magnie wrote:
So the method is HTTP? Or Dropbox's file transfer method?
Well, that method is insecure, cause the user could just look for any file and get it directly without creating a file of their own. The server needs to validate the connection.Yes, you see, that's the trick. (dropbox file transfer method). What happens if even if the user tries to hack, the server picks it up because it checks how the client validates it. Also, the hackers have one chance to edit info and change it, when it's in the que. They only have 2-3 secs though!
Is that on the client or the server? Cause if it's on the client, people could easily just remove the blocks that stop them from doing that.
The host (server) checks it. It first checks to see if it has been validated, and it then checks to see if it's not ridiculousv (e.g. score is 999999999999999999).
Offline