From e05653f72039714f339d945316d4f67e0f583369 Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Sun, 21 Sep 2014 03:07:52 +0200 Subject: m + advantages and disadvantes with the architecture MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- doc/info/mds.texinfo | 68 +++++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 65 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/info/mds.texinfo b/doc/info/mds.texinfo index fac11b4..4bf497e 100644 --- a/doc/info/mds.texinfo +++ b/doc/info/mds.texinfo @@ -59,8 +59,9 @@ Texts. A copy of the license is included in the section entitled * Servers:: About @command{mds} servers. * Protocols:: @command{mds} procotols. * libmdsserver:: Overview of @command{libmdsserver}. -* mds-base:: Overview of @command{mds-base}. +* mds-base.o:: Overview of @file{mds-base.o}. * Keyboard Codes:: Scancodes and keycodes. +* Discussion:: Discussion on display server-architecture. * GNU Free Documentation License:: Copying and sharing this manual. @end menu @@ -4648,8 +4649,8 @@ in the display server message passing system. -@node mds-base -@chapter @file{mds-base} +@node mds-base.o +@chapter @file{mds-base.o} @file{mds-base.c} and @file{mds-base.h} as an object filepair whose purpose is similar to libmdsserver. @@ -5074,6 +5075,67 @@ Right @kbd{super} key +@node Discussion +@chapter Discussion + +This chapter aims to enumerate advantages and +disavantages with micro-display servers and +traditional monolithic display servers. Please +chime in with any insight. + + +@b{Advantages of the microserver architecture:} + +@itemize @bullet{} +@item +Knowing the names of the servers you use and +their purpose makes it very easy to find where +you want to do patching in the source code. + +@item +If the message passing used in the display server +allows for message modification and retrieval +ordering, extending, modifying and using the display +server in unforeseen ways becomes much easier, +and will often not require any modifications to +the existing servers. + +@item +Replacing the display server is easier than it +is for a monolithic display server, because there +servers could be replaced one by one and could +even support running under two distinct protocol +during the transitional period. + +@item +Not as many subprotocols needs to be defined. +For example, recording the output of the display +does not require a special protocol, one only +needs to write a server that listens on messages +passed between servers. + +@item +If a server crashes it does not crash the entire +session. Crashes can most often be repaired. +@end itemize + + +@b{Advantages of the monolithic server architecture:} + +@itemize @bullet{} +@item +The monolithic architecture makes it trivial +to isolate information for clients to achive +confidentiality. + +@item +Monolithic server does not need to pass messages +between modules, but can rather perform normal +function calls and achive greater performance. +@end itemize + + + @node GNU Free Documentation License @appendix GNU Free Documentation License @include fdl.texinfo -- cgit v1.2.3-70-g09d2