Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unfortunately I don't know any books about netty, but the online documentation together with JavaDocs and examples are pretty good. Here is a handful of examples:</p> <ul> <li><p>if you want to serve thousands of concurrent users/connections, non-blocking I/O is your only choice. Java (and OS) won't handle thousands of threads effectively, needed for blocking I/O. netty can, without creating that many threads.</p></li> <li><p>netty is as good as underlying protocol (TCP/IP or UDP). You cannot work around network latency. E.g. sending a packet from USA to Europe will take around 150 ms.</p></li> <li><p>if timing is so important, you might need to synchronize the clocks somehow or use central time source. Check out <a href="/questions/tagged/ntp" class="post-tag" title="show questions tagged 'ntp'" rel="tag">ntp</a></p></li> <li><p>you must decide how your protocol will interact with the server:</p> <ul> <li><p>short request/response connections, established every time users wants to upload question or get new one - think <a href="/questions/tagged/http" class="post-tag" title="show questions tagged 'http'" rel="tag">http</a>. This will be very slow, but quite reliable (you don't have to worry about long-lasting connections being interrupted</p></li> <li><p>establishing one connection per user, lasting throughout the whole quiz. This will minimize latencies, but you must handle broken connections and reconnects manually.</p></li> <li><p>Hybrid approach - choose <a href="/questions/tagged/http" class="post-tag" title="show questions tagged 'http'" rel="tag">http</a> protocol with <code>Keep-alive</code> option</p></li> </ul></li> <li><p>in netty, avoid copying of byte arrays (<code>ChannelBuffer</code>/<code>ByteBuf</code> is pretty good at that) and creating too much garbage</p></li> <li><p>avoid blocking I/O operations in netty worker threads. Monitor how many worker threads are utilized, avoid queueing of netty events.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POApplication design using Netty
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTomasz Nurkiewicz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POApplication design using Netty
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks Tomasz, that's given me something to go on.
      singulars
      1. PO
      1. USByte Foundry
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload