Shashank Singh
Shashank Singh
ProtocolV3.visit() have no implementation to handle incomplete messages over non-blocking socket channel. socketChannel.read(readBuffer) directly update BEFrame 'tag' and 'state' expecting message to be in a complete state.
I was comparing blocking JDBC with this async-pgsql2 API. Design: Blocking JDBC - 1000 threads making connection with the DbServer. In this case, heap utilization was 600MB. Any suggestion for...
**DataSource.getConnection()** submit a new submission to connect with the Database Server. If any connection-exception is reported for e.g. **"password authentication failed for user -"**; there is no design to report...