On Sun, 01 July 2001, Risto Järvinen wrote:
...
> While I'm at it, I'd recommend trying to port PicoGUI to uClibc. glibc2
> is bloated (libuClibc.so is only ~150kB). OTOH uClibc is limited but at
> least busybox runs under it, so why not PicoGUI too. Though at the moment
> there is only partia
On Sat, 30 June 2001, Risto Järvinen wrote:
>
> Hi,
>
> Have you considered using unix domain sockets for client-server
> communications?
I have been planning to implement domain sockets all along, just haven't got around to
it.
What I'll (eventually?) get around to doing is modularizing the
Unix socket is a good idea. It will surely be included.
By the way, PicoGUI already run on uClinux.
-philippe
> While I'm at it, I'd recommend trying to port PicoGUI to uClibc. glibc2
> is bloated (libuClibc.so is only ~150kB). OTOH uClibc is limited but at
> least busybox runs under it, so wh
>
> Without TCP:
> System is 481 kB
> -rw-r--r--1 root root 496215 Jul 1 11:02 bzImage
> -rwxr-xr-x1 root root 1519072 Jul 1 11:02 vmlinux
>
> With TCP:
> System is 572 kB
> -rw-r--r--1 root root 589503 Jul 1 11:07 bzImage
> -rwxr-xr-x1 root roo
On Sat, 30 Jun 2001, Shane Nay wrote:
> On Saturday 30 June 2001 16:14, Risto Järvinen wrote:
> > Have you considered using unix domain sockets for client-server
> > communications?
>
> Config option makes sense mostly for cutting down on kernel size.
I did a preliminary measurement with Linux/x
On Saturday 30 June 2001 16:14, Risto Järvinen wrote:
> Hi,
>
> Have you considered using unix domain sockets for client-server
> communications?
Config option makes sense mostly for cutting down on kernel size.
Thanks,
Shane Nay.
___
Pgui-devel maili
Hi,
Have you considered using unix domain sockets for client-server
communications?
When both client and server reside in the same computer unix sockets
should be more efficient than internet sockets. Especially in the
embedded environments where you might want to conserve memory by removing
tc
