1,633
edits
SigServer DEV: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{TOCright}} | {{TOCright}} | ||
{{eyecatch|Note | {{eyecatch|Note|'''This page only lists development resources. If you're interested in using the AniDB Signature Server, visit: [[SigServer]]'''}} | ||
=General= | =General= | ||
This is the place to contribute ideas on a possible future addition of a special signature picture feature to AniDB. | |||
Related forum thread: [http://www.anidb.net/forum/viewtopic.php?t=5413 AniDB Development Forum - SigServer] | Related forum thread: [http://www.anidb.net/forum/viewtopic.php?t=5413 AniDB Development Forum - SigServer] | ||
| Line 11: | Line 11: | ||
=Vision= | =Vision= | ||
AniDB users can create highly | AniDB users can create highly personalised signature images which can be used in forum signatures and which accurately reflect user specific or general AniDB data. Some examples are: | ||
* | * MyList statistics of the user (MyList size, latest added, latest watched, total watched, ...) | ||
* Vote statistics general or user based (Top3 | * Vote statistics general or user based (Top3 anime, my Top3, worst anime ever, ...) | ||
* General AniDB statistics | * General AniDB statistics | ||
* Group statistics (Latest releases by group X, ...) | * Group statistics (Latest releases by group X, ...) | ||
| Line 21: | Line 21: | ||
The user would not need any webspace to host such images and would not need to update/regenerate them. All signature images would be directly loaded from an AniDB webserver. | The user would not need any webspace to host such images and would not need to update/regenerate them. All signature images would be directly loaded from an AniDB webserver. | ||
The idea is for the sig server to be the middle entity between AniDB and the user, which allows almost any kind of | The idea is for the sig server to be the middle entity between AniDB and the user, which allows almost any kind of signature pic to be created, according to the personal preferences of the user. As such a lot of attention should go towards the configuration/customisation interface of such a feature. We are aware that this is a hell lot of work, but it's the long term goal. The image generation itself is fairly easy. | ||
Basically AniDB will offer all kinds of stats data and more via | Basically AniDB will offer all kinds of stats data and more via XML, much more than is currently on offer. The sig server would transparently get it's data from AniDB and the user will be able to pick all kinds of information bits from the available data and position and format it freely on a background pic which he can upload himself. | ||
Of course many users wouldn't need this degree of flexibility, so there would need to be some common | Of course many users wouldn't need this degree of flexibility, so there would need to be some common pre-made default selections for style/info combinations which are most commonly requested. Furthermore background images could be shared between users. | ||
... if a users feels like having a total mess of a sig pic where every single character is done in a different font type, colour and size... why not let him do it? ... | ... if a users feels like having a total mess of a sig pic where every single character is done in a different font type, colour and size... why not let him do it? ... | ||
| Line 42: | Line 42: | ||
* The sig server has it's own user database | * The sig server has it's own user database | ||
* Users can configure the signature pics via a web interface of the sig server | * Users can configure the signature pics via a web interface of the sig server | ||
* The sig server provides an | * The sig server provides an URL which returns the sig pic | ||
* When the URL is requested the sig server will look for a locally cached pic or cached AniDB status information for the user and will either return the cached pic, a new pic created with the cached information or will issue an http request to retrieve the needed stats via as XML and then create the pic. | * When the URL is requested the sig server will look for a locally cached pic or cached AniDB status information for the user and will either return the cached pic, a new pic created with the cached information or will issue an http request to retrieve the needed stats via as XML and then create the pic. | ||
| Line 65: | Line 65: | ||
** Just to be clear - You will NOT have access to the AniDB database via SQL. As such you're free to come up with your own database schema for the information you need to store. All AniDB data you need will be available as XML via HTTP GET requests. | ** Just to be clear - You will NOT have access to the AniDB database via SQL. As such you're free to come up with your own database schema for the information you need to store. All AniDB data you need will be available as XML via HTTP GET requests. | ||
** The SigServer will require a separate signup and will not make use of the AniDB user account data. | ** The SigServer will require a separate signup and will not make use of the AniDB user account data. | ||
* Currently the server only runs PHP4 [http://sig.anidb.info/phptest.php | * Currently the server only runs PHP4 [http://sig.anidb.info/phptest.php PHP Info], but PHP5 could be installed. | ||
==Data Retrieval== | ==Data Retrieval== | ||
| Line 71: | Line 71: | ||
Here are some examples. | Here are some examples. | ||
CAUTION! - Don't access these | CAUTION! - Don't access these URLs more than once or twice a day or you will get yourself an automatic 24h ban! | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=file http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=file] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=file http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=file] | ||
:* latest files added to | :* latest files added to MyList | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=anime http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=anime] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=anime http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=anime] | ||
:* latest | :* latest anime for which files were added to MyList (each anime is listed only once). | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=watched http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=watched] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=watched http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=watched] | ||
| Line 107: | Line 107: | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32 http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32 http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32] | ||
:* statistics for an anime, together with user | :* statistics for an anime, together with user MyList info | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32&gid=41 http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32&gid=41] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32&gid=41 http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=animestat&aid=1&uid=32&gid=41] | ||
:* statistics for an anime, together with user | :* statistics for an anime, together with user MyList and group info | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidbstat http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidbstat] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidbstat http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidbstat] | ||
:* global | :* global AniDB statistics | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=file http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=file] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=file http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=file] | ||
:* latest files added to | :* latest files added to AniDB | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=anime http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=anime] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=anime http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=anime] | ||
:* latest animes for which files were added to | :* latest animes for which files were added to AniDB (each anime is listed only once). | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=review http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=review] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=review http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=review] | ||
:* latest reviews added to | :* latest reviews added to AniDB | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=recs http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=recs] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=recs http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=anidblatest&list=recs] | ||
:* latest recommendations added to | :* latest recommendations added to AniDB | ||
* ... lot's more to be added | * ... lot's more to be added on request | ||
The | The MyList export documentation may be helpful in understanding the meaning of the different fields in the XML replies: [[MyList export template guidelines]] | ||
=== Feature Requests === | === Feature Requests === | ||
| Line 147: | Line 147: | ||
To parse the XML, standard php-commands can be used. | To parse the XML, standard php-commands can be used. | ||
A working example for xml.xml with the output array stack(): | A working example for <tt>xml.xml</tt> with the output array stack(): | ||
{| width="70%" | {| width="70%" | ||
|<pre><nowiki> | |<pre><nowiki> | ||