Thread: Networking

Dear Java Programmers,

Moderators keep closing my threads because i don't have an 'open mind' so i will say exactly what i want. If u want to help me thank you but i don't want any tutorials if it doesn't explain EVERY line of code. I want to understand what every line of code does and not just what a few lines of code together do.

I want to learn about networking but it seems to be very hard to find a good full tutorial about networking so i need to learn about Packages, Sockets etc but not just about Networking in general. I have to try find a good tutorial for every part of Networking.

I want to make a program (It is NOT a game, i know: for making games u need to be very good at programming and i'm not yet). I don't know how to explain my program but it uses something u will need to use in a game too. In a game u need to handle moving players, and u don't want to do that with the client because the client can be decompiled so u need to let the server handle it. But how? Lets say u send packages with move up for example, the server will move the player up, but if the client is decompiled and u send 2 packages instead of 1 at once and compile it again u will run 2 times faster. How can i avoid that? Is it possible to make an array of every connected user and validate that u dont receive more than like 60 packages per second from every user? U can see it as like the X and Y of the player when he/she logged out and when the player logs back in ur on the same X and Y as when you left.

Also if i want to save variables for every user that change like every second should i save them every 3 seconds or something? Or every 10 seconds or every second? Because its not a big problem if the variable is a little bit old but its just important to be close to the newest one but i dont want to drop the performance because u have to store that variables for every user in a database.

Thanks in advance, (AND PLEASE don't close my thread..)
Resantic

These are the same questions you've asked before and didn't like the answers you'd received. Come back when you have some code that you need help with.

Thread closed.