An inspiration 1.1.3.1.5
As a practical application, I'm writing a simple mail client that the time has been compared JExp several saved Message object (mainly a few key attributes and message content) to the local method, such as XML, Properties, etc., and finally chose to use serialized way, because this method is the most simple, some can be regarded as "Learning" strike. Here "to access the program state" is actually only an introduction topic it may, I want to say is? ? Just as we discussed earlier on the same topic of logging? ? In front of the same problem Java you can have a variety of solution: familiar file operations, you may feel Properties, XML, or more convenient Bean, Preferences and then found there is such a stuff, probably will also lamented that "there is day" , and until you touch a very wide range of new method, the results would "converge" to re-reflect on Serialization mechanism itself. This is not just Java, science is also the same reason.
As a practical application, I'm writing a simple mail client that the time has been compared JExp several saved Message object (mainly a few key attributes and message content) to the local method, such as XML, Properties, etc., and finally chose to use serialized way, because this method is the most simple, some can be regarded as "Learning" strike. Here "to access the program state" is actually only an introduction topic it may, I want to say is? ? Just as we discussed earlier on the same topic of logging? ? In front of the same problem Java you can have a variety of solution: familiar file operations, you may feel Properties, XML, or more convenient Bean, Preferences and then found there is such a stuff, probably will also lamented that "there is day" , and until you touch a very wide range of new method, the results would "converge" to re-reflect on Serialization mechanism itself. This is not just Java, science is also the same reason.
No comments:
Post a Comment