Comments on: On using sequences and tasks with the DrupalService http://www.dpdk.nl/opensource/on-using-sequences-and-tasks-with-the-drupalservice Opensource initiative by Dutch interactive agency dpdk. Thu, 09 Feb 2012 01:09:34 +0000 http://wordpress.org/?v=2.6 By: Rolf Vreijdenberger http://www.dpdk.nl/opensource/on-using-sequences-and-tasks-with-the-drupalservice#comment-311 Rolf Vreijdenberger Thu, 11 Nov 2010 17:26:50 +0000 http://www.dpdk.nl/opensource/?p=426#comment-311 Hey SP, the resource itself is not destroyed, only the local reference to the resource in the specific task. It's a memory cleanup thing. The DrupalProxy reference is nulled, so the Task does not point to it anymore. The drupalProxy instance itself is not touched at all. We're about to release (17th of november) the DrupalInvokeTask which will make all other tasks obsolete and will allow you to sequence all of your drupal calls with the help of only this task. a little example with some demo code for the adobe user group xl event (www.adobeusergroupxl.nl): sequence.add(new DrupalInvokeTask(drupal, "system", "connect")); sequence.add(new CallBackTask(drupal.setRemoteCallId, "data")); sequence.add(new DrupalInvokeTask(drupal, "node", "get", 66)); // add a pause for the demo! sequence.add(new CallBackTask(sequence.pause)); /* * tag the next call to node.get with an id of "picture". We are calling node.get again but with a different purpose. * the handler for all node.get calls is the same however. * the remote call id allows us to distinguish between multiple calls to the same method (we could also distinguish on the node id: nid) */ sequence.add(new CallBackTask(drupal.setRemoteCallId, "picture")); // node 122 is predefined and is a cck made node in drupal that has an extra field with a url of a picture in it. sequence.add(new DrupalInvokeTask(drupal, "node", "get", 122, new Array("nid", "type", "field_picture"))); sequence.add(new CallBackTask(sequence.pause)); // it is often not needed to tag the call, but it is easy for debugging sequence.add(new CallBackTask(drupal.setRemoteCallId, "sleep 3")); sequence.add(new CallBackTask(write, "sleep for 3 seconds (timout test)")); take care Hey SP,
the resource itself is not destroyed, only the local reference to the resource in the specific task. It’s a memory cleanup thing. The DrupalProxy reference is nulled, so the Task does not point to it anymore. The drupalProxy instance itself is not touched at all.

We’re about to release (17th of november) the DrupalInvokeTask which will make all other tasks obsolete and will allow you to sequence all of your drupal calls with the help of only this task.

a little example with some demo code for the adobe user group xl event (www.adobeusergroupxl.nl):

sequence.add(new DrupalInvokeTask(drupal, “system”, “connect”)); sequence.add(new CallBackTask(drupal.setRemoteCallId, “data”));
sequence.add(new DrupalInvokeTask(drupal, “node”, “get”, 66));
// add a pause for the demo!
sequence.add(new CallBackTask(sequence.pause));
/*
* tag the next call to node.get with an id of “picture”. We are calling node.get again but with a different purpose.
* the handler for all node.get calls is the same however.
* the remote call id allows us to distinguish between multiple calls to the same method (we could also distinguish on the node id: nid)
*/
sequence.add(new CallBackTask(drupal.setRemoteCallId, “picture”));
// node 122 is predefined and is a cck made node in drupal that has an extra field with a url of a picture in it.
sequence.add(new DrupalInvokeTask(drupal, “node”, “get”, 122, new Array(”nid”, “type”, “field_picture”)));
sequence.add(new CallBackTask(sequence.pause));
// it is often not needed to tag the call, but it is easy for debugging
sequence.add(new CallBackTask(drupal.setRemoteCallId, “sleep 3″));
sequence.add(new CallBackTask(write, “sleep for 3 seconds (timout test)”));

