Sorry for the mistake @sam, the counter and update methods were raw… I’ve reimplemented the extension to use MessageBus. It does only an initial json request to session/current.json to obtain che current user id (the response it’s about 1.5 KB) to use with MessageBus.subscribe /notification/userId (each response with data is about 800 B in my case). I’ve not found another method: exists ? You can verify the code here.
Is the cpu load fixed ?
Is there some documentation about subscriptions that can be done in MessageBus ?
2 Likes