[Mono-list] POLL: How to write Mono Services (was Writing deamons in C#)

[Shahms E. King]

--=-xqVcHZHZ8aIg10cM8nhk
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

>  > We can always have a `monoservices' init.d script for the SysV to
>  > launch, and this one in turn would load the definitions for Mono
>  > services from a Mono-controlled directory, but that way we minimize th=
e
>  > integration work, and maximize flexibility.
>=20
> I'm also voting for the mono based service manager. Additionally to the
> compatibility issue I could imagine that we also would gain some
> efficience from using a mono based service manager: See the Mono runtime
> would be launched only once (potentially faster startup) and as long as
> not explicitly requested to deal it different all the services could
> life in appdomains of the same mono vm...
>=20
> Ciao,
> Mathias


Yes, doing it this way is infinitely preferable.  Once you have a
general mono services manager (msm) that handles ordering itself and
allows you to control individual scripts, it becomes a
packaging/distribution problem of how it gets loaded.  Each service can
even be individually integrated into the SysV startup process, provided
the msm can provide an in-order list of services.  A little scripting
magic could generate the proper symlinks/commands to add the services to
whatever the platform standard service system is, or it can be run to
just start all of the services itself, whatever fits the system.

--=20
Shahms E. King <shahms@shahms.com>

--=-xqVcHZHZ8aIg10cM8nhk
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA93FT2RsWY28vsX4ARAv4BAJ9f4Hy8fF0IyEG2yCmBRSZUFWIN9ACg1dEM
KkYKovLmtiwXpMnxl8UJkSw=
=L6it
-----END PGP SIGNATURE-----

--=-xqVcHZHZ8aIg10cM8nhk--