UDP API DEV: Difference between revisions

Bit 23 of <tt>acode</tt> (other name) will return language (official title) defined by <tt>lang</tt> where <tt>lang</tt> is a list of ISO 639-1 (?) codes (ie. <tt>de,en</tt>) ordered by preference. The first existing language will be returned. Applies to 24 (short name list) and 25 (synonym list) also.

:: well, for now i'm stuck with using wget anime page and than parse it, which is bad, cos theres many unneeded data => more traffic, and changes in html layout breaks compatibility( [[User:iSage|iSage]] 15:26, 27 July 2007 (UTC)

::: that's really bad. Why do you need to do that? What are you actually trying to do? Usually you'd use a mylist export as base, import it and only use the UDP API to update the data. [[User:Exp|Exp]] 17:59, 27 July 2007 (UTC)

:::: i'm need to get list of english names of all or some episodes of some specified anime. and mylist is not a solution. well, if this is considered as ripoff.. sorry then, i'll try to look for another solution  [[User:iSage|iSage]] 12:01, 28 July 2007 (UTC)

:::: web-site with file archive. triger is: add new anime (or edit)->assign AniDB id->cache episodes. hope you'll understand what i mean. [[User:iSage|iSage]] 06:58, 07 August 2007 (UTC)

::: what's the url of that page? [[User:Exp|Exp]] 08:28, 7 August 2007 (UTC)

Is the UDP API supporting other cheksum formats? Would it be too much trouble to implement i.e. md5 checksums?

: Needs db support, meaning exp has to grant it. --[[User:Epoximator|Epoximator]] 09:34, 9 July 2007 (UTC)

:: The real question is: Should we enforce uniqueness? It's not really a problem to implement and shouldn't lead to any problems. We have reports on uniqueness and there are atm 2x2 files with equal md5, which obviously is wrong (if you look at them). Constraints would just mean that DerIdiot doesn't have to go around and fix such entries from time to time. On the other hand, supporting md5 lookup for clients is hardly important and it'll only have a negative impact on performance (although probably unnoticeable). --[[User:Epoximator|Epoximator]] 12:02, 10 July 2007 (UTC)

::: Well, enforcing uniqueness in the db brings a slight performanc overhead with it, but as file additions are a very seldom event, that wouldn't hurt us. We'd have a couple of extra indicies on the file table, which would increase the storage requirements of the db. Though even that wouldn't be all that much. Supporting MD5 hashes on the UDP API might simplyfy the writing of very simple UDP clients, as there are easily available MD5 libraries for every programming language out there. For ed2k/md4 libs you might have to search for a bit. However, I think I wouldn't go as far as to enforce uniqueness for all our hashes (i.e. sha1 and tth). But it might be seriously worth considering enforcing MD5 uniqueness, especially if we might somday drop ed2k hashes. MD5 hashes would offer a nice fallback in such a case. [[User:Exp|Exp]] 08:52, 11 July 2007 (UTC)

* The lid of the added file is written in the reply only in case just one file was added. ''Actualy, if many files were added, there lid's would by useless to client because it wouldn't know the correspondence between lid's and files.''

** 128bit MD5 sum (raw, don't convert to hex) of api encryption key (api pass) is used as 128bit key.

*** if it is an ENCRYPT packet, disable encryption, discard the old key and iv and then process the ENCRYPT packet (thus reenabling encryption with a new key and iv)

Probably best implemented to behave just like the mylist commands.

* The state field provides information about the location and sharing state of a file in mylist.

   1 - on hdd - the file is stored on hdd (but is not shared)

   2 - on cd - the file is stored on cd

   3 - deleted - the file has been deleted or is not available for other reasons (i.e. reencoded)

It would probably be ok to add this, but note that it would be a hassle to fetch a complete mylist. I mean, you can already do this with your own list, but it takes a lot of time because of the datagram rate limit. (It would take at least 8h to fetch my own list). And that is usage we don't really want @ udp api. And a command that returns all the data at once will, of course, not be allowed. So, in other words, if you just want to check if a friend has a specific file, or what files per anime (multiple files found), then ok, but ''view and browse a specified user's list just as I can with the web interface'' is not likely to happen/be allowed.--[[User:Epoximator|Epoximator]] 11:29, 4 June 2006 (CEST)

:What I'm really interested in is maintaining local dbs of 3/4 user lists and having a client automatically update them every 2/3 weeks. We use this to coordinate information within our country regarding who has what =p. But what we're interested in is a way to be able to selectively retrieve the entire list by some index. OFcourse if its slow, then it makes sense to maintain it locally and just look for changes. The other thing I really want is to somehow retrieve with mylist file data (or user list file data), the date at which something was added to the list. (I understand this information exists). The idea here is we can locally query these lists for files added within the last 2/3 months. --[[User:path|path]] 11:53, 25 June 2006 (IST)

::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)

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)