On Mon, Jan 14, 2008 at 08:24:40PM +0100, Pieter Palmers wrote: Many thanks for this (long awaited) release. Finally we have a complete set of callbacks to monitor clients, ports and connections without requiring polling for information all the time. Some questions about these. The port_id seems to be an integer in the range 0..MAX_NUMBER_OF_PORTS - 1, in other words an index into an array of preallocated port_t structs, with jackd using the lowest available ones for new ports. Any app wanting to keep a list of all existing ports, connections etc. would need to do something similar for its own per-port data structs. Can the port ids be safely re-used for this purpose ? In other words are they specified to behave as they do now ? It would be useful. Also what is the cost of looking up port_t pointers, port names and aliases given the port_id ? If they are just read from memory mapped at the client side it makes not sense for a client to store this information itself, for e.g. a GUI refresh. If not, it would be essential for a client to do so. Ciao, -- FA Laboratorio di Acustica ed Elettroacustica Parma, Italia Lascia la spina, cogli la rosa.