At 2012-09-23 19:37:50,"Sylvain Rochet" <address@hidden> wrote:
>Hi,
>
>On Sun, Sep 23, 2012 at 05:41:46PM +0800, ?? wrote:
>> Hi All
>> Is there have a plan to let lwip support AF_UNIX domain? or multiple domain can register to socket dynamically.
>> If lwip support AF_UNIX domain, that can completely support of some software which need local communication with AF_UNIX socket.
>> So lwip will become very versatile.
>>
>>
>> Of course, before compile, AF_UNIX can be configured out from source.
>
>Humm, I don't see why AF_UNIX should be added. This is only useful for
>multi processes environment, which small embedded systems don't have,
>for obvious reasons, and it requires a filesystem abstraction able to
>create other than regular files (i.e. socket files), which are only
>available on filesystems which are several magnitude bigger than lwIP.
>
>Or I am wrong ? :)
>
>Sylvain
You are right, but the embedded systems becoming increasingly complex,If lwip support AF_UNIX domain, Many software porting will become very easy,
That do not even need to modify the code, If not, we will need to modify the code.
Also AF_UNIX can be retrenched, It will not affect the small system.
As for the file system, can only define a lwip_vfs structure, and achieved by porting the code.
If no plans in the future to support AF_UNIX, then a lot of the system will be continue to use the BSD / socket.
Because lwip socket layer currently very difficult to join a new domain by user now, I suggest that developers should join AF_UNIX domain. Thanks!
hanhui