http://bugs.winehq.org/show_bug.cgi?id=17195
--- Comment #42 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2011-12-16 14:16:01 CST --- dan, it's more than that: you're forgetting that NamedPipes are fundamental and critical to wine at a low-level. i've mentioned several times now that the implementation of ncalrpc [incorrectly] uses NamedPipes when it should be using an implementation of local-communication [that *can* be kernel-based or wine's equivalent thereof].
even just doing service start, stop and other management; registry edits and reads, *everything* that's fundamental to nt is based around MSRPC, and that means that everything that's fundamental is critically dependent [accidentally] on NamedPipes.
you will cause *massive* resource starvation. do a profile (gprof) on a range of applications (or use debug grepping, whatever) looking for WriteFile and ReadFile and Transact2 on NamedPipes. i think you'll find that even running "ordinary" applications has a severe performance penalty as well as massive resource usage.
i wrote this patch as a demo, and proved that yes it can be done but it is *not* suitable for production usage.