On 8/12/07, Pedro Côrte-Real <[EMAIL PROTECTED]> wrote:
>
>
> When would owserver need loop suppression? I understand that owlib has
> the functionality that's why owserver seems complicated for something
> that only has to answer three commands.
>
> I'm always open to suggestions and simplification.
The owserver code has 9 files:
owserver.c -- main, initialization, argument parsing -- listen socket
handler.c -- accept socket, handle persistency and start a thread for
"keepalive" messages unless real data has been sent.
data.c -- parse the message and answer based on type. Forestall the
"keepalives"
dir.c dirall.c read.c write.c -- call appropriate owlib routines
to_client.c from_client.c -- actually create or read the tcp messages.
Most of the complexity is probably in handler.c -- but it's a multithreaded
server with keepalive and persistence. More complax a problem than you might
think.
Paul Alfille
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
