UDP API DEV: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 2: Line 2:


'''[[UDP_API_Definition|UDP API]] DEVELOPMENT'''
'''[[UDP_API_Definition|UDP API]] DEVELOPMENT'''
* add feature requests here
 
* feel free to edit / comment / whatever
Please use the tracker for all feature requests and bug reports: http://tracker.anidb.net
 
This page is for laying out larger (or radical) additions / changes to the UDP API using the same format and style as the API documentation. This makes it easy to compare different solutions and to copy over changes to the documentation when finally implemented. Tracker items should suffice for minor requests and bug reports.
 
Feel free to edit / comment / whatever.
 


== Data Commands ==
== Data Commands ==
Line 211: Line 216:
::That's really not wanted usage for this api. Have you thought about the possibility to use mylist export? You know you can make you own export template and get all the info you want at once? A command that query all changes (lids) within the last 2/3 months (or even weeks) is not going to be added. --[[User:Epoximator|Epoximator]] 12:36, 25 June 2006 (UTC)
::That's really not wanted usage for this api. Have you thought about the possibility to use mylist export? You know you can make you own export template and get all the info you want at once? A command that query all changes (lids) within the last 2/3 months (or even weeks) is not going to be added. --[[User:Epoximator|Epoximator]] 12:36, 25 June 2006 (UTC)


== Web Service API ==
 
== Other ==
=== Web Service API ===


I think most of the UDP API funcionality could be exposed as a web service. Not only it would  make client programming simpler but could also solve some NAT/Proxy/Firewall UDP problems. This web service would only provide query capabilities, since callbacks (required for notifications) in web services still pose some problems. --[[User:Jassuncao|Jassuncao]] 08:43, 20 September 2006 (UTC)
I think most of the UDP API funcionality could be exposed as a web service. Not only it would  make client programming simpler but could also solve some NAT/Proxy/Firewall UDP problems. This web service would only provide query capabilities, since callbacks (required for notifications) in web services still pose some problems. --[[User:Jassuncao|Jassuncao]] 08:43, 20 September 2006 (UTC)
Line 218: Line 225:


::Since this is not the right place to start a flame war I will not comment.
::Since this is not the right place to start a flame war I will not comment.
=== HTTP/XML API===
A complemental HTTP/XML API has been suggested (and approved). See http://forum.anidb.net/viewtopic.php?f=11&t=6871


[[Category:Development]]
[[Category:Development]]
[[Category:UDP]]
[[Category:UDP]]