Issue 26268 - Bad parameter "name" of UNO connection type "pipe"
Summary: Bad parameter "name" of UNO connection type "pipe"
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: 680
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2004-03-09 14:52 UTC by Stephan Bergmann
Modified: 2017-05-20 11:29 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2004-03-09 14:52:44 UTC
The current form of "pipe" connection strings (e.g., starting OOo with
"-accept=pipe,name=foo") is prone to introduce race conditions: the actual
pathname of the named pipe is not the value of the "name" parameter (but rather
some value computed from that value), so the constructor of a "pipe" connection
string (e.g., code that starts an OOo instance) cannot control that the
resulting named pipe pathname is not used otherwise.  It would be better to
replace the "name" parameter with something like a "pathname" parameter, which
denotes the complete pathname of the named pipe.  (Then, either the client could
create the pipe and pass its name to the started OOo instance, or the client
could create a dummy file with that pathname, and the started OOo instance would
have to remove it before creating the named pipe.)
Comment 1 Stephan Bergmann 2004-03-09 14:54:47 UTC
sb->tbe: FYI
Comment 2 kai.sommerfeld 2004-03-09 14:58:52 UTC
Comment 3 kai.sommerfeld 2005-12-05 15:23:20 UTC
Stephan, please take care.
Comment 4 Stephan Bergmann 2005-12-05 16:07:32 UTC
Comment 5 Marcus 2017-05-20 11:29:23 UTC
Reset assigne to the default "".