http://www.PaisaLive.com/register.asp?2024379-5217218
On 2/25/11, John Beynon <[email protected]> wrote: > We're faced with having to generate PDFs on Heroku - we've been looking at > wickedPDF and taken a look at the new heroku addon DocRaptor. > > I'm curious with DocRaptor - with their Ruby example > at http://docraptor.com/examples (Rails tab) - where does Heroku's > involvement end - is a dyno 'busy' throughout? For example a pdf link is > clicked which is then passed over to DocRaptor via a post (consuming a Dyno) > and then waits for the response to be generated and then streamed back to > the same dyno which then sends the data to the client browser - so a dyno is > essentially busy throughout this process from when the link is clicked, > waiting for the response and then returning the data to the client browser? > > What we're looking at is being able to generate PDFs without consuming > precious dynos - I've seen mentions of using DJ for background processing > but we want the user to able to click a button which kicks of the PDF > generation and shows them 'Generating' and then when the doc is ready send > it to the client but I'm thinking that may need writing to tmp to then serve > back? > > Any one done anything similar? > > Any ideas? > > John. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
