On Friday 21 February 2003 17.52, Angus F. Hewlett wrote: > On Fri, 21 Feb 2003, Paul Davis wrote: > > i don't believe that this example counters my claim that GMPI > > doesn't have to consider networking. plugins as we have defined > > them (we have defined them, right? :)) are not standalone pieces > > of code. they do not execute outside a host context. ergo, > > networking is not to/from plugins, but to/from hosts. hosts > > communicating with hosts is not part of what GMPI covers. > > hmm, a "plugin" can be regarded as two related components, "GUI" > and "DSP"... and is treated as such to some extent in both the DX > and AudioUnit architectures. That's the main area where to network, > or not to network, is significant. If both DSP "units" and GUIs are plugins (the latter may be stand-alone executables or DLLs), this makes no difference. If it's possible to connect plugins across host boundaries, it will Just Work(TM), like any other plugin->plugin connecitons. //David Olofson - Programmer, Composer, Open Source Advocate .- The Return of Audiality! --------------------------------. | Free/Open Source Audio Engine for use in Games or Studio. | | RT and off-line synth. Scripting. Sample accurate timing. | `-----------------------------------> http://audiality.org -' --- http://olofson.net --- http://www.reologica.se --- ---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission. Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe