[MTOS-dev] New Dispatcher On the Way
Byrne Reese
byrne at sixapart.com
Thu Mar 6 20:27:30 PST 2008
If creating a new call back will facilitate the integration of this code -
then let's start in one of our next dev cycles to integrate that callback
for you. Then we can do some additional testing and optimization.
Thoughts?
Can you submit a patch for the new callback in the core?
On 3/6/08 9:09 AM, "Hirotaka Ogawa" <hirotaka.ogawa at gmail.com> wrote:
> On Fri, Mar 7, 2008 at 1:32 AM, Reed A. Cartwright <reed at scit.us> wrote:
>> Hirotaka Ogawa wrote:
>>>
>>> I think, TheSchwartz part can be separated from this dispatcher and
>>> realized as a plugin which facilitates post_run callback.
>>
>> I see, but I'd have to call a new callback, right? One that is specific
>> to the dispatcher and not used elsewhere.
>
> Yes and No.
>
> Yes - You can serve the dispatcher with a certain callback hook. Or
> you can create a new post_takedown or post_finish callback hook into
> MT core.
>
> No - You can use take_down callback hook as well. If it should be
> used only from the dispatcher, you can check which dispatcher is
> facilitated, in the callback function. So, no new callbacks are
> required.
>
> Everything is in your hands.
>
>> I think that right now, I'll
>> be satisfied with splitting more of the code off into sub functions.
>>
>> --
>>
>>
>> *********************************************************
>> Reed A. Cartwright, PhD http://scit.us/
>> Postdoctoral Researcher http://www.dererumnatura.us/
>> Department of Genetics http://www.pandasthumb.org/
>>
>> Bioinformatics Research Center
>> North Carolina State University
>> Campus Box 7566
>> Raleigh, NC 27695-7566
>>
>> Cuiusvis hominis est errare, nullius nisi
>> insipientis in errore perserverare. --Cicero
>>
>
>
More information about the MTOS-dev
mailing list