08-25-2004, 12:01 PM
Is that something internal to your site, via choices you make during design, or a provision you agree on with the hosting service as a prioritization system?
For example, one easy flag to attach to request is the "yes" "no" to the Member data point. If there is a high demand on getting into your site, can't you, to prevent a Slashdotting sort of thing, have in place a priority rule that puts members in the que and "clips" non members in high traffic times? That would, I suspect, keep the pipe clogging concerns down to a dull roar.
A certain hit rate or flow density causes a "clipping" feature to kick in and "AK404's" "site not found" start going back to, starting bottom priority to top, those trying to access the site.
Or am I being rubish in asking a complete NOOB question about site management?
Occhi
For example, one easy flag to attach to request is the "yes" "no" to the Member data point. If there is a high demand on getting into your site, can't you, to prevent a Slashdotting sort of thing, have in place a priority rule that puts members in the que and "clips" non members in high traffic times? That would, I suspect, keep the pipe clogging concerns down to a dull roar.
A certain hit rate or flow density causes a "clipping" feature to kick in and "AK404's" "site not found" start going back to, starting bottom priority to top, those trying to access the site.
Or am I being rubish in asking a complete NOOB question about site management?
Occhi
Cry 'Havoc' and let slip the Men 'O War!
In War, the outcome is never final. --Carl von Clausewitz--
Igitur qui desiderat pacem, praeparet bellum
John 11:35 - consider why.
In Memory of Pete
In War, the outcome is never final. --Carl von Clausewitz--
Igitur qui desiderat pacem, praeparet bellum
John 11:35 - consider why.
In Memory of Pete