While I grasp the essential concept behind ICEPush - where the client subscribes, the server notifies subscribers of new data, and the client requests the payload through ajax - there is a noticeable performance issue in certain scenarios.
Imagine a scenario where a page is monitoring changes to multiple items. Let's say I subscribe to an ICEPush event on the server named "ItemChange." This event triggers whenever a process on the server alters an "Item" entity. Now, if a user is tracking items with IDs 2 and 3, and an event occurs that changes item 5 on the server, the server will notify an "ItemChange" event. Consequently, the client would request a payload that is irrelevant since it is not tracking item 5. This situation leads to unnecessary server calls.
I have been searching for a solution to this dilemma but haven't found one yet. If there was a way to include a parameter with the notification, I could simply pass along the IDs of the changed items. Then, the client would know whether it needs to request the payload or not. Unfortunately, it seems like there is no straightforward method to achieve this. Any suggestions would be greatly appreciated. Thank you.