8,288
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + Line 45:
Line 45: + − + − + − + − + − + + + + + + + + + +
no edit summary
<noinclude>{{GoogleTrans-en}}{{TOCleft}}</noinclude>
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
== Objective ==
== Objective ==
Collaboration data:
Collaboration data:
Bemasc has suggested to store the messages using files and directories
Bemasc has suggested to store the messages using files and directories
/users could be a list of current users
* /users could be a list of current users
/$USERNAME/ could be a list of messages, displayed as files
* /$USERNAME/ could be a list of messages, displayed as files
To check for new messages, just poll the contents of /$USERNAME/.
* To check for new messages, just poll the contents of /$USERNAME/.
To check for new users, just poll /users.
* To check for new users, just poll /users.
If you want to see what messages $USERNAME has emitted, poll /$USERNAME/
* If you want to see what messages $USERNAME has emitted, poll /$USERNAME/
Also one other way is using http PUT & GET
Also one other way is using http PUT & GET
Flaws: it's all broadcast, and it's all polling.
Broadcast is inefficient in the network if you really only want to send a message to a single user. Polling wastes CPU, battery, and possibly network.
On way to handle polling is setting a high timeout for XHR. (Thanks Lucian)
[[Category:GSoC]]
[[Category:GSoC]]
[[Category:Collaboration]]