Removed export.py in examples; moved export2.py to export.py; updated README.md in same directory.

Author: Frederick Ross

examples/export/README.md

@@ -29,28 +29,5 @@ the most friendly/intuitive format.
 
 ## Notes
 
-* 	The "time chunking" algorithm tries to put as many events, up to the 
-	limit specified in a "bucket". We start out by breaking the index into buckets 
-	of 86400 seconds, or one day. If the number of events in this bucket is more 
-	than our limit, we split the day into 24 buckets of one hour each. If any of the 
-	hour buckets contain more events than our limit, the hour is split into 60 
-	buckets of one minute each. If any of the minute buckets contain more events 
-	than our limit, the minute is split into 60 buckets of one second each. A second
-	bucket is the smallest granular size.
-	
-	The code has a downsample map:
-	
-	 { 86400 : 3600, 3600 : 60, 60 : 1 }
-	
-	This maps the current "bucket length in seconds" to "next bucket length in 
-	seconds" if the current bucket contains more events than our limit.
-	
-	As such, it is important that the initial starttime begins on a day boundary 
-	(i.e. 12:00:00 AM).
-
-*	The goal of export.py is NOT to optimize the number of requests to splunk, 
-	rather to optimize the size of the return request from splunk so that in the 
-	cases of very large indices, robustness and restart are paramount.
-
 * 	When using csv or json output formats, sideband messages are not included. If 
 	you wish to capture sideband messages, the xml format should be used.