I'm working on the design stage of turning my csound sequencer into a host
app that will embed csound, and I plan on using some sort of multi-threaded
client-server archictecture for the sequencer whereby the sequencer engine
will be a high priority timing-critical server that sends output to csound
through the csound api, but also is able to receive input from from multiple
clients that maybe completely different processes and will be lower
priority. Ie, many users can send data to the sequencer through client input
modules that could even be on different computers connected to the server
over sockets, pipes, midi, what have you.

What I would like to know is:

- what should I be researching? I am new to multi-threading, event driven
programming, and client-server architecture period.
- anyone have any good tutorials to recommend, or good books, or good code
to look at?
- any suggestions on specific approaches that would be good to look at?

I would like to spend some time doing enough research that I start with
fewer features and good extendable and scalable architecture rather than
just making it go and having to rewrite it later. I've done enough
prototyping in csound to know how I want the sequencer to behave and work,
but I don't know much about implementation.

Thanks in advance
Iain

_______________________________________________
csoundtekno mailing list
csoundtekno-N4abDuUB7xo@public.gmane.org

Subscribe, unsubscribe, change mailing list options: