___ ___ _ _ ___ ___ ___ ___ _ ___ _ _ ______ _______________ _________ |_, |== |\| |== |-< |-| | | [_] |\| __/_/_______ _____ ___/__(_)_____________ ____/____________ ___________________________ _______ /__ ____ /_ ___ /__ ___/ _ \ / _ __ \_ __ `__ \ __ \ __ \_ __ \ _ \_ __ \ __/ ___ __/ __ / _ / / __/ /___ / /_/ / / / / / / /_/ / /_/ / / / / __/ / / / /_ /_/ /_/ /_/ \___/\____/ \____//_/ /_/ /_/_/ __/\____//_/ /_/\___//_/ /_/\__/ (c) Lada 'Ray' Lostak (c) Orcave (c) 1996-2004 FC server architecture ---------------------- FC server consists of 2 separate infos, usualy stored as separate section 'fcsrvr' in exacutable file. Server is just placeholder for components. Also, FC server have to export function 'FcServerAcquire' which returns pointers to 'Creators array' and 'Component infos'. 1. Creators array ----------------- This is just list of 'C' functions, which creates physical component instances. This section is avilable after module is loaded/relocated into memory. This block doesn't need to be a part of 'fcsrvr'. 2. Component infos ------------------ Heap of component infos. This section can be accessed without loading module into memory. Its just pure text based XML structure. Used structure: 00000000 00000000000000000000000000000000 123456789abcdef orcave.archivers.zip orcave.some.owner ZIP archite support (c) Orcave Dela hovno Dlouhej popis toho zd dela hovno Neco udelat Udelat neco jinyho 1.0 67 1.45 cFcFileSystem /booze/Whiskey/Fc/Src/Sould/FileSys/FcFileSys.cpp 0xB27A2448B47FD690 45