Databases
StackOverflow2013
Postsdbo
POHow to use ChunkedStream properly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to use ChunkedStream properly
    primarykey
    data
    text
    <p>Here's my use case... I have an upstream service that sends my Netty app data over the network, and that data needs to be published to multiple clients connected to Netty. The data pushed to the clients must be HTTP "Transfer-Encoding: chunked."</p> <p>I found <code>ChunkedStream</code> and though that maybe I could create a <code>PipedInputStream</code> and a <code>PipedOutputStream</code> (connected to the <code>PipedInputStream</code>) and write the <code>ChunkedStream</code> to the channel. Then when data is received from my upstream service I could write the data into the <code>PipedOutputStream</code> of the channels and it'd be sent to the clients:</p> <p><strong>In channelConnected</strong></p> <pre><code>PipedInputStream in = new PipedInputStream(); PipedOutputStream out = new PipedOutputStream(in); ctx.getChannel().write( new PersistentChunkedStream(in) ); </code></pre> <p><strong>Separate thread publishes data to a connected channels</strong></p> <pre><code>ChannelBuffer buff = ChannelBuffers.copiedBuffer("FOO",CharsetUtil.UTF_8); out.write( buff.array() ); channel.get(ChunkedWriteHandler.class).resumeTransfer(); </code></pre> <p>I had to extend <code>ChunkedStream</code> to return <code>null</code> from <code>nextChunk</code> if there are 0 bytes available (to "suspend" the write without the thread hanging), so I call <code>resumeTransfer</code> after I write to the <code>PipedOutputStream</code> of the associated channel. When I debug and step through the code, I can see <code>flush</code> of <code>ChunkedWriteHandler</code> being called, which does call:</p> <pre><code>Channels.write(ctx, writeFuture, chunk, currentEvent.getRemoteAddress()); </code></pre> <p>with the bytes I wrote into the <code>PipedOutputStream,</code> but it's never received by the client.</p> <p><strong>HTTP curl</strong></p> <pre><code>~ $ curl -vN http://localhost:8080/stream * About to connect() to localhost port 8080 (#0) * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8080 (#0) &gt; GET /stream HTTP/1.1 &gt; User-Agent: curl/7.19.7 (universal-apple-darwin10.0) libcurl/7.19.7 OpenSSL/0.9.8r zlib/1.2.3 &gt; Host: localhost:8080 &gt; Accept: */* &gt; &lt; HTTP/1.1 200 OK &lt; Transfer-Encoding: chunked &lt; ### NOTE: NO "FOO" TRANSMIT BACK ### </code></pre> <p>Any thoughts? Maybe there's a better way to accomplish this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDaniel A. White
    1. USRyan Shelley
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to use ChunkedStream properly
      1. USVinicius Carvalho
      1. VTFavorite
    1. COHere's a screenshot of just before it writes "FOO" to the channel: http://screencast.com/t/XATjUfCsre6U Note that you can see the chunk contains "70, 79, 79" = FOO
      singulars
      1. POHow to use ChunkedStream properly
      1. USRyan Shelley
    2. COIt's really strange because I can see `write0` of `NioWorker` being called and writing to the channel, but nothing on the other end. I even make sure to use "-N" of curl to prevent buffering on the client side. I've also let it run in a loop for awhile thinking something needed to be flushed, but still no dice.
      singulars
      1. POHow to use ChunkedStream properly
      1. USRyan Shelley
    3. COIt's gotta be me. I can see it in WireShark. Maybe there's a terminator I'm not passing to inform curl the chunk has been received.
      singulars
      1. POHow to use ChunkedStream properly
      1. USRyan Shelley
 

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