[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] Sockets, threads and GUI<->Kernel communication

From: Gabriel Dos Reis
Subject: Re: [Axiom-developer] Sockets, threads and GUI<->Kernel communication
Date: 12 Apr 2007 11:32:02 -0500

C Y <address@hidden> writes:

| --- Gabriel Dos Reis <address@hidden> wrote:
| > However, my fundamental point remains: common things should be
| > simple.
| > 
| > I think we should be careful about the arguments we make.
| Agreed.  My understanding was that it was the use of sockets itself
| which you were objecting to.

I'm objecting to unconditional use of "sockets" because they might
better handle the future.  

I think most of my objections are qualified :-)


| > | some introductory material on thread vs. socket issues that I could
| > | read?
| > 
| > They are not mutually exclusive, so I don't understand your point.
| I misunderstood your original objection - I thought sockets applied to
| Axiom in any fashion was a problem.  It sounds more like the way we
| CURRENTLY do things isn't so good regardless of mechanism, and that's a
| different sort of issue.


|  I'm surprised that this aspect of Axiom is
| complex, so there are clearly some design issues I'm not taking into
| account yet.

Well, they are not outstandingly complex, but they do add complexity.
When you try to port Axiom to say, ECL, SBCL, CLISP, etc. that added
complexity becomes non-negligeable.  Since, I've been doing that, I
think I let my exasperation out.

-- Gaby

reply via email to

[Prev in Thread] Current Thread [Next in Thread]