Danke für den Hinweis. Wir haben das ganz selten auch beobachtet, aber konnten den Effekt noch nicht genauer eingrenzen. Wir haben unsere Entwickler informiert und werden das gut beobachten und untersuchen.

Ein Rechtsclick mit einer Maus auf Windows entspricht einem Control-Mausclick (sprich Control-Taste drücken und gleichzeitig mit der Maus klicken) auf dem Mac.

That's a great idea in principle and we have discussed it intenally already in the past. We came to the conclusion that we can not (yet) do it. There are a number or reasons:

- The Workplace uses the RCP framework quite intensively, but does so from a "self-standing" RCP app point of view - without considering any other uses. In other words, while we use Perspectives, Views, Status Bar, Splash, Icons, Initial Registration, Update Manager, Menus, and many more RCP features, it would require a very significant effort to make this work properly with the IDE and find a good way to combine the two worlds.
- The application is targeted at normal end-users and everything is made very simple and self-contained. If we integrated with an IDE, new requirements would come up immediately. Developers would want to share code, add features, have API's, share actions in other contexts, etc. This would end up becoming a totally different product.
- Unfortunately our resources are extrementy limited. So even if we would love to do so, we can simply not do it right now.

Collanos will evolve further and we plan to spearate the P2P Replication Engine and the Workspace Management from the actualy Eclipse UI in the near future. With an open API it will be much easier to call the services from different applications and UI's, including the Eclispe IDE.

Die aktuelle Version ist leider noch nicht auf Vista lauffähig. Die nächste Version ist aber schon fast fertig und wird kurz vor Ende März parat sein. Wir bitten deshalb um noch etwas Geduld und Verständnis.
Gruss aus San Francisco

Yes, it's is all related, unfortunately, to the mentioned bug. The forthcoming "Beta 2" will fix this.