take care

]]> By: Speechless pumpkin http://www.dpdk.nl/opensource/on-using-sequences-and-tasks-with-the-drupalservice#comment-309 Speechless pumpkin Sat, 30 Oct 2010 22:33:52 +0000 http://www.dpdk.nl/opensource/?p=426#comment-309 Arrgh :). Now I see something. After rereading my post. DrupalService and DrupalProxy. I got them mixed up. So I assume drupalService (outdated now, i suppose) wasn't so brutal in it's destroy method, and was reusable after one task? What's your approach now when using DrupalProxy and sequencing? Because DrupalConnectTask and DrupalNodeTask still destroys the resource, so is there some other way to create such sequence with only one drupalService, or you have to create drupalService for each task? Or is there still something else I don't see... ? Arrgh :).
Now I see something. After rereading my post. DrupalService and DrupalProxy. I got them mixed up.
So I assume drupalService (outdated now, i suppose) wasn’t so brutal in it’s destroy method, and was reusable after one task?
What’s your approach now when using DrupalProxy and sequencing? Because DrupalConnectTask and DrupalNodeTask still destroys the resource, so is there some other way to create such sequence with only one drupalService, or you have to create drupalService for each task? Or is there still something else I don’t see… ?

]]> By: Speechless pumpkin http://www.dpdk.nl/opensource/on-using-sequences-and-tasks-with-the-drupalservice#comment-308 Speechless pumpkin Sat, 30 Oct 2010 22:26:09 +0000 http://www.dpdk.nl/opensource/?p=426#comment-308 Hi, very interesting stuff.. but I don't get one thing. In the code above you create one service:DrupalService and pass it as a parameter to DrupalConnectTask. When DrupalConnectTask finishes, DrupalConnectTask.destroyTaskHook is called where you destroy dataService that was passed in (by calling this.ds.destroy()) . This is from DrupalProxy destory() method description: /** * cleans up the class. * destroys all references, frees memory etc. * after a call to destroy, the instance of DrupalProxy cannot be used anymore */ (notice the last line - this instance of dataProxy cannot be used anymore). So DrupalConnect task is done and sequence continues with next task : which is first of the 100 DrupalNodeTasks. Which is passed in same drupalProxy resource (that should be already destroyed right now).. This task does its job, again destroys drupalProxy, next task kicks in, with same drupalProxy, and again and again :). Am I missing somethig here? Is DrupalProxy a unkillable vampire or what? Sorry, maybe it's too late for me , but I just can't figure this one out. Will be glad for any explanation. And yes, I'm a programmer, not a newbie, so don't go soft on me :). Happy Halloween everyone. Hi,
very interesting stuff.. but I don’t get one thing. In the code above you create one service:DrupalService and pass it as a parameter to DrupalConnectTask. When DrupalConnectTask finishes, DrupalConnectTask.destroyTaskHook is called where you destroy dataService that was passed in (by calling this.ds.destroy()) . This is from DrupalProxy destory() method description:
/**
* cleans up the class.
* destroys all references, frees memory etc.
* after a call to destroy, the instance of DrupalProxy cannot be used anymore
*/
(notice the last line - this instance of dataProxy cannot be used anymore).
So DrupalConnect task is done and sequence continues with next task : which is first of the 100 DrupalNodeTasks. Which is passed in same drupalProxy resource (that should be already destroyed right now).. This task does its job, again destroys drupalProxy, next task kicks in, with same drupalProxy, and again and again :).
Am I missing somethig here?
Is DrupalProxy a unkillable vampire or what?
Sorry, maybe it’s too late for me , but I just can’t figure this one out. Will be glad for any explanation. And yes, I’m a programmer, not a newbie, so don’t go soft on me :).
Happy Halloween everyone.

]]> By: Rolf Vreijdenberger http://www.dpdk.nl/opensource/on-using-sequences-and-tasks-with-the-drupalservice#comment-99 Rolf Vreijdenberger Mon, 14 Dec 2009 10:30:58 +0000 http://www.dpdk.nl/opensource/?p=426#comment-99 Hi Benoit, veryyy nice.. Also very nice to see that you actually used the package as envisioned by us (thanks to letting everyone be able to view your source code) and in the way we use it ourselves. Subclassing the Task class to create powerfull sequences etc. Nice to hear you could really use it and thanks for letting us know :) take care Hi Benoit,

veryyy nice.. Also very nice to see that you actually used the package as envisioned by us (thanks to letting everyone be able to view your source code) and in the way we use it ourselves. Subclassing the Task class to create powerfull sequences etc. Nice to hear you could really use it and thanks for letting us know :) take care

]]> By: Benoît de Raemy http://www.dpdk.nl/opensource/on-using-sequences-and-tasks-with-the-drupalservice#comment-95 Benoît de Raemy Wed, 02 Dec 2009 07:23:22 +0000 http://www.dpdk.nl/opensource/?p=426#comment-95 Here's my first attempt to convert my Drupal portfolio into flex : http://www.brandnewside.com Sorry, the content is in French, translation to English is on the way. But amateurish developer like me can still look at the source : comments are in English... well, sort of... Professional developer : you've been warned. Anyway, thank you again, your stuff works perfectly. Here’s my first attempt to convert my Drupal portfolio into flex :
http://www.brandnewside.com
Sorry, the content is in French, translation to English is on the way. But amateurish developer like me can still look at the source : comments are in English… well, sort of…
Professional developer : you’ve been warned.
Anyway, thank you again, your stuff works perfectly.

]]> By: Ercan Bozoglu http://www.dpdk.nl/opensource/on-using-sequences-and-tasks-with-the-drupalservice#comment-77 Ercan Bozoglu Mon, 12 Oct 2009 13:52:48 +0000 http://www.dpdk.nl/opensource/?p=426#comment-77 It is not only easy to implement, but also easy to read as code. All the tasks are manipulated in separate Callback tasks...Nice, because I don't wanna use events. Greate job It is not only easy to implement, but also easy to read as code. All the tasks are manipulated in separate Callback tasks…Nice, because I don’t wanna use events. Greate job

]]>