Re: Exception Misconceptions
In article <98095a1d-cca3-4ccc-9b82-9b3f7208f9b6@d21g2000yqn.googlegroups.com>, James Kanze <james.kanze@gmail.com> wrote:
On Dec 20, 8:40 pm, Brian <c...@mailvault.com> wrote:
On Dec 20, 7:06 am, James Kanze <james.ka...@gmail.com> wrote:
[...]
My first reaction to your description is that you obviously need
two processes: one doing the filtering, and another to manage
the GUI.
Correct. Except not processes, but threads I would think
And the reason for it is that you don't want your GUI thread
to lock up because of some processing hang in other threads.
Your GUI MUST be, AT ALL TIMES, responsive.
No matter what happens.
With a queue between them. In this case, from
experience, I'd say that two processes are a must, because you
want the filtering to maintain as small a footprint and use as
few resources as possible.
Has nothing to do with "small footprint".
But sorry, I have not much time to really dig into this stuff.
Cya.
Which means, BTW, that I would do it
in C++, and that I wouldn't use garbage collection, since
garbage collection does have a significant memory overhead (and
in such filtering applications, unlike a lot of other
applications, doesn't really buy you that much). For the GUI,
I'd use Java, because I know Swing, and I don't know any of the
C++ GUI libraries.
It might make sense to learn one of those C++ GUI libs since
then the filtering could be done in a thread.
In this particular case, I think a separate process would be
preferable. But that doesn't mean that I shouldn't learnone of
those C++ GUI libs. In case I get a different job, where
threads would be more appropriate.
--
Programmer's Goldmine collections:
http://preciseinfo.org
Tens of thousands of code examples and expert discussions on
C++, MFC, VC, ATL, STL, templates, Java, Python, Javascript,
organized by major topics of language, tools, methods, techniques.