Context Navigation

Changes between Initial Version and Version 1 of Ticket #5328, comment 24

initial	v1
4	4	And some more evidence: http://wordpress.org/support/topic/admin-ajaxphp-being-called-from-admin-pages-causing-db-connection-issues
5	5
6		On my site (for example) I often have upward of 200 concurrent logged-in users, I don't want heartbeat coming anywhere near my frontend. In fact, admin-ajax is already pretty inefficient. So much so, that for an ajax heavy theme (which every BP theme would be if heartbeat is integrated) you are much better off routing theme-side ajax calls through a separate custom frontend AJAX handler which ~~uses almost 50% less memory~~.
	6	On my site (for example) I often have upward of 200 concurrent logged-in users, I don't want heartbeat coming anywhere near my frontend. In fact, admin-ajax is already pretty inefficient. So much so, that for an ajax heavy theme (which every BP theme would be if heartbeat is integrated) you are much better off routing theme-side ajax calls through a separate custom frontend AJAX handler which is far less resource intensive.
7	7
8	8	The heartbeat API is great for the WordPress backend, but let's face it, WP is not by nature a membership site platform. Heartbeat was designed to allow a team of authors to avoid stepping on each other's toes.