[LineControl-development] Re: Future of KLCC / current state of linesrv3

[S. F. <lin...@sr...>]

Hello,

> as WLC is kind of dead

It is dead... at least from my side, and nobody seems to be willing
to take it over. The source is GPL since 2004-05-16.
I just don't have any interest in coding Windows applications and
learning all the neccessary things for it I currently don't know.


I'm glad to hear that something's still going on. Reminds me
somehow of finishing linesrv3. Motivation is not that big as
I learned a few things about softare design patterns after I
designed linesrv3 ;) (I think I started linesrv3 before I began
my electrotechnical engineering studies... which will be over
in about 27 weeks). Starting a large, sorry... long, project
and learning a few things afterwards though you should have
known them before can be quite tediously...

linesrv3 needs some polishing and a lot of bugfixes before
we can release a testing version. Registering/unregistering
a client works (LCP3, as linesrv2 is using), dialing works
too (at least for certain line types), but apparently I don't
catch SIGCHLD properly. The server terminates during hangup.

If anyone has the neccessary time and interest to help on
linesrv3, feel free. I suggest to use KDevelop or some other
IDE that helps navigating C++ classes. Before you start reading
the Line- / Client State Machines I suggest taking a look
at the following two documents:
ftp://fuchs.dnsalias.net/linecontrol/client-state-machine.pdf
ftp://fuchs.dnsalias.net/linecontrol/line-state-machine.pdf
They can be found in the source under linesrv-3/doc/code/*.pdf too.
.o0( hope I committed them ;)
And... yes, I know, the protocol stack is a horrible "design".
Logging doesn't seem work be implemented / work yet.

Greetings

Stefan Fuchs
---
http://srf.ch/