Peter,
Well its a good idea but I would not do it at SocketFactory layer but instead at the ConnectionManager layer. The ConnectionManager was actually designed with these things in mind.
The problem I see is that this statement is rife :
final ServerSocket serverSocket = factory.createServerSocket(mPort, 5, mBindTo);
ServerSocket ( I need not tell you) is the java.net class for accepting connections. It was at that level I was thinking of an interception. Perhaps we could extend that class and have a series of subcasses for it that do diferent things. Looking at the source for it, it seems that there is even provision for custom Socket implementations.... lots of possibilities.
I think that ServerSocketFactory is the place to intercept incoming sockets and that ConnectionManager would be untouched..... please take another look Peter.
* rate limiting (ie max of 10k per second on socket) * connection limiting (max of 10 connections from one port at a time) * logging who conencts - perhaps via identd protocol * logging where connects from and at what rates etc
Agree, good features.
- Paul
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
