What is the preferable size for modules that are distributed by a Code Server?
A13. It doesn’t matter – but the better broken up they are, the more seamlessly they can be distributed. Against that, the more modules there are, the more entries in the module interrelationship diagram there are (more searching, more association time), but we say that the time to associate is small compared to the time to download as long as the network is slow (and it always will be). Also, Code Servers can store the results (i.e. names, locations, and reference lists) in a database. Use of large modules is a stupid optimization which works when you have a fast disk. The original system we built this for had a slow network (1 MBps) and (potentially) NO hard disk. EVery so often someone points out that things load faster with larger modules (see for example this technical note from Microsoft), but with the Code Server approach we are pushing for smaller ones. Q14.
Related Questions
- The security of the information contained into a QO is preserved also if it is detached from the host server and distributed physically via e-mail or CD-Rom?
- Can server modules operate based on password-protected logons without requiring the user to know the password?
- What is the preferable size for modules that are distributed by a Code Server?
