svn commit: r953503 - in /websites/staging/thrift/trunk/content: ./ docs/HowToNewLanguage.html

[bu...@apache.org]

Author: buildbot
Date: Mon Jun  1 23:15:55 2015
New Revision: 953503

Log:
Staging update by buildbot for thrift

Modified:
    websites/staging/thrift/trunk/content/   (props changed)
    websites/staging/thrift/trunk/content/docs/HowToNewLanguage.html

Propchange: websites/staging/thrift/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jun  1 23:15:55 2015
@@ -1 +1 @@
-1682992
+1683021

Modified: websites/staging/thrift/trunk/content/docs/HowToNewLanguage.html
==============================================================================
--- websites/staging/thrift/trunk/content/docs/HowToNewLanguage.html (original)
+++ websites/staging/thrift/trunk/content/docs/HowToNewLanguage.html Mon Jun  1 23:15:55 2015
@@ -100,9 +100,15 @@
 <h3 id="the-minimal-feature-set">The minimal feature set</h3>
 <p>The minimum required feature set should cover at least:</p>
 <ul>
-<li>Transports: Sockets, HTTP, Buffered, Framed </li>
-<li>Protocols: Binary required, JSON and Multiplex recommended</li>
-<li>Server types: SimpleServer</li>
+<li>Transports: Sockets, Buffered, Framed required, HTTP client recommended</li>
+<li>Protocols: Binary and Multiplex required, JSON recommended</li>
+<li>Server types: SimpleServer required</li>
+</ul>
+<h3 id="other-recommended-features">Other recommended features</h3>
+<ul>
+<li>Transports: HTTP server, Pipes, NamedPipes (where it makes sense)</li>
+<li>Protocols: Compact</li>
+<li>Server types: Nonblocking, Threaded and/or Threadpool server implementation</li>
 </ul>
 <h3 id="final-things">Final things</h3>
 <ul>
@@ -118,7 +124,7 @@
 </ul>
 <h2 id="remarks">Remarks</h2>
 <p>Note that the 4 implementation steps are not really a linear process, it is more kind of an iteration. Even if the code that comes out of the generator finally is compileable and does not spit out any warnings and seems to run fine, you still will run into problems as you move on with implementing library and tests. This is fully normal and expected.</p>
-<p>It is a good idea to post your work early on the mailing lists, and to create the JIRA ticket early - that's why this particular point is on top of the list. This serves not only the purpose of announcing the work you are about to do, it is also a good starting point for other people who might be just looking for exactly that stuff. You will be able not only to get valuable early feedback, but probably also be able to raise some support with implementation and/or testing.</p>
+<p>It is a good idea to post your work early on the mailing lists, and to create the JIRA ticket early - that's why this particular point is on top of the list. This serves not only the purpose of announcing the work you are about to do, it is also a good starting point for other people who might be just looking for exactly that stuff. You will be able not only to get valuable early feedback, but probably also be able to raise some support with implementation and/or testing. Having someone else looking over your code (or reviewing each other) is generally a good thing, especially with regard to the overall quality of the contribution you are about to do.</p>
 <p>Happy coding!</p>
 	</div>
 	<div class="container">