What steps will reproduce the problem?

on machine 1 1. check out svn revision 149 2. make 3. make runx

on machine 2 4. navigate to http://machine1:3001 5. subscribe to time demo

on machine 1

6. erlycomet_demo:status().
7. result is: Total connected clients: 0

What is the expected output? What do you see instead? even though the client is connected and subscribed

What version of the product are you using? On what operating system? svn rev 149, gentoo linux, erlang 5.6.1

Please provide any additional information below.

seen on:

svn rev 149 ubuntu linux 2.6.24-23-xen SMP - x86_64 (Running on Slicehost) erlang 5.6.3

When trying to access demos via firefox, logging window at bottom of page reports:

cometd?message=%5B%7B%22version%22%3A%20%221.0%22%2C%20%22minimumVersion%22%3A%20%220.9%22%2C%20%22channel%22%3A%20%22%2Fmeta%2Fhandshake%22%2C%20%22id%22%3A%20%220%22%7D%5D&jsonp=dojo.io.script.jsonp_dojoIoScript1._jsonpCallback (line 1)

I met the same issue, I use fedora 11 x86_64, when request http://localhost:3000/, firebug displayed

POST http://localhost:3000/cometd 404 Object Not Found 74ms dojo.xd.js (第 20 行)

and erlycomet_demo:status(). was 0.

I traced this error to the included /priv/ebin/*.beam files for a 2007 version of Mochiweb with bug as described at http://code.google.com/p/mochiweb/issues/detail?id=11 and fixed in Mochiweb revision 72. To fix with ErlyComet:

cd ~ svn checkout http://mochiweb.googlecode.com/svn/trunk/ mochiweb-read-only cd mochiweb-read-only make rm ~/erlycomet-read-only/priv/ebin/* cp ebin/* ~/erlycomet-read-only/priv/ebin cd ~/erlycomet-read-only make clean run

This will result in the samples running as expected.

@juliadotter: Thanks for your comment. This helped me.