Postman - a JavaScript message bus

1–8 of 8 posts

Postman - a JavaScript message bus

Post by slace » Tue, Jul 19, 2011, 3:25 AM UTC

Postman is a JavaScript library & npm package which allows for cross-component messaging like traditional pub/ sub libraries but without the reqiurement on a message to be published after all the listeners are attached.

Postman - a JavaScript message bus
github.com

Re: Postman - a JavaScript message bus

Post by oinksoft » Tue, Jul 19, 2011, 5:06 AM UTC

No, it's a CoffeeScript message bus.

Re: Postman - a JavaScript message bus

Post by the-harsh-truth » Tue, Jul 19, 2011, 5:34 AM UTC

Congratulations. You managed to make a wrapper for arrays in god knows how many commits.

Re: Postman - a JavaScript message bus

Post by brutally_honest » Tue, Jul 19, 2011, 5:42 AM UTC

the-harsh-truth wrote: post #3

Congratulations. You managed to make a wrapper for arrays in god knows how many commits.

n00b

Re: Postman - a JavaScript message bus

Post by slace » Tue, Jul 19, 2011, 5:47 AM UTC

oinksoft wrote: post #2

No, it's a CoffeeScript message bus.

Well yes, but there is a JavaScript version in the github repository so you don't need to know what CoffeeScript is or anything

Re: Postman - a JavaScript message bus

Post by [deleted] » Tue, Jul 19, 2011, 6:01 AM UTC

[deleted]

Re: Postman - a JavaScript message bus

Post by drdaeman » Tue, Jul 19, 2011, 4:23 PM UTC

Could someone please explain me what's the point of this? I can't imagine any serious use case.

It looks inefficient (uses arrays instead of linked lists/queues, so every cleanup requires full array rebuild), lacks any sort of message ordering guarantees (or notifications of lack thereof), lacks queue length limits (only time-based expiry and custom cleanup functions seeing only the value of message are provided) and so on.

Moreover, I don't get the following:

    dropByDate = (date, msgs) ->
        msgs.reduce (x) ->
            x.created


I believe msgs is an array (cache[name].history), but IIRC Array.reduce does not work like this, it's Array.filter that does.


    
      Permalink
      View on HN
      Reply on HN
      Top


  
  
    
      Re: Postman - a JavaScript message bus
      #8
    
    
      slace
      HN member
      S
      
      
        Activity:
13
        Joined:
Tue, Feb 22, 2011, 4:44 AM UTC
        HN karma:
52
      
      
    
    
      Post by slace » Tue, Jul 19, 2011, 11:50 PM UTC
      
      

  
    drdaeman wrote:
    post #7
  
  
    
    
    Could someone please explain me what's the point of this? I can't imagine any serious use case. It looks inefficient (uses arrays instead of linked lists/queues, so every cleanup requires full array rebuild), lacks any sort of message ordering guarantees (or notifications of lack thereof), lacks queue length limits (only time-based expiry and custom cleanup functions seeing only the value of message are provided) and…
  


      
      I wrote this because the application I'm working on has dozens of small JavaScript components loaded, some of which rely on messages published by others. Some of them are invoked in-place, others are invoked as part of dom ready events so ensuring that the handlers are added before the messages are raised can't be done. Message ordering isn't important and since it's intended for asynchronous programming it shouldn't be important.As for linked lists vs arrays I'm not convinced that a linked list would be a better performer than an array for iterative access (which is a rather crucial part of the library).
The reduce thing is a bug (I've chucked it on the issue register) as well as a feature request for only keeping a finite message limit.
      
    
    
      Permalink
      View on HN
      Reply on HN
      Top




  Post reply on HN