Closed (fixed)
Project:
Notifications
Version:
6.x-1.0-beta2
Component:
Documentation
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
15 Aug 2008 at 06:12 UTC
Updated:
22 Oct 2008 at 18:52 UTC
What is the purpose of the Immediate sending option at Notifications settings > General > General settings?
Without enabling this setting, when a subscription with a send interval of Immediate is created, notifications of updated nodes are sent when cron runs. How would enabling this option affect what already seems to be working?
Perhaps the help text for this option should be updated: "Do not queue notifications for immediate sending. This will produce more timely notifications for sites with a small number of users." I can't tell if that's an instruction (if so, why have the option?) or a description (which would seem to be the opposite of its purpose).
Comments
Comment #1
jose reyero commentedI think the description is accurate.
If you have a site with a few users, you can just send out notifications on page request instead of waiting for the next cron. But if you have many users, that may be too much for a page request and you will want to send them out in successive cron runs, so the load can be balanced.
Hope this helps. If you have a better wording for this feature, let us know.
Comment #2
mrtoner commentedI would change this to
"Does not queue notifications until next cron run. Instead, notifications are sent when content is created or updated. This will produce more timely notifications for sites with a small number of users."
or
"Does not queue notifications until next cron run. Instead, notifications are sent when content is created or updated. Not recommended for sites with a large number of users."
This explains what the setting does a little more clearly, IMO. As I noted in my first message, I did not understand what the help text was describing.
On a related subject, the default "Immediate" interval should be renamed "As soon as possible" -- "Immediate" does not reflect what actually happens.
Comment #3
jose reyero commentedWell, that's not really accurate, it only happens when the send interval is Inmediate.
I think I've improved it a little bit, using some pieces of your text..
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.