mossbauerlab / tinytcpserver Goto Github PK

I wrote complicated scripts depending on other assemblies and got compilation errors (possibly due to compiler was unable to load referenced assemblies), so we should properly adjust compiler (via one more parameter to FlexlibleTcpServer).

Now TinyTcpServer supports only net40, we should support multiple platforms:

net45 (add additional) async Interface

netstandard2.0

netcoreapp2.0+

It is necessary to read server configuration from file, at present GUI uses default paramters

Server must be able to run on CLR or Mono

We shoul be able to start, stop or restart server from console, send and receive strings and files, e.t.c

Surely Start and Restart method must be overloaded with function without parameters for starting and restarting server on the same IP and Port.

We have to make GUI more convenient to use:

• display and edit config options (grid like control) with possibility to export
• logging more cases 4 FlexibleTcpServer (display compiler options)
• remember directories path

I think parallel to NetworkClient class that works with pure sockets we should add option to run server with TcpClient, and this would be the way to TinyTcpClient project.

API must contains following functions:

1. Start on pair IP, port. If not defined will be used last values or default

2. Stop server

3. Restart server

4. Add or remove filter (by tcp port, by ip address)

5. Add or remove handlers on Receive e.t.c

6. Send data to defined client (ip+tcp port)

The following task should be included in release

#2
#3
#4
#5
#6

However, I was not able to solve all the problems with multiclient parallel working without any protocol on raw data. Maybe it is impossible to do it without some tricks: protocls, resending e.t.c. Hoever we should think if we could speed up our server (v.1.2) and we shoul measure it.

Now when server is started it holds console, but it is better to manipulate it from shell script with return control after one command.

We should create a simple gui app to monitor clients and send any data or file to any client.

There is a idea to make server awailable to work with any protocols, over TinyTcpServer itself (as transport layer). Possibly script engine will be Roslyn

Echo server

Time server

e.t.c.

For case when we are running server with script we must adjust GUI for this case