nanogui: Named Socket Binding and romfs
Subject:
RE: [nanogui] Named Socket Binding and romfs
From:
Fabrice Gautier ####@####.####
Date:
9 May 2002 00:55:11 -0000
Message-Id: <B1F6452C89AFD411AE0800A0CC734C239DBC15@EMAIL1>
> -----Original Message-----
> From: Thomas Gleixner ####@####.####
> Sent: Wednesday, May 08, 2002 5:32 PM
> To: Alex Holden; Fabrice Gautier
> Cc: Nanogui (E-mail)
> Subject: Re: [nanogui] Named Socket Binding and romfs
>
>
> On Thursday, 9. May 2002 01:26, Alex Holden wrote:
> > Fabrice Gautier wrote:
> > > So Is there any other solution I can use to connect
> > > client and server?
> Why don't you use the nano-x shared memory interface instead ?
Probably because i'm not quite sure what this shared memory interface is and
require. I tought this was not for communication between client and server
but for allowing a client to draw directly into the framebuffer.
I guess this shared memory interface uses SysV IPCs. And then I would think
the SysV message queues would have been used to implement the server/client
comunication not the shared memory.
So thats why I'm thinking this shared memory interface has nothing to do
with server/client communication. You'll tell me if im wrong but anyway the
IPC SysV support doesnt compile on my uClinux kernel so this would be one
more problem.
