will wrote:moltra wrote:1. you mean returnedSize or requestedSize.
2. Yes I will change it to title.
3. Yes I removed that so it would be easier in the future. I actually removed it in the drupal database
4. It will be easy to add the title search. I just need to enter one line of sql. I already have it setup so that you can search region, title at the same time. and all searches are wildcard type searchs
I also need to setup the region as a request. Should take a few minutes, will get it today sometime. I was up all night working and will probably lay down in a little bit.
Yes I have thought about the custom urls and I think know how to do it. The thing I am trying to figure out is how to get them from the database. Since it is user specific, need user/password controls?
I am also still fighting to get the xml to work right.
1) Keep it as returnedSize
4) Search by plugin (not title, assume that was a typo)
Custom urls/templates: Why would it be user specific? The idea would be that you would have none, one or multiple per plugin that describe in a form usable by clients, on how to build urls from the minimal amount of user input.
The way I was thinking, the user would log in serviidb and go to say picasa and they would enter their username for picasa and folder it they wanted a specific folder returned only.
Now to get this via the API it would have to be saved. That way it could be retrieved by the API for entry by serviidroid.
Or the API could return a generic url where the custom URL was complete, except for replacing one word in the URL with the username, or file name. The client could replace that word. This way the user never has to create and save a custom url on serviidb
Either or both is fine with me.
Hey, in the api there is also a client parameter, that way we can see what client is doing what and how often. Plus I will be logging response time with date/time and client so i can make sure that the API is not slowing the clients down.
I am going to be adding one more field to the results returned that is the nid (node id). If I can get the clients to send this back when the media source is added to serviio, I can track "installs" of the sources. I have not started writing that API yet, but it should be a straight put command with 2 parameters, client and nid.