sites

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs

commit 69d8aa7dfa827e74cc4866c870904a1e367c1d8b
parent 1c3da561ca4ff26b57dc834d0a737dce3c04e45c
Author: Connor Lane Smith <cls@lubutu.com>
Date:   Fri,  3 Jun 2011 00:41:18 +0100

update p9p link
Diffstat:
Mlibs.suckless.org/libixp.md | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libs.suckless.org/libixp.md b/libs.suckless.org/libixp.md @@ -4,7 +4,7 @@ LIBIXP `libixp`'s server API is based heavily on that of [Plan 9](http://cm.bell-labs.com/plan9)'s [`lib9p`](http://man.cat-v.org/plan_9/2/9p), 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](http://plan9.us/), 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 `fid`s and `tag`s to arbitrary pointers and `P9Req` structs. +* `libixp` multiplexes connections internally, while on `Plan 9`, the kernel performs this task, and in [plan9port](http://swtch.com/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 `fid`s and `tag`s to arbitrary pointers and `P9Req` structs. * `libixp` is released under a lenient MIT-style license.