Community
Participate
Working Groups
Build ID: M20070212-1330 Steps To Reproduce: 1- Create 3 connections to one IP for e.g 10.30.6.101. Each connection use a different username and password, this will point to different folders in the server. 2- I have 3 folders have files with the same name and folders structure. Let's say in my case I have a file name account_block.php in folder: /portal/includes/modules in connection #1. My connection #2 also has the name like that in the same folder struture. 3- When I open account_block.php from Connection #1, there's nothing wrong. But after that I try to edit account_block.php from Connection #2, it open the file from Connection #1 which is now put in /workspace/RemoteSystemsTempFiles. This happens because RSE creates a folder structure in local as: /workspace/RemoteSystemsTempFiles/10.30.6.101/portal/includes/modules/. With connections which connect to the same IP address and same folder structure and file names, it bugs. It should either: open the new file from connection #2 and replace the file in connection #1 (I guess this is still a bug because you can't open 2 file in the same time) or create each parent folder for each connection instead of each IP address as of now. More information: reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=185894#c9
There have been requirements to share temp files between multiple connections to the same host so this request is not entirely easy to fix. Especially, using the connection name instead of the IP address per default is not possible. We discussed this in http://wiki.eclipse.org/DSDP/TM/Committer_Phone_Meeting_26-Jun-2007 and we think that in the future, each subsystem could contribute different items for qualifying the path to the temp files; there will be a need to re-organize the temp files naming scheme anyways, because of bug #160100 and similar issues with files that have characters in their name which are not valid in the client file system. For now, one workaround is to use different hostname specifiers for your different connections, e.g. the IP address and the DNS hostname, and perhaps DNS hostname with domain stripped: e.g. 10.30.6.101 yourserver.yourdomain.com yourserver.yourdomain yourserver We know that this doesn't really scale but it might help for the moment. Another possibility might be to write an extension for the mountPathMappers extension point, see http://dsdp.eclipse.org/help/latest/topic/org.eclipse.rse.doc.isv/reference/extension-points/org_eclipse_rse_ui_mountPathMappers.html -- we are investigating this now. Given these possibilities, would you be OK with dropping the severity to NORMAL, since it looks like we cannot address this real soon?
thanks for the point out. By using the DNS hostnames it helps but as you said it's just for the moment.
Looking at the mountPathMapper extension point it looked like this would solve the problem since it allows an extender to customize where temp files are stored. However, I discovered that this, as currently used in RSE, will only help if the connection is for a local mount (i.e. a drive mount on windows). I've opened an enhancement request for this: bug #195285
Resolving this as a duplicate of 195285. To avoid temp files being shared between connections, the mount path mapper extension point can now be used, allowing custom locations within the temp file project. *** This bug has been marked as a duplicate of bug 195285 ***
Hm... so the question remains, what the default behavior should be? Should the temp files cache be shared between connections by default?
This is actually better fixed with bug 245260. *** This bug has been marked as a duplicate of bug 245260 ***
