a stand-alone client/server 9P library including ixpc client
libixp is a stand-alone client/server 9P library including ixpc client. It consists of less than 2000 lines of code (including ixpc). libixp's server API is based heavily on that of Plan 9's lib9p, and the two libraries export virtually identical data structures. There are a few notable differences between the two, however:
- libixp multiplexes connections internally, while on Plan 9, the kernel performs this task, and in plan9port, a separate process is spawned to do so. Despite this divergence, the user of the library will not notice any difference in behavior, except that there may be duplicate tag and fid numbers between different connections. This issue is of little relevance, however, as the library handles the task of mapping fids and tags to arbitrary pointers and P9Req structs.
- libixp is released under a lenient MIT-style license, with the exception of the file intmap.c, which comes from Plan 9, and falls under the LPL. This file may be rewritten at some point, but the authors, as of yet, has been uncompelled to do so
- libixp lacks lib9p's file trees.
- Unlike plan9port's lib9p, libixp is POSIX based, and should compile without specialized libraries on nearly any POSIX system.
released on 20 September 2008
|License||Verified by||Verified on||Notes|
|License:Expat||Kelly Hopkins||31 March 2010|
|Other||Kelly Hopkins||31 March 2010|
Leaders and contributors
Resources and communication
This entry (in part or in whole) was last reviewed on 21 February 2018.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.