[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Distributed collaborative development with Saros
Saros actually selects between multiple transmission methods, depending
on what the server supports. It favours SOCKS5 (direct or mediated), but
will fall back to IBB if it cannot achieve such a connection.
--- Begin Message ---
- From: Ali Naddaf <ali.naddaf@xxxxxxxxx>
- Date: Thu, 22 Jul 2010 15:02:12 +0200
- Accept-language: en-GB, de-DE, en-US
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=HjW9HhHgU4QBhG42Qbn7SxzEQ69BilGyeTMekbRvHwGpV68QGoyYdZ/q2W9D6FEIRb splhvO/KPyiN3Lzb0PQ16YXOy6vvN3V6OEhFLwnQYHLumevQE/+fCtok4Ryxj4dhBnMy mKMsOBFcBJRnqG3wc/AJlwgxOH5G8bQ9sjrkk=
- Thread-index: AcspniQGecHCqvaGSFifD1WrEVC+SQ==
- Thread-topic: [ecf-dev] Distributed collaborative development with Saros
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:18.104.22.168) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5
Thanks for the introduction to your project, sounds very nice and I will
give it a try. A minor question: it looks like you are using the Smack
library in your plugin. On your site, you mention that one can use
talk.google.com as the xmpp server. I was under the impression that file
transfer implementation in google's server is not standard and smack
file transfer doesn't work with that. Are you using the xmpp file
transfer mechanism for sharing projects or there is a different
approach? If it is based on the xmpp file transfer, how does Smack use
google jabber server to achieve that?
On 7/22/2010 7:10 AM, Beecher, Karl wrote:
> Hi Ecf-dev,
> After earlier conversations with Scott Lewis and encouragement from him, I would like to introduce myself to you all along with the project I represent.
> Who am I?
> I am a researcher within the Software Engineering Workgroup at Freie Universität (Free University) Berlin. I manage the Saros project.
> What is Saros?
> Saros is a fully-functional Eclipse plug-in that enables two or more developers to work simultaneously over the Internet on a shared project and share each other's changes. It grew out of ongoing research into the difficulties posed by distributed collaborative development.
> How does Saros work?
> At its simplest, Saros works like a collaborative editor. After inviting a number of other users, you can jointly edit any artefact in your Eclipse project and see each other's changes.
> However, there is more. Saros provides in-built communication methods (including IM, VoIP and screen-sharing), a roster, and also simple user role management (each user can be a "driver" or an "observer", and a user can automatically "follow" another user's movements).
> Exciting features currently in development include whiteboarding and version control system integration.
> Any technical details?
> I won't go too deep into these, suffice it to say that Saros:
> - is written in Java
> - uses XMPP protocol for low-latency, high bandwidth communications
> - is tested in Eclipse 3.4, 3.5, 3.6 on Windows (XP, Vista, 7), Mac OSX, and Linux
> So, why am I here? We in the Saros team are very intrigued by the possibilities of working closer with the ECF project, given how the goals and the technology of the ECF overlap with ours. For now, I'd like to learn more about your project and I would be happy to answer questions about mine. In time, we could exchange ideas and contributions, and so improve our software.
> In the meantime, feel free to refer to the following resources:
> Website: https://www.saros-project.org
> Update Site: http://dpp.sf.net/update
> Saros @ SF: http://sourceforge.net/projects/dpp
> I look forward to a dialogue.
> Yours faithfully,
> Karl Beecher
> Dr. Karl Beecher
> Research Associate
> Software Engineering Workgroup
> Department of Computer Science
> Free University of Berlin
> Takustr. 9, 14195
> Berlin, Germany
> ecf-dev mailing list
--- End Message ---