OWAMP is a command line client application and a policy daemon used
to determine one way latencies between hosts. It is an implementation
of the OWAMP protocol as defined by RFC4656.
With roundtrip-based measurements, it is hard to isolate the direction
in which congestion is experienced. One-way measurements solve this
problem and make the direction of congestion immediately apparent.
Since traffic can be asymmetric at many sites that are primarily
producers or consumers of data, this allows for more informative
measurements. One-way measurements allow the user to better isolate
the effects of specific parts of a network on the treatment of
traffic.
- rc scripts added (names suggested by Nigel Taylor, I was having
a hard time coming up with something nice that avoid a conflict with
base snmpd now the rc.d namespace is shared).
- Get rid of using libtool's --tag=disable-static option.
- Stop moving the libjabber / liboscar libraries and properly set
the rpath for the XMPP / AIM / ICQ protocol plugins.
From Brad (MAINTAINER)
ac_cv_openssl_libs "fix" and WANTLIB fix by me.
GUPnP-UI is a collection of GTK+ widgets on top of GUPnP. It features a
GtkTreeModel exposing devices discovered by a GUPnPControlPoint and a
GtkTreeView for exposing such models.
ok aja@
GUPnP Tools are free replacements of Intel UPnP tools that use GUPnP.
They provides the following client and server side tools which enable
one to easily test and debug one's UPnP devices and control points.
ok aja@
GUPnP DLNA is a small utility library that aims to ease the DLNA-related
tasks such as media profile guessing, transcoding to a given profile,
etc.
ok aja@
- traded -pedantic for -Werror (per tedu@'s earlier comment),
- SHARED_ONLY=Yes, because all binaries were removed in 2.1.x.
from piotr sikora
maintainer timed-out
GUPnP is an elegant, object-oriented open source framework for creating
UPnP devices and control points, written in C using GObject and libsoup.
The GUPnP API is intended to be easy to use, efficient and flexible. It
provides the same set of features as libupnp, but shields the developer
from most of UPnP's internals.
ok aja@
- tightvnc-server is based on a really old X release - it barely
works on i386, but doesn't support most X clients - and fails on most
other arch (it's neither LP64 nor big-endian clean).
x11vnc is a suitable alternative for some users, anyone interested
in the exact same type of functionality (standalone RFB X server)
should look at porting tigervnc.
- ssvnc-viewer is a significantly improved fork of tightvnc-viewer
and basically a drop-in replacement (same filename for the viewer).
ok dcoppa@ and supported by weerd@ and various ports@ readers
