svn commit: r1373914 - /incubator/kafka/site/design.html

[ne...@apache.org]

Author: nehanarkhede
Date: Thu Aug 16 16:45:14 2012
New Revision: 1373914

URL: http://svn.apache.org/viewvc?rev=1373914&view=rev
Log:
Fixed producer config name from buffer.time to queue.time

Modified:
    incubator/kafka/site/design.html

Modified: incubator/kafka/site/design.html
URL: http://svn.apache.org/viewvc/incubator/kafka/site/design.html?rev=1373914&r1=1373913&r2=1373914&view=diff
==============================================================================
--- incubator/kafka/site/design.html (original)
+++ incubator/kafka/site/design.html Thu Aug 16 16:45:14 2012
@@ -295,7 +295,7 @@ The goal is to expose all the producer f
 The new producer -
 <ul>
 <li>can handle queueing/buffering of multiple producer requests and asynchronous dispatch of the batched data - 	
-<p><code>kafka.producer.Producer</code> provides the ability to batch multiple produce requests (<code>producer.type=async</code>), before serializing and dispatching them to the appropriate kafka broker partition. The size of the batch can be controlled by a few config parameters. As events enter a queue, they are buffered in a blocking queue, until either <code>buffer.time</code> or <code>batch.size</code> is reached. A background thread (<code>kafka.producer.async.ProducerSendThread</code>) dequeues the batch of data and lets the <code>kafka.producer.EventHandler</code> serialize and send the data to the appropriate kafka broker partition. A custom event handler can be plugged in through the <code>event.handler</code> config parameter. At various stages of this producer queue pipeline, it is helpful to be able to inject callbacks, either for plugging in custom logging/tracing code or custom monitoring logic. This is possible by implementing the <code>kafka.producer.async.
 CallbackHandler</code> interface and setting <code>callback.handler</code> config parameter to that class.
+<p><code>kafka.producer.Producer</code> provides the ability to batch multiple produce requests (<code>producer.type=async</code>), before serializing and dispatching them to the appropriate kafka broker partition. The size of the batch can be controlled by a few config parameters. As events enter a queue, they are buffered in a queue, until either <code>queue.time</code> or <code>batch.size</code> is reached. A background thread (<code>kafka.producer.async.ProducerSendThread</code>) dequeues the batch of data and lets the <code>kafka.producer.EventHandler</code> serialize and send the data to the appropriate kafka broker partition. A custom event handler can be plugged in through the <code>event.handler</code> config parameter. At various stages of this producer queue pipeline, it is helpful to be able to inject callbacks, either for plugging in custom logging/tracing code or custom monitoring logic. This is possible by implementing the <code>kafka.producer.async.CallbackHa
 ndler</code> interface and setting <code>callback.handler</code> config parameter to that class.
 </p>
 </li>
 <li>handles the serialization of data through a user-specified <code>Encoder</code> -