fix double notification

notifications come from initial subscription and from change on the
object. the race was possible. now completion of publishing comes when
object is loaded and it is equal to the published.
assume that there is only one publisher for the same object, which was
always the rule of the game.
test was not accurate

following notification can swallow previous. this is legitimate.
minor tuning
test with node 0.10
tune test
serialize execution of publishing for the same object

this allows to publish concurrently from the same application and be
sure the completion of publishing would be satisfied.
async  0.2.x
cosmetic
typo
cosmetic
test case that shows object state reverted by completion

Change in object got wiped upon publishing completion.
This is problematic from usage perspective and require changes change in
how rebus handles published data in the same process
no load for published files

published files are managed locally.
update tests
typo
Merge branch 'master' of https://github.com/anodejs/node-rebus into yosefd2
try without os.tmpdir()
Merge pull request #13 from anodejs/yosefd2

revised handling of handling object in process that publishes it