Hello to all!
There is one thing I (and I guess other developers) B) want to know:
Why 10 000 dpConnect wont affect on event manager as 10 000 _dp_fct config?
How _dp_fct config works? Is it differ from dpConnect?
dpConnect and _dp_fct comparsion
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: dpConnect and _dp_fct comparsion
A dpConnect() is made by a manager, e.g. CTRL or UI.
The Event Manager has to keep some information which managers have made connects to send the hotlink messages if a dp-element + config + attributes was changed which was used at the dpConnect().
The _dp_fct config is kept in memory of the Event Manager during runtime, resulting in an increased memory usage.
In the Event Manager a _dp_fct (not a stastical dp function) is similar to a dpConnect. If one of the parameters changes the function is called and the result is written to the dp element where the dp function is configured. There is no need to send a message to a manager.
Which of these options is more useful in a given environment and use case depends on the use case.
Best Regards
Leopold Knipp
Senior Support Specialist
The Event Manager has to keep some information which managers have made connects to send the hotlink messages if a dp-element + config + attributes was changed which was used at the dpConnect().
The _dp_fct config is kept in memory of the Event Manager during runtime, resulting in an increased memory usage.
In the Event Manager a _dp_fct (not a stastical dp function) is similar to a dpConnect. If one of the parameters changes the function is called and the result is written to the dp element where the dp function is configured. There is no need to send a message to a manager.
Which of these options is more useful in a given environment and use case depends on the use case.
Best Regards
Leopold Knipp
Senior Support Specialist