polling.3taps.com/anchor not working consistantly

[that1guy]

Hi Josh,

http://polling.3taps.com/anchor?auth_token=f2862071ede0bbd93bee4f091c522a9e&timestamp=xxx fails to give an anchor all too often.

{"success":false,"error":"No anchor found"}

This effects my local ingest agent and I can only assume it affects ingest agents in cloud too.

Just wanted to let you know you can get a new anchor another way too:

http://polling.3taps.com/poll?auth_token=f2862071ede0bbd93bee4f091c522a9e

{"success":true,"anchor":2308797101,"postings":[]}

If this is an issue in the cloud then perhaps we can modify the Node 3Taps library to get an anchor using this method?

[that1guy]

Since migrating to socket.io for feed this is no longer an issue on client-side. Also ingest agent appears to be working wonderfully with the 3Taps library.