1.2.0 Event Handler Caching, your input is required?
Since event handler caching will be instilled into the framework, the
performance is dramatic. It actually, does not make sense to be
creating event handlers for each request. So version 1.2.0 will be the
last version to support uncached handlers. The versions after 1.2.0
will have caching of handlers by default. I see no benefit of
not caching the handlers. And they can easily be recreated by using
fwreinit= url command
So. Since event handler caching actually changes A LOT in event
execution. The methods will receive the request collection object,
instead of the handler being injected with it at creation. What does
this imply? Well, mainly the 'rc' scope will become deprecated. You
can keep it, however, you must var scope it locally.
Example:
var rc = arguments.oRC (or whatever the argument is named, still
pending)
Sana
Hi Luis,
Does this will work under load balance. If this only session based then websites running on two physical webserver might have problem. just curious to know that each utitlityof ColdBox will not have problem in clustering environment.
Thanks
Luis Majano
Session is no longer in use Sana. Just application scope. So, this is cluster safe. More changes are coming, stay tuned.
Sana
Hi Luis,
thats great news, just curious to know what about message plugin, does it will use application scope or not. because i think application scope is the way for clustering environment for these kind of features.
Thanks Sana
Sana
Hi Luis,
sorry small correction in my question..
thats great news, just curious to know what about message plugin, does it will use application scope or not. because i think application scope is not the way for clustering environment for these kind of features.
Thanks Sana
Luis Majano
Sana,
The messagebox will now have a choice of storage, either session or client.
This is framework-wide. Or can be changed via the plugin API.
This gives the programmer the option of storage for the messages.