For a long time, I have never liked the smart design and implementation. For example, many products under Windows, users are not dummies, at least for people like me :)
Therefore, when designing and implementing our Abacus system, I handed over all the things that I could not do to the user, because if the user did not, it could not be done, of course he knows when to do this :)
Case1 classpath management:
If the virtual machine is used, it seems redundant and binds Abacus file system and Abacus VM together. I do not like this and it may cause many name conflicts... So the user is the smartest :)
Case2 service reload:
If the virtual machine does this, the overhead is to check whether there is a latest service file in the file system every time you find a service instance. Obviously, it doesn't matter in a small system, but if the system runs an eclips application, it will only crash the virtual machine. in addition, the frequency of service reload calculation is not high, only during the virtual machine running process, the user updates ProgramThis problem occurs only when it is released again. Therefore, this is the smartest user. He knows what to do, right? haha.
The above are two lazy jobs I did in March, haha
Simply is beauty. Lazy is also beauty. I like both HS and beauty :)
