View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002529 | MMW v4 | Properties/Auto-Tools | public | 2006-07-03 20:47 | 2006-08-03 17:09 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.5.4 | ||||
| Summary | 0002529: Freedb2 backup to freedb service | ||||
| Description | Currently the freedb servers are still working, however, we don't know whether: -they will continue working for long -they will continue to accept new submissions It would be a good idea to have a means of using freedb2.org over http as a backup solution in the event that freedb goes down. e.g. client tries to connect via freedb.freedb.org, gets an error --> MM tries to connect over http to freedb2.org There are other possible approaches to this. The main idea is that users should be able to get the metadata without having to manually reconfigure the server to which they must connect, and without adding new strings. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1002 | ||||
|
|
It would probably be safer to connect to something like freedbinfo.mediamonkey.com and download an updated list of working freedb servers in case the currently configured server doesn't work well. |
|
|
Good idea, though i'd suggest something like servers.mediamonkey.com so that it can be used for other servers as well (and because freedb may change names). Suggestion: the check can occur when a freedb lookup is initiated IFF a check hasn't been done within 2 weeks. Also, on the backend, it would be a good idea if some sort of message could be provided along with the server change. e.g. the xml file might be: ServerOption=FreedbServer (defines what server is being changed) ServerOptionSetting=New Setting for the defined Server option NotificationType=[Silent | Notify | Promt] (config change can be silent, can just notify the user of the change, or can prompt the user whether to accept the change) Message=Text message that should appear in the notification dialog This is probably overkill for now...just sharing my thoughts. |
|
|
Fixed in build 1002. - I used freedbconfig.mediamonkey.com, because it's currently used only for this purpose and I find it more flexible this way. - It does connect to MM server at most once a week in order to get secondary freedb server to be used in case the configured one doesn't work. - In case the configured server doesn't work for >1 week while the secondary server works fine, the configured server is automatically replaced by the secondary (to make lookups faster the next time). |
|
|
Verified 2.5.4.970. |
