Scope for Network Client / Server

Scope for Network Client / Server

UnKnown

1/13/2014 11:59:00 AM

Hi James / All,

What high level scope should we keep as our objectives for a Network Client / Server component or Library?

Some already set are

1. TCP for chat

2. UDP for game data

What else?

a. Performance? Should we look at C++ on .NET? Or we keep the polyglotic thoughts to a minimal?

b. Scale? - I have some info from James: Atleast 20+ Users during tests. Definitely massive when online.

c. AsyncIO? - Should we research on building a model on AsyncIO that scales rather well or keep it a task for the final model only?

d. Secure Channel / Encryption ? - Should the data transmission be secure (TCPS) or Encrypted or None? If Yes, what kind of encryption do we look at simple Blowfish to AES?

e. Hooks for notifications - I feel, the library/component should support hooks to notify the game client / server to notify asynchronously the failure to deliver or success thereof of an earlier transmission (by some ID), this can make it async or event based.

Thoughts?

Post Replay

All Replayies

We would like to keep everything .NET related so we dont have to support multiple system on different langauge structures.
We are shooting for a 5 v 5 online game at this time this came to light after yesterdays leaders meeting.
I would say let keep it simple for now until we have a need for it.
We will only worry about secure protocol when we implement a shopping system in the game, as far as chatting and game data i dont think it is need to started once again just keep it simple to get us up.
Yes even drivin 100%

Good questions thank you.

By : 1/13/2014 12:27:00 PM

Thanks James. This helps.

I will be a little slow as I have catching up to do with C# and N/w libs. But I am pretty much on it.

By : 1/15/2014 8:12:00 AM

Forum Statistics

Posts

8,45.34

Replay

8,45.34

Users

8,45.34

Forums Thread