XML-RPC memory leak question..

[eluser]TheFuzzy0ne[/eluser]
Exactly so. Setting a hard limit on the results just makes your solution scalable, and it won't break if there too many results. You just need to bear in mind when setting a hard limit, that your data is variable, so you don't want a string that's longer than most breaking your application. For me, with my memory usage capped at 128MB, the application maxed out the memory limit on the 727th iteration of the main loop, so I would suggest going with something like 250 results per page, or at a push, 500 (if you're sure that'll work), and maybe raise the memory limit to 256M to be on the safe side, if you are able to do that. If you are on a shared host, you might want to let them know as they might not want you to.