[gmpi] Re: multithreading host interface
- From: Martijn Sipkema <m.j.w.sipkema@xxxxxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Thu, 10 Apr 2003 19:08:46 +0100
> > I am in agreement here. I think that the documentation for every
> > function should list the following:
> >
> > 1.) Can the function be simultaneously called by multiple threads?
>
> i don't think it's necessary.
> the SET/GET_datas function can be called by one thread only (the GUI one)
> while the ProcessFonction is called in CriticalTime Thread.
How is the process thread supposed to get the data then?
> > 2.) Can the function ever be serially called by more than one thread?
>
> i don't think it's necessary.
> if an other Thread (than the GUI) wants to get or set data , we might
> provide another SET/GETfunctions. it's easier to go in this way than to
> design something where 5 threads can Get or Set context of the effect in
the
> same time.
>
> for example
> Get/Set for GUI port
> Get/Set for meter display port
> Get/Set for MIDI port
> Get/Set for ETHERNET port
> etc...
To be honest, I don't understand you at all...
There is a shared resource and having multiple functions access
that resource won't help.
> > 3.) Is the function time-critical? I.e., is it usually going to be
> > called by a very high priority thread.
>
> only the processing function i think.
And possibly other threads for asynchronous processing.
--ms
----------------------------------------------------------------------
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
Other related posts:
