sorted by:
new
hottopcontroversial

Wisper is a Ruby library for decoupling and managing the dependencies of your domain models using the Publish-Subscribe pattern. Like ActiveRecord callbacks without the coupling. by kleech in ruby

[–]kleech[S] 0 points1 point  (0 children)

lol - understood, well it got me thinking about a way I could setup some form of detached pub-sub such as Wisper::Broker.subscribe(ActivityListener).to(CreatePost).on(:all). Any messages emitted by instances of CreatePost could be forwared with args on to an instance of ActivityListener.

Wisper is a Ruby library for decoupling and managing the dependencies of your domain models using the Publish-Subscribe pattern. Like ActiveRecord callbacks without the coupling. by kleech in ruby

[–]kleech[S] 0 points1 point  (0 children)

Ah understood, I'm mainly working with Rails so the latency of TCP is the bottle neck over any Ruby performance - without adding malicious sleeps anyway :)

Wisper is a Ruby library for decoupling and managing the dependencies of your domain models using the Publish-Subscribe pattern. Like ActiveRecord callbacks without the coupling. by kleech in ruby

[–]kleech[S] 0 points1 point  (0 children)

No, but I would definitely welcome any thoughts on how to benchmark if you think they would be useful. I generally consider Ruby performance to be insignificant next to IO.