Atmosphere/atmosphere — Issue #88:  FeatureRequest: use cache-layer before filtering
Author: haed
Created: 2011-11-28 22:42:44+00:00
State: open

The cache-layer (BroadcasterCache) must handle with already transformed/filtered objects (by BroadcastFilter). In our scenario (and i think also in some other scenarios) the api is working with high-level message instances which must be finally transformed to a streamable representation (e.g. via BroadcastFilter). But it would be nice if a BroadcasterCache is able to use also this higher-level objects to have more possibilities for cache-optimizations (e.g. using an incremental long counter). Also in our scenario we are sharing identical messages in between multiple broadcaster, so in the current approach each BroadcasterCache is caching an own identical instance (if they don't use a global share instance, but this is hard to implement, because the cache is working with "low-level" objects).

The workaround in haed.notification is to transform the higher-level message instance to a string before broadcast to optimize cache sizes in the cache layer. It would be nicer if we could use BroadcastFilter for this.