Re: multiple update processor chains.
Your correct, its not specifically for the update.chain. my mistake. thanks msj On Mon, Sep 9, 2013 at 3:34 AM, Alexandre Rafalovitch wrote: > Which section in the docs specifically? I thought it was multiple chains > per config file, but you had to choose your specific chain for individual > processors. > > I might be wrong though. > > Regards, >Alex. > > Personal website: http://www.outerthoughts.com/ > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > - Time is the quality of nature that keeps events from happening all at > once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) > > > On Mon, Sep 9, 2013 at 1:51 PM, mike st. john wrote: > > > Alexandre, > > > > it was setup with multiple processors and working fine. I just noticed > in > > the docs, it mentioned you could have multiple chains, it seemed to make > > sense to have the ability to chain the defined processors in order > without > > the need to merge them into a single update processor definition. > > > > thanks > > msj > > > > > > On Mon, Sep 9, 2013 at 12:28 AM, Alexandre Rafalovitch > > wrote: > > > > > Only one chain per handler. But then you can define any sequence inside > > the > > > chain, so why do you care about multiple chains? > > > > > > Regards, > > >Alex. > > > > > > Personal website: http://www.outerthoughts.com/ > > > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > > > - Time is the quality of nature that keeps events from happening all at > > > once. Lately, it doesn't seem to be working. (Anonymous - via GTD > book) > > > > > > > > > On Mon, Sep 9, 2013 at 5:43 AM, mike st. john > wrote: > > > > > > > is it possible to have multiple run by default? > > > > > > > > i've tried adding multiple update.chains for the > UpdateRequestHandler > > > but > > > > it didn't seem to work. > > > > > > > > > > > > wondering if its even possible. > > > > > > > > > > > > > > > > Thanks > > > > > > > > msj > > > > > > > > > >
Re: multiple update processor chains.
Which section in the docs specifically? I thought it was multiple chains per config file, but you had to choose your specific chain for individual processors. I might be wrong though. Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Mon, Sep 9, 2013 at 1:51 PM, mike st. john wrote: > Alexandre, > > it was setup with multiple processors and working fine. I just noticed in > the docs, it mentioned you could have multiple chains, it seemed to make > sense to have the ability to chain the defined processors in order without > the need to merge them into a single update processor definition. > > thanks > msj > > > On Mon, Sep 9, 2013 at 12:28 AM, Alexandre Rafalovitch > wrote: > > > Only one chain per handler. But then you can define any sequence inside > the > > chain, so why do you care about multiple chains? > > > > Regards, > >Alex. > > > > Personal website: http://www.outerthoughts.com/ > > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > > - Time is the quality of nature that keeps events from happening all at > > once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) > > > > > > On Mon, Sep 9, 2013 at 5:43 AM, mike st. john wrote: > > > > > is it possible to have multiple run by default? > > > > > > i've tried adding multiple update.chains for the UpdateRequestHandler > > but > > > it didn't seem to work. > > > > > > > > > wondering if its even possible. > > > > > > > > > > > > Thanks > > > > > > msj > > > > > >
Re: multiple update processor chains.
Alexandre, it was setup with multiple processors and working fine. I just noticed in the docs, it mentioned you could have multiple chains, it seemed to make sense to have the ability to chain the defined processors in order without the need to merge them into a single update processor definition. thanks msj On Mon, Sep 9, 2013 at 12:28 AM, Alexandre Rafalovitch wrote: > Only one chain per handler. But then you can define any sequence inside the > chain, so why do you care about multiple chains? > > Regards, >Alex. > > Personal website: http://www.outerthoughts.com/ > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > - Time is the quality of nature that keeps events from happening all at > once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) > > > On Mon, Sep 9, 2013 at 5:43 AM, mike st. john wrote: > > > is it possible to have multiple run by default? > > > > i've tried adding multiple update.chains for the UpdateRequestHandler > but > > it didn't seem to work. > > > > > > wondering if its even possible. > > > > > > > > Thanks > > > > msj > > >
Re: multiple update processor chains.
Only one chain per handler. But then you can define any sequence inside the chain, so why do you care about multiple chains? Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Mon, Sep 9, 2013 at 5:43 AM, mike st. john wrote: > is it possible to have multiple run by default? > > i've tried adding multiple update.chains for the UpdateRequestHandler but > it didn't seem to work. > > > wondering if its even possible. > > > > Thanks > > msj >
multiple update processor chains.
is it possible to have multiple run by default? i've tried adding multiple update.chains for the UpdateRequestHandler but it didn't seem to work. wondering if its even possible. Thanks msj
