Karma/Collaboration - Revision history

FGrose at 16:07, 3 August 2009

2009-08-03T16:07:07Z

← Older revision		Revision as of 12:07, 3 August 2009
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{~~TOCleft~~}}</noinclude>		<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>

	== Objective ==		== Objective ==
Line 64:		Line 64:

	[[Category:GSoC]]		[[Category:GSoC]]
			[[Category:Collaboration]]

Subzero at 04:29, 31 July 2009

2009-07-31T04:29:42Z

← Older revision		Revision as of 00:29, 31 July 2009
Line 52:		Line 52:
	* 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]]

Subzero at 04:15, 31 July 2009

2009-07-31T04:15:46Z

← Older revision		Revision as of 00:15, 31 July 2009
Line 45:		Line 45:

	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

	[[Category:GSoC]]		[[Category:GSoC]]

Subzero at 04:14, 31 July 2009

2009-07-31T04:14:13Z

← Older revision		Revision as of 00:14, 31 July 2009
Line 26:		Line 26:

	bemasc		bemasc
	* a DNS server and httpd server on each client. WikiBrowse		* a DNS server and httpd server on each client. (example WikiBrowse )


	m_stone:		m_stone:
	*name the people with one wishes to collaborate with:		* name the people with one wishes to collaborate with using:
			** Telepathy
			** DNS
			** D-Bus to telepathy

			* a way to get those names to the JS.
	** D-Bus to telepathy		** D-Bus to telepathy
	** HTTP to a webserver to D-Bus to telepathy		** HTTP to a webserver to D-Bus to telepathy
Line 39:		Line 44:
	** point-to-point HTTP links to peer webservers.		** point-to-point HTTP links to peer webservers.

	~~work in progress~~		Collaboration data:
			Bemasc has suggested to store the messages using files and directories
			/users could be a list of current users
			/$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 users, just poll /users.
			If you want to see what messages $USERNAME has emitted, poll /$USERNAME/

			Also one other way is using http PUT & GET

	[[Category:GSoC]]		[[Category:GSoC]]

Subzero at 19:46, 30 July 2009

2009-07-30T19:46:06Z

← Older revision		Revision as of 15:46, 30 July 2009
Line 4:		Line 4:
	To provide a mechanism to enable collaboration using JavaScript. On this way, we'll be able to support collaboration on Karma lessons.		To provide a mechanism to enable collaboration using JavaScript. On this way, we'll be able to support collaboration on Karma lessons.

	== ~~Examples~~ ==		== Use cases ==
			Examples:
	* A simple chat (over an html file), where you can see connected children to the activity and talk each other.		* A simple chat (over an html file), where you can see connected children to the activity and talk each other.

Subzero: Created page with '{{GoogleTrans-en}}{{TOCleft}} == Objective == To provide a mechanism to enable collaboration using JavaScript. On this way, we'll be able to support colla…'

2009-07-30T19:45:17Z

Created page with '<noinclude>{{GoogleTrans-en}}{{TOCleft}}</noinclude> == Objective == To provide a mechanism to enable collaboration using JavaScript. On this way, we'll be able to support colla…'

New page

<noinclude>{{GoogleTrans-en}}{{TOCleft}}</noinclude>

== Objective ==
To provide a mechanism to enable collaboration using JavaScript. On this way, we'll be able to support collaboration on Karma lessons.

== Examples ==
* A simple chat (over an html file), where you can see connected children to the activity and talk each other.

* Let's imagine a lesson: "Learning basic arithmetic", on this lesson we touch the topics: add, rest and multiply a number. At the end of the lesson we got the "Test". Here on "Test" one child writes a basic equation and challenges other child to solve it, then switch turns.

== The problem ==
How to create an easy way to write collaborative JavaScript to be run client-side in browsers.

== Keep in mind ==
* JavaScript has no model for distributed collaboration.
* Shared data can be considered volatile.

== Possible solutions ==
It would be ideally as simple as possible and as web-like as possible.

lucian has suggested 2 possible ways[http://honeyweb.wordpress.com/2009/07/29/generating-files-from-web-apps/]:
* Starting local servers in each Browse and using XMLHttpRequest(XHR) to send data between.
* Adding an API for this in window.sugar and using the existing Sugar collaboration Python API as a backend.

bemasc
* a DNS server and httpd server on each client. WikiBrowse

m_stone:
*name the people with one wishes to collaborate with:
** D-Bus to telepathy
** HTTP to a webserver to D-Bus to telepathy

* data transfer via:
** D-Bus + Telepathy
** a central relay webserver
** point-to-point HTTP links to peer webservers.

work in progress

[[Category:GSoC]]