First, the interface introduction:
1.
/**/Publicinterface websiteoperable {
2.
/**/Publicinterface interactable {
3.
/**/Publicinterface Iemailinfogeter {
4.
/**/Publicinterface Taskexecuter {
Second, the key class introduction:
1.
/**/publicabstractclass Abstractwebsiteoperater implements Websiteoperable, interactable {
and its subclasses
2.
/**/publicabstractclass Abstracttaskcommand extends Thread Implements Taskexecuter {
and its subclasses
3.
/**/Publicclass Taskdispatcher extends Thread implements taskdispatchable {
4.
/**/Publicclass Taskcommandfactory {
5.
/**/Publicclass Websiteoperaterfactory {
6.
/**/Publicclass Captchaverify {
7.
/**/Publicclass Cookies implements Cloneable {
8.
/**/
9.
/**/Publicclass Forms {
10.
/**/Publicclass Fileforms {
11.
/**/Publicclass Customforms {
12.
/* * A simple caching mechanism to cache objects and data that are created to consume a lot of resources. * Background: Strong references are not recycled under any circumstances * for softreference It is less stringent for GC to be recycled, * If the current strongest reference to an object is a soft reference and the JVM has sufficient memory, * The garbage collector is not recycled for that object. The GC reclaims the object pointed to by the soft reference only when the memory is tight, * from this feature we can see that soft references are used to do some caching, better with the LRU strategy. Today I will write a play. * * and for softreference it is less stringent for GC recovery, * If the current strongest reference to an object is a soft reference and the JVM has sufficient memory, * The garbage collector is not recycled for that object. * Only when the memory is tight, the GC reclaims the object pointed to by the soft reference, * from this feature we can see that soft references are used to do some caching, better with the LRU strategy. * */ Public class Referencecache<k, t> {
Introduction of mass software/promotion software interface