[hpsdr] Proposal for a new Software project.

[Bob Cowdery]

I fully agree that these are the right kind of questions to be asking
because they fundamentally affect the architecture and the subsequent
capabilities of the system. Software decomposition into components can
be as much a management tool as it is an architecture tool as it can
allow people to create components for a plug-in architecture without
having to wade through thousands of lines of code to establish exactly
where and how to add new features.

Loose coupling components through an event system rather than tight
coupling through direct connect interfaces makes the whole system
dynamic and solves problems like how does the DSP, hardware controller
or WHY know to receive frequency changes from something that wasn't even
there yesterday. It's not a case of where does it get the changes from,
because the answer is whatever can generate those requests, and moreover
each of the controls can know that the frequency is changing and track
the change. I build all my system that way but that's not to say other
people want to do that. Architecture is a very personal thing and
therein lies the problem of trying to lay down what it should be.

73's
Bob
G3UKB

Chris Albertson wrote:
> ***** High Performance Software Defined Radio Discussion List *****
> 
> On Tue, Dec 1, 2009 at 11:27 PM, David McQuate <mcquate at sonic.net> wrote:
> 
>> Are there other "channels" that should be considered in addition to TCP /
>> UDP?
> 
> That is way to low of a level to be worried about now.  What you need
> to thing about first are:
> 
> (1) what are the "things" that need to talk and what might they need to say.
> 
> (2) are the comunicatins channels one to one.  Or should each object
> listen to whom ever might want to speek.
> 
> (3) If an object needs to make a request does it need to know in
> advange who to ask or do we need a kind d directory service.
> 
> For example, say I plug in something that can act as a tuning knob.
> How does the DSP software know to listen to the knob and not the
> software slider
> 
> More generally when part are built by many people and we can't even
> know what parts are available or might be built years from now how can
> a part I make today be designed such that it can talk to something not
> yet designed.
> 
> The the things/object processes, computers, USB devices?????
> 
> The decision to use TCP, UDP or shared memory or
> 


 1259793404.0