[dancer-users] Delayed template processing

[Clive Eisen]

Other people have told you how to do this

In your template have callbacks to OTHER routes that return the rest of the data as and when it’s available

If you  insist use the same route and figure out from a param whether its the initial call or a callback

As far as I can tell once you have served a template that request is closed

--
Clive Eisen
GPG: 75056DD0






> On 16 Oct 2015, at 11:31, Joerg Fallmann <fall at tbi.univie.ac.at> wrote:
> 
> To circumvent this I thought about forwarding to another route
> after processing a template,
> this should actually work around the update existing output problem,
> but it seems this is not possible either
> so I really got no idea how to proceed at the moment.
> 
> --joerg
> 
> On 10/16/2015 09:05 AM, Yitzchak Scott-Thoennes wrote:
>> For this to work, you'd either need a template engine that is tightly integrated into Dancer or a streaming template engine (that would call a callback to call content as it got chunks) with the ability to loop over iterators or trigger callbacks to get more data to format.  Though I guess you could use a normal template loop over a tied array too.
>> 
>> But I don't know of such a template engine.
>> 
>> 
>> 
>> _______________________________________________
>> dancer-users mailing list
>> 
>> dancer-users at dancer.pm
>> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
> 
> _______________________________________________
> dancer-users mailing list
> dancer-users at dancer.pm
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.preshweb.co.uk/pipermail/dancer-users/attachments/20151016/e02aab28/attachment.sig>