home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
My Anime 2
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="lwerndly" data-source="post: 697277" data-attributes="member: 64817"><p>This is very common for large collections.</p><p>If you get this error you should wait until your ban has been removed and then try running the import again.</p><p>It should pick up from where it left off usually.</p><p></p><p>The web cache was introduced for this reason (ie to reduce the number of calls to AniDB, and reduce the frequency of bans)</p><p></p><p></p><p></p><p>I would say it is a working title, Craig might disagree <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Not so much functional scope yet, more like some very high level goals.</p><p>The main one being to separate the back end functionality from the user interface</p><p>Back End = File hashing, downloading info from AniDB/TvDB, Database functionality, etc.</p><p></p><p>The main reasons for this separation?</p><p>- Allow the database to be shared between multiple clients e.g. you can use the client plugin on different machines and both machines will know which episodes have been watched etc, hashing of files is only done on one machine</p><p>- Allows creation of different types of clients without needing to re-do all the back-end functionality</p><p> - Definite Clients: Media Portal 2 Plugin, Windows Client</p><p> - Probable: Windows Media Centre</p><p> - Possible: Web Server/Browser Based, Android etc</p><p></p><p>For most users of MyAnime in MP, they probably don't care about this stuff, but it is important to some of us <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Other non-related goals (mine, other devs will have their own)</p><p>- Full support for localisation (other langauges)</p><p>- Support for SQL Server, SQLite</p><p>- Persisting of commands to database, so you can resume from where you left off for an import</p><p>- Simplified processing of files and commands (slower but more reliable)</p><p>- Searching on anime titles across languages, synonyms etc</p><p>- More powerful filtering and user defined views</p><p>- Name pattern matching like TV Series</p></blockquote><p></p>
[QUOTE="lwerndly, post: 697277, member: 64817"] This is very common for large collections. If you get this error you should wait until your ban has been removed and then try running the import again. It should pick up from where it left off usually. The web cache was introduced for this reason (ie to reduce the number of calls to AniDB, and reduce the frequency of bans) I would say it is a working title, Craig might disagree :) Not so much functional scope yet, more like some very high level goals. The main one being to separate the back end functionality from the user interface Back End = File hashing, downloading info from AniDB/TvDB, Database functionality, etc. The main reasons for this separation? - Allow the database to be shared between multiple clients e.g. you can use the client plugin on different machines and both machines will know which episodes have been watched etc, hashing of files is only done on one machine - Allows creation of different types of clients without needing to re-do all the back-end functionality - Definite Clients: Media Portal 2 Plugin, Windows Client - Probable: Windows Media Centre - Possible: Web Server/Browser Based, Android etc For most users of MyAnime in MP, they probably don't care about this stuff, but it is important to some of us :) Other non-related goals (mine, other devs will have their own) - Full support for localisation (other langauges) - Support for SQL Server, SQLite - Persisting of commands to database, so you can resume from where you left off for an import - Simplified processing of files and commands (slower but more reliable) - Searching on anime titles across languages, synonyms etc - More powerful filtering and user defined views - Name pattern matching like TV Series [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
My Anime 2
Contact us
RSS
Top
Bottom
