nanogui: IPC client/server comm.


Previous by date: 30 Mar 2000 06:31:11 -0000 Please include me in the mailing list., 마종현
Next by date: 30 Mar 2000 06:31:11 -0000 Re: FLTK based browser running on Microwindows, Peter van Sebille
Previous in thread: 30 Mar 2000 06:31:11 -0000 IPC client/server comm., Martin Jolicoeur
Next in thread: 30 Mar 2000 06:31:11 -0000 Re: IPC client/server comm., Rob Taylor

Subject: Re: IPC client/server comm.
From: "Greg Haerr" ####@####.####
Date: 30 Mar 2000 06:31:11 -0000
Message-Id: <009201bf9a10$07fae2a0$15320cd0@gregh>

: In the context of a client/server model in nanox, I was wondering what
: is the benefit of using sockets (with an IP stack) for communications
: between the client and server if the client AND the server runs on the
: same CPU/machine ?
:
The socket is an AF_UNIX local socket, so it doesn't use the IP
stack or localhost.

However, I see your idea.  Perhaps Morten and/or Vidar could comment
on how well pure SysV IPC could be used without any unix sockets.


: Do you think integrating that communication mechanism in nanox would be
: difficult/long/annoying ? (I know that Morten already contributed shared
:
: mem support)

I'm also interested in another option: direct client framebuffer mapping.  This
would allow the client process to write the framebuffer directly.  It would have
access to shared code and data that would setup the appropriate clip
regions so that window heirarchies would be maintained...

Regards,

Greg




Previous by date: 30 Mar 2000 06:31:11 -0000 Please include me in the mailing list., 마종현
Next by date: 30 Mar 2000 06:31:11 -0000 Re: FLTK based browser running on Microwindows, Peter van Sebille
Previous in thread: 30 Mar 2000 06:31:11 -0000 IPC client/server comm., Martin Jolicoeur
Next in thread: 30 Mar 2000 06:31:11 -0000 Re: IPC client/server comm., Rob Taylor


Powered by ezmlm-browse 0.20.