Re: [google-appengine] Task target - specific Module
On Friday, 16 August 2013 07:21:21 UTC+12, Alexis wrote: There is currently no way to target a specific version on a non-default module using cron.yaml or dispatch.yaml. But that may work programmatically (when you enqueue the task you can also specify a target, and maybe version.module works) For anybody else who searches this up... You should be able to use version-dot-module as a target. This is working for me in cron.yaml and queue.yaml. I have not tested it in dispatch.yaml. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Task target - specific Module
I tested queue with target parameter directing to non default module. Unfortunately I tested it on production as it seemed to work. I routed certain messages and after about a day when checking stats I found out that about 1/4 of the messages were lost. Removing the target from the queue and handling the messages by the default module fixed this back to normal. I don't know whats wrong, but there is something wrong definitely... четверг, 15 августа 2013 г., 22:21:21 UTC+3 пользователь Alexis написал: It works for me. The target parameter of a cron job definition currently will go to the default version of the specified module or the specified version of the default module. If you both have a URL for the Cron job that points to an specific module and a target parameter that points differently, the URL forwarding rule via dispatch.yaml will prevail here. There is currently no way to target a specific version on a non-default module using cron.yaml or dispatch.yaml. But that may work programmatically (when you enqueue the task you can also specify a target, and maybe version.module works) -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Task target - specific Module
For some reason target works for me both in queue and cron... so it looks to be supported feature.. четверг, 15 августа 2013 г., 8:38:48 UTC+3 пользователь Vinny P написал: On Wed, Aug 14, 2013 at 9:34 AM, bFlood bfl...@spatialdatalogic.comjavascript: wrote: hello all I'm having trouble targeting specific Modules from the Task queue, I thought it would be as simple as Backends using the target param. Am I missing something obvious? Use a dispatch file. See https://developers.google.com/appengine/docs/python/modules/routing (Scroll down). You can configure routing so that all requests to a particular path are mapped to a particular module. Map your modules, then set the request address in the task to hit the module needed. - -Vinny P Technology Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Task target - specific Module
It works for me. The target parameter of a cron job definition currently will go to the default version of the specified module or the specified version of the default module. If you both have a URL for the Cron job that points to an specific module and a target parameter that points differently, the URL forwarding rule via dispatch.yaml will prevail here. There is currently no way to target a specific version on a non-default module using cron.yaml or dispatch.yaml. But that may work programmatically (when you enqueue the task you can also specify a target, and maybe version.module works) -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Task target - specific Module
On Wed, Aug 14, 2013 at 9:34 AM, bFlood bfl...@spatialdatalogic.com wrote: hello all I'm having trouble targeting specific Modules from the Task queue, I thought it would be as simple as Backends using the target param. Am I missing something obvious? Use a dispatch file. See https://developers.google.com/appengine/docs/python/modules/routing (Scroll down). You can configure routing so that all requests to a particular path are mapped to a particular module. Map your modules, then set the request address in the task to hit the module needed. - -Vinny P Technology Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
