是一个读取端口，一个端口用于为套接字应用程序写一个好主意吗？

Question

I am wondering if it is a good idea to have 2 separate ports one for read, one for write ? Can I expect better performance ?

NOTE: Server is Centos, Client is flash, message format in communication is JSON.

Answer 1

There's no significant performance advantage, and it can require much more code to handle two sockets than one, particularly on the server side.

You'd also still have to open both sockets from the client side, as most systems wouldn't permit the server to open a connection back to the client.

Answer 2

AFAIK, TCP is optimised assuming you will send a request and get a response on the same socket, however the difference is likely to be trivial.

Often the simplest solution is also the fastest.

What is the problem you are trying to solve?

Answer 3

Best to have it in TCP with a single port, also depending if you are using NIO or not,

Just in case you want to have 2 ports & Unless its not a TCP (eg UDP)

If you are in Cent OS 32 bit, ensure that your kernel to use up more ports that it should.

This is to prevent port starvation & would quickly cripple your server.

Do the math, if you need to support 100 users, 100 x 2 = 200 open ports.

but in most cases, its only (65534 - 1024) ports available, so, if you could afford it, then its cool.

Also remember that most ISP's would block certain ports, so keep the right ports open for read / write.

regards