I am in the process of slowly porting an existing server (Process Control) to become an Avalon-Phoenix solution instead.Small comment - Component (the interface) is on its way out. you meant (small c) component right?
Yesterday, I managed to make "the whole sha-bang" into a Block and Assemble it into a server. Later I will break up the existing services to Blocks and existing subsystems into Components.
However, one immediate problem in the migration is the FileSystem. Are there any recommendations on how the "file system space" is managed? I.e. Is it meant to be that each Phoenix server puts all its file into its apps/abc-server/ space, even files that the "server user" is to maintain?Tis up to you. You can use relative or abolute paths for your own mamaged files. The current dir for phoenix is bin. via BlockContext (or a key via Context) you can ge tte hworking dir as I think you know, or you could have some concept of a config.xml driven absolute path. Nobody will have a problem with that.
In the existing solution I have a concept of ProductDir vs ProjectDir, where the former is a standard distro, that the user never change, and ProjectDir is for the user only, and can be placed at any place on disk with a simple pointer to change at startup. Any recommendations regarding this?Tis up to you. We're lacking some context for this. Any chance you can hint us about the application? It sounds intriguing.
- Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
