PureEngage On-Premises

Hello,

the ConfigurationService has two methods:

confService.setBrokerInvoker(invoker);
confService.setInvoker(invoker);

- When is it technically necessary/reasonable to set an individual AsyncInvoker ?
- What must be consindered with this custom AsynchInvoker implementation? 
- What defaults are used if none custom Invoker is set? E.g. how many threads are handling asynchronies events by default? 

Thx

There are some comments.
 
1)nconfService.setBrokerInvoker(invoker);
Deprecated, has no effect. Don’t use it.
 
2) confService.setInvoker(invoker);
If set, invoker notifies user handlers with  ConfEvent object (using its separate thread). Otherwise, the ConfServer protocol invoker will be used.
If  invoker wasn’t set and user handler processing ConfEvent slowly or blocks, this may affect protocol message delivery.
My recommendation –ConfEvent processing in user handler should be fast. Otherwise -  delegate it to another user’s thread.
 
Invoker life cycle is under user control,  so, user should dispose invoker separately from ConfService. This is documented in ConfService API docs.
 

Some clarifications.
 
confService.setInvoker(invoker)                used to perform callbacks for service.beginRetrieveMultipleObjects()
 
confService.setBrokerInvoker(invoker);Implicitly grants ,  previously set by confService.setInvoker(invoker) to the ConfEvent broker. Argument of the setBrokerInvoker()  ignored. Recommendation – perform long-time operations with ConfEvent in separate user thread.
 

thx