title: Tablesorter server side pagination - requirements for different Ajax options
body: <p>I intend to use tablesorter's Ajax server side pagination functionality but have a couple of questions about how it works. The documentation for 2.10.0 says:</p>
  
  <blockquote>
    <p>The ajaxProcessing function was updated to only require a total number of rows to be returned, also instead of returning an array of table rows, you can build the table yourself and just return the jQuery object containing those rows</p>
  </blockquote>
  
  <p>If you build the table yourself (which I assume means the full HTML for the next set of rows, including cell values), does the ajaxUrl still need to return JSON information for the set of rows or should it return the HTML for the table? If the JSON information is to be returned, how is the table input into the jQuery?</p>
  
  <p>The ajaxProcessing can return just the total rows and $rows as an object or array, or also the headers: what determines which is the best choice of these options? How is the $rows object created? In general how should the code be changed to effect these different options?</p>
  
  <p>Sorry if I'm a little slow on this and thanks for any pointers.</p>
  
  <p>Regards,</p>
  
  <p>lindon</p>
  
  <hr>
  
  <p>Continuing my question here with more detail on one thing I'm confused about:</p>
  
  <p>My ajaxUrl will get the next set of rows as HTML and the normal syntax for pagination (i.e., without table sorter) is:</p>
  
  <pre><code>databasequery.php?offset=0&amp;numrows=25
  </code></pre>
  
  <p>Offset and numrows are variables that are defined as part of the php call. It's not clear to me how to use this together with <code>size={size}&amp;page={page}</code> in order for this to work properly with table sorter.</p>
  
  <p>Appreciate any tips. Thanks,</p>