Hi Laurin, just in case, did you follow the following steps: [url=http://community.collanos.com/index.php/topic,18.msg38.html#msg38]http://community.collanos.com/index.php/topic,18.msg38.html#msg38[/url]?

If you are still experiencing problems, please send us your Log Files. See here how to do it: [url=http://community.collanos.com/index.php/topic,30.msg72.html#msg72]http://community.collanos.com/index.php/topic,30.msg72.html#msg72[/url]

Thank you.

In most support situations, we might ask you to send us three Application Log Files. We need those files to analyze and fix the problem. The following post describes how to do this, i.e. where to find the three files and how to send them to us.

To start, please go to the directory where you installed the application. Typically this data is stored in the following path (on Windows) with the User Name being different from one machine to another:
C:\Documents and Settings\User_Name\My Documents\Collanos\MyWorkspaces

Note: If during installation you overwrote the default settings of where to store your data this path is not applicable.

In the "MyWorkspaces" folder you will see two files, one is called "error" and the other "transport" (both are text documents). There may be more than one file called "error". Please send us all of them.

The last file we need is in the sub-folder: "MyWorkspaces\.metadata". The file has no name but can be easily identified by the extension ".log". It is the only text document in that folder.

Please copy and paste these three (or more) text files into an email and send them to: support AT collanos DOT com.

Thank you very much for you help and we will get back to you very soon with an update.

Sorry to hear. Please read: [url=http://community.collanos.com/index.php/topic,28.0.html]http://community.collanos.com/index.php/topic,28.0.html[/url]

I am afraid you are affected by this issue. We'll be releasing a fixed version ASAP, hopefully within the next two weeks.

Your are right, we use JXTA for the basic transport layers. Good to see you know the P2P space!

Actually, we are not open source. We use several OSS components, but we are not ourselves open. Our basic version is free and will stay free. Maybe some Web site interpreted this wrongly. It would be interesting to find out where this was and have them correct this information. Can you remember where you saw this?

Still, if you like the idea of getting more involved, why don't you send me a private message or email at franco.dalmolin AT collanos DOT com. I'll be happy to discuss if we can work together is some ways.... Thx :-)

Unfortunately, some of you are experiencing serious synchronization problems. The resulting effects seem to vary from installation to installation, ranging from large files not being synchronized at all, to slow replication, all the way to unpredictable behavior, while many other installations work just fine.

Our engineers have analyzed this issue extensively during the last 2 weeks and have now identified the core problem. In certain circumstances the content replication algorithm would go “out of control” and produce a lot of unneeded traffic and congest/disrupt the real "net content" traffic, which would never get a chance to transmit successfully. The reason seems to be related to "internal timing" or "performance" of user's computers, i.e. on some computers it works fine, while on others we encounter this nasty situation.

This is obviously a serious bug (and it caught us by surprise)!! Engineering is fixing it right know!! A maintenance release (we call it "Beta 2") should become available very soon. We hope by the end of this month (to be confirmed). The new release will also fix a number of other minor issues.

If you are negatively affected by this issue, please accept our apologies. We are sorry for any inconveniences this may have caused you. Please bear with us for another two weeks. Thank you.

Hi Chrigui, thanks for your feedback.

A related question was posted/answered here: [url=http://community.collanos.com/index.php/topic,16.msg36.html#msg36]http://community.collanos.com/index.php/topic,16.msg36.html#msg36[/url].

This should (at least partially) also answer your question. If it does not well enough, please elaborate a bit more and get back to me with more questions. I'll be happy to provide additional information.

With regards to the "back server" functionality, we do have currently two services running centrally: (1) The so-called "Rendezvous" Service (see also above link to the other post) is responsible for keeping dynamic lists of "who is currently online" and "where". (2) The so-called "Relay" Service is needed to help route traffic between any two peers, if one (or both) of the peers are behind firewalls with only Port 80 / HTTP protocol enabled.

BTW, a great new body of knowledge is the following book: Peer-to-Peer Systems and Applications (Lecture Notes in Computer Science) (Paperback)
by Ralf Steinmetz (Editor), Klaus Wehrle (Editor).

Hi Steve, great points, thanks!

Drag and Drop will become available very soon. We plan to deliver this with the next major release, maybe even in an earlier maintenance release. Specifics will be annoucnced relatively soon.

With regards to transmitting only changes, we already today capture binary changes to file content and transmit only the changes. This means that a small change to a 10 MB PowerPoint file could result in a "change element" of e.g. only 10 kB that will be transmitted to the other peers. We'd achieve a factor 1000x optimization in this example. This feature is already in the product today!

Regarding the "check-in/out" feature, please read also http://community.collanos.com/index.php/topic,20.msg46.html#msg46 that lines out related concepts.

I like your proposal of publishing a roadmap. This will give us a great opportunity to capture your comments, votes, and priorities. Please give us a few more weeks, but I can commit already today that we will make our roadmap more transparent very soon.

We look forward to keep in touch with you and get your valued feedback. Thanks so much.

Hi Steve, thanks for your post.

We are not aware of this problem yet, so it's very important for us to find out what exactly causes this and track down the problem properly. There are three Log Files that we would need to analyze to find out more.

Please go to the directory where you installed the application. There in the folder [b]..\Collanos\workspace\[/b] you will see two files called "[b]error[/b]" and "[b]transport[/b]" (both are text documents). The last file we need is in the [b]..\Collanos\workspace\.metadata\[/b] folder and has no name but is the only text document in that folder.

Please copy and paste these three documents into an email and send them to support AT collanos DOT com.

Thank you very much for you help and we will get back to you very soon with an update.

Hi Louis, thanks for pointing this out. Email "integration" is a hot topic. While do don't want to become yet another Email Client, there are a number of Email support and integration scenarios that are possible:

1) Simply drag and drop an email message from your Email Client to a workspace. This would store the file as an Email Message type. Double-clicking would bring you back to your email client. Drag and drop will be provided very soon. :-)

2) Sending one or several objects to somebody from the Workplace using Email. This is very simple and would just make it easier to share content with others by Email.

3) Moving one or several Emails (including all their attachments) into a Workspace, by providing a Plug-In for your Email Client, e.g. a "Store in Collanos" button that would be added to your Outlook Email client. The problematic aspect here is: Everybody uses different Email clients and we also run on Windows, Mac and Linux. Very difficult for us to provide ALL the right plug-ins...

4) A recent idea is "Email only Members". This is somebody that you can add to your workspace. Every change that happens in the space would then be captured and sent by Email to this special member type. This could be ideal to keep somebody in the loop if they don't want to install Collanos, but could potentially generate quite many Emails in a "busy space".

Of all of the above, which scenarios would be the most relevant for you? What solution would be "sufficient" in a first release?

Thanks for your input!

The current release does not offer any specific conflict resolution strategies. At the moment the default behavior is "last change wins", which works fine if a group is coordinating their tasks at hand. Of course, if everybody just begins to make changes, this will obviously not work. For such situations, we will deliver additional features in the future:

- Simple ad-hoc workflow that controls who can do changes in what order (e.g. ideal for review processes)
- Locking of files (will not work in offline mode, needs participants to be online to receive the right to edit)
- Automatic generation of versions, i.e. conflicts will be captures and saved as "version trees"
- Historisation of all changes, which would allow reverting back to any previous version (also valuable as "audit trail")

Which of the above approaches would you deem the most important for a distributed team and the most relevant features for you? If you had to choose just one or two of the above, which ones would you pick?

Propagation of the object deletion action falls into some of the above options (e.g. "audit trail" could save deleted objects). In the current version, you can assign somebody Participant or Guest permissions, to prevent them from deleting. At the moment there is not a "general" way to prevent that somebody deletes a file from the workspace.

Thanks your valued feedback!