Re: [Chicken-users] 1095 (prerelease) + some eggs

[Joerg F. Wittenberger]

Felix Winkelmann <address@hidden> writes:

> Joerg F. Wittenberger wrote:
> 
> > address@hidden:~/build/Askemos-0.7.0$ ./chicken/askemos
> > chicken/config.scm mechanism/debug-access.scm
> 
> > Fri, 21 Feb 2003 22:50:58 +0100 Debug access open at port 7070.
> > Fri, 21 Feb 2003 22:50:58 +0100 Take off.
> > Error: deadlock
> > The problem can be in a) the new scheduler b) tcp.scm c) askemos.  I
> 
> > guess it's not askemos for two reasons:
> 
> (BTW, this error means that there are no ready or blocked threads)

I see.  But with there are.  I'm pretty sure the detection is wrong.
I fire 5 threads 4 of them waiting at a network port and one at a
mailbox.  Then the last call traced is thread-join! in the main thread
waiting for the one at the mailbox.

> > Uhm, plans to have at least a private library directory?  (Or is this
> 
> > already there?)
> 
> Good point. If I understand you correctly, a private directory
> (say ".chicken-library") should then be searched before (and in
> addition to) the normal library directory, right?

right.  I expect users no to have write access to the installation
directory.  Or, if they need to the have to mess around with two
installations, a system wide one and a private one.

> >>Here a very simple example of it's use:
> >>http://www.call-with-current-continuation.org/server
> >>http://www.call-with-current-continuation.org/client
> > May I ask you a favor: can we try to integrate these implementations
> 
> > with the Askemos code.  I somewhat hate too much duplication in the
> > code base.
> >
> 
> 
> You mean the http stuff? Well, it's not really part of the
> official Chicken, just something I hacked together recently.
> The code really is pretty simplistic.

I see.  The Askemos HTTP and SMTP parts where the stepchild of the
whole Askemos code for too long and is still not complete HTTP 1.1.
What I'd love to have was a library of network code in srfi quality.
I feel it's a waste the everybody has to rewrite this kind of code,
which is a such simple, but easily confusing.

Well, maybe I'm wrong.  Maybe we all have to write some more ad hoc
code until we know how to do it the right way(TM).

What do people think is the best network protocol suite to go with?

so short

/Jörg
-- 
The worst of harm may often result from the best of intentions.