Open flowersinthesand opened 9 years ago
+1 on the idea. I think for intra-net application some customers could be attrackted. Now what do you have in mind client side to interact with the server side?
I'd like to create lightweight platform for client side (maybe ClientHttpExchange
and ClientWebSocket
) like with server side for Vibe Java Client. I think, however, unlike with server, because client is generally used as standalone (easy to replace with other one), it's unlikely to be as attractive as server side. And AHC you wrote has already similar concept. Right? If you are interested, I'll open a new issue with more research.
TCP protocol also can be supported along with HTTP and WebSocket e.g.
ServerTcpSocket
likeServerHttpExchange
. A network application written using this feature probably will be able to run seamlessly on Netty, Grizzly, Vert.x, MINA and so on. The following usages are expected.And the following questions should be discussed.
ServerHttpExchange
doesn't support protocol upgrade, it's not possible to implement WebSocket protocol but it's possible to implement Vibe protocol. In most cases, when some feature is not supported, it's due to high-level application framework not supporting it. In this case, platforms to bridge are generally in low-level.