2 ms·
Probably ajax, which is more resource intensive/laggy than WebSocket-y and isn't bi-directional (you've got to poll with ajax if you want to push changes from t
by mcantelon 13y ago
Probably ajax, which is more resource intensive/laggy than WebSocket-y and isn't bi-directional (you've got to poll with ajax if you want to push changes from the server).
- wcummings 13y agoAjax is Good Enough for this use case (and probably a lot of others), imo. Even polling every 10s is plenty for messaging on a site like localbitcoins.