A third-party server solution that uses seven bull's image storage as a discuz so good?

The image storage of the seven cows was originally intended to facilitate the relocation of data by the user to exist

The official suggestion is that after the data has been relocated to seven cattle, the new images will be uploaded directly to the seven cows by the user (UGC site).

However, I used discuz remote accessory docking Seven cattle when I found some problems, it is inconvenient to use.

It's a very handy mirror storage feature.

So if I always use image storage as a solution, that is, the user uploaded images are saved locally and then automatically changed to a seven-ox url after the image is crawled once.

What are the disadvantages compared to direct remote attachments?

All I can think about is
1, because to go back to the source station to fetch the data once, so the first time to open the picture is slower (but the post-posting himself will load the picture once more, so in fact, no difference for other users)

2, will there be any additional fees to be added?

3, the server hard disk capacity requirements are higher, equivalent to a more storage costs (although not expensive)

4, please add?

Reply content:

The image storage of the seven cows was originally intended to facilitate the relocation of data by the user to exist

The official suggestion is that after the data has been relocated to seven cattle, the new images will be uploaded directly to the seven cows by the user (UGC site).

However, I used discuz remote accessory docking Seven cattle when I found some problems, it is inconvenient to use.

It's a very handy mirror storage feature.

So if I always use image storage as a solution, that is, the user uploaded images are saved locally and then automatically changed to a seven-ox url after the image is crawled once.

What are the disadvantages compared to direct remote attachments?

All I can think about is
1, because to go back to the source station to fetch the data once, so the first time to open the picture is slower (but the post-posting himself will load the picture once more, so in fact, no difference for other users)

2, will there be any additional fees to be added?

3, the server hard disk capacity requirements are higher, equivalent to a more storage costs (although not expensive)

4, please add?

Pull the source station resource directly through the image storage the first pull will be slower, the cost of the words will not change in nature, at most, the source station will be more than one storage, traffic will be more than one copy;

Mirrored storage a little bit more trouble, that is, when the mirror source station update resources, seven cattle will not take the initiative back to the mirror source to pull resources, because seven of cattle will have priority access to the resources already exist in the space, so if the mirror source station update resources, then you need to call the Prefetch interface or Actively delete seven cattle space of the same name resources, so that the next visit to the time of seven cattle to force back to the source pull resources.

