correction, even here we can just directly end the output files <div class="gmail_quote">On Fri, Mar 20, 2009 at 8:20 PM, Vamsi Krishna Davuluri <<a href="mailto:vamsi.davuluri@gmail.com">vamsi.davuluri@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> 1) Implement print-to-pdf, transfer the file to the server in a normal tcp/ip protocol, and never interact with CUPS client side, the transferred file with open in a default viewer or a one after the other in a queue (FIFO) format. which can then be saved/printed/ deleted accordingly. The logic for printing to pdf with with cairo is fairly simple ( I have the code ready) . Now what is left is sugarizing them, The journal will be the printing hub, i will write a small activity that takes care of printing to pdf/ or sending a locally temporary pdf to server. </blockquote></div>