On 05/16/2012 08:16 AM, Jiri Svoboda wrote: > Jakub wrote: >> Shouldn't have websrv stayed under app/ as it does not provide a HelenOS >> service of its own? It is merely an application which listens on a TCP >> port... > Just like loc is merely an application which listens on IPC interfaces :-)
Well, this is what makes locsrv a system service. > IMNSHO the classification /app - Application and /srv - Server > should be based on the interaction class of the binary. That is, servers run (are meant to run) in the background (cf. UNIX daemon, Windows service) and applications run in the foreground. This is a rather clear classification and makes sense from the user's point of view. What kind of interface the services are presented over (IPC, socket, ...) seems immaterial. The idea is that /srv contains system services that are essential for the proper functioning of the system: locsrv, vfs, inetsrv, ns. These are supposed to be the 'servers' as in 'multiserver'. On the other hand, websrv is not that essential and falls into a completely different category. Typically, the user will not want to run anything from /srv manually, which might not be the case of websrv. To make the distinction clearer, we could introduce something like /netsrv or /dmn or /usrv. Jakub _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
