To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110878 Issue #|110878 Summary|Slow open/save when using network paths Component|Word processor Version|OOo 3.0.1 Platform|PC URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|save-export Assigned to|writerneedsconfirm Reported by|keme6206
------- Additional comments from [email protected] Wed Apr 14 13:22:04 +0000 2010 ------- This is more of a theory than an issue in its own right, but it may point to the cause of a few other issues reported. The eye opener for me was a forum thread: http://user.services.openoffice.org/en/forum/viewtopic.php?f=6&t=26710&start=0 I have tested this on a somewhat old setup, using OOo 3.0.1, but the forum discussion confirms the issue on OOo 3.2, so I guess it shows about the same behavior. It seems that if a network path is connected, OOo assumes http/port 80. If the network share is mounted (assigned a drive letter), the correct port/protocol is selected. When I set up a network path ... >net use \\server\share password /user:myself ... the share appears in my "network places". I get write access, and can save and open a file on the share. With a simple Writer file (containing only the word "test"), open and save takes anything from 10 to 30 seconds. Close takes 5-10 seconds. When I mount the shared folder by using a device name (drive letter) ... >net use H: \\server\share password /user:myself ... the share appears as an available network disk. That same Writer file opens in 1-2 seconds, and saving is about the same. Close time is near zero (less than half a second). I tested the above several times, alternating between the two connection methods, to avoid being fooled by preloaded content/modules. I also tried alternating between OOo dialogs and Windows common dialogs for open/save. The results were consistent. Copying back and forth over the connections did not display any delay. >From the above (including the network traffic detected by ChelseaIT in the >forum thread I referred to) I guess that protocol/port negotiating on network paths starts with http, and does not continue until there's a timeout or connection reject (which may take considerable time). Can OOo improve the port/protocol identification on network paths? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
