Re: [GD-Windows] Process communication

[David H. <da...@em...>]

Jon and Kent thanks, I'll take what you both say about maintaining parallel
component based systems on board.

    But it seems to me that once you go the step of deciding you need to
compile to a big flat file for production data you might just as well design
around this big file in the first place and also design all the
associative/dependency stuff straight in there.
    Eg. If I know level 4 is dependant on Texture "brick4" with crc 0x12345,
why not simply store all that dependency stuff straight into the database
along with the texture and the level assuming I can make the process as fast
as a file copy (or similair through version control software). Once you've
written your core delete record,add record,replace record functionality I
can knock an entire level out of the database and come back in the morning
to find all data which makes up "level 4" gone except for shared
textures/objects.

:)


David