[Olsr-dev] nameservice plugin for Windows with olsr 0.5.6
Tue Oct 28 22:05:54 CET 2008
Windows guru? Me!? Please do not link me to that - will give bad reputation
in a couple of years. Personally, I don't understand COM+ nor dotNET nor
XAML in depth. Have I mentioned there are really no MSV* certification
stamps in my CV?
To answer your comment: for what? A fifo simply saves (tmp disk) space and
makes it easier to extract data whithin cgi-scripts. Does anybody really
needs some analogon e.g for IIS / some scripting-host hacking worth digging
in the MSDN dirt? To my knowledge no embedded-XP based routers around, so I
doubt it's worth the hassle.
Bernd Petrovitsch wrote:
> On Tue, 2008-10-28 at 15:31 +0100, Sven-Ola Tuecke wrote:
>> if you don't understand #ifdef, this may be communication layer problem.
>> The function writes to something which is a fifo under linux and cause by
>> #ifdef to a thing named "file" with windoof. Do I miss something?
> As it somewhat fits here (and you seem to be the local Windows guru;-):
> Windows as such has named pipes as virtual hierarchy under "\pipe" IIRC.
> Isn't there a possibility to use that?
More information about the Olsr-dev