JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32) +--- Forum: Kodi Application (https://forum.kodi.tv/forumdisplay.php?fid=93) +---- Forum: JSON-RPC (https://forum.kodi.tv/forumdisplay.php?fid=174) +---- Thread: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC (/showthread.php?tid=68263) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Tolriq - 2012-07-10 Well the point is that you can't pass json directly to /image you need to urlencode it again. This lead to url like : http://192.168.0.11:90/image/image://Z%253a%255cFilms%255cL%2527Enqu%25c3%25aate%2520-%2520The%2520International%2520(The%2520International)%2520%255b720p%255d%2520%255b2009%255d%255cmovie.tbn urlencoding the % to %25 is really not needed but without it doesn't work. At the moment the option to get image is : - http://xxx:yy/image/ urlencode the json image path - http://xxx:yy/vfs/ json image path without "image://" (no url encode) Seems to be the opposite from what jmarshall says in the last post. For me the /image should not need the second url encode or the json should be url encoded but there's something not logical. Edit : After more tests /vfs/image:// works with correct urlencoding. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-07-10 OK I was wrong in my previous statement. You have to URL-encode the thumbnail/fanart URL again BUT you have to URL-encode the whole URL not just what comes after "image://" so the above URL you posted is invalid because it contains "://" unencoded (which is reserved for appearing after the protocol). That's also probably why it didn't work for you over VFS. So what you should do is grab the whole URL JSON-RPC provides, URL encode it and either append it to "http://<ip>:<port>/vfs/" or to "http://<ip>:<port>/image/". As an example JSON-RPC provides Code: image://H%3a%5c12%20Rounds%5c12%20Rounds.tbn Code: image%3A%2F%2FH%253a%255c12%2520Rounds%255c12%2520Rounds.tbn Code: http://<ip>:<port>/vfs/image%3A%2F%2FH%253a%255c12%2520Rounds%255c12%2520Rounds.tbn Code: http://<ip>:<port>/image/image%3A%2F%2FH%253a%255c12%2520Rounds%255c12%2520Rounds.tbn When using the image/ handler you can also just take whatever JSON-RPC provides, remove the "image://" from the beginning of the URL and append the rest to http://<ip>:<port>/image/ which would lead to Code: http://<ip>:<port>/image/H%3a%5c12%20Rounds%5c12%20Rounds.tbn RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Tolriq - 2012-07-10 Hum ok that seems more logical And effectively works like that. (Was also the reason about problem of /vfs) I was just a little lost with docs in this post that may not be always up2date. Thanks for clarification. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-07-11 Wednesday, July 11th 2012: Commit: c924204d75d511489972
RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Millencolin007 - 2012-07-15 (2012-07-11, 11:24)Montellese Wrote: Wednesday, July 11th 2012: The virtual keyboard is often used to edit an existing text. Would it be possible to include this text in the Input.OnInputRequested notification? RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-07-15 This has already been requested but after I added the new features. It will be added ASAP. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Millencolin007 - 2012-07-15 Requesting song details does not return the artistid in the current git builds. In eden the same request works ok. Request Code: { Response Code: { RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - jmarshall - 2012-07-15 This is a known issue - there's a pull request for it here: https://github.com/xbmc/xbmc/pull/1117 RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Mizaki - 2012-07-21 Can't seem to make FR on trac any more so I'll put it here for now. If I'm supposed to do something else let me know Notification for library clean - start and stop Notification for library export - start and stop This may be a silly question/idea but is it possible to provide a UPnP link for library items? I'm thinking with the headless it might be useful. You'd probably want to use a proper UPnP program to browse the library but if possible it might be useful. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-07-22 Yeah feature requests have been disabled on trac. You can create an issue and label it as "Feature Request" on my github issues page (see https://github.com/Montellese/xbmc/issues) if you want. What do you mean with UPnP link? I never really used UPnP so far and AFAIK the UPnP implementation in XBMC is being reworked as part of alcohecas GSoC project. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Millencolin007 - 2012-07-22 Such a UPnP link would be fantastic since it would let us stream files and more importantly seek inside a file from a remote location using an url provided by json-rpc, something which does not work with the "vfs" url which is returned by Files.PrepareDownload (since it does ignore partial http requests) RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Mizaki - 2012-07-22 (2012-07-22, 11:39)Montellese Wrote: Yeah feature requests have been disabled on trac. You can create an issue and label it as "Feature Request" on my github issues page (see https://github.com/Montellese/xbmc/issues) if you want. I've added the FR to your issues. Shall I add the other outstanding ones or are they alright where they are? I'm somewhat in the dark about UPnP as well. Maybe Millencolin007 can explain things better. If I look at an item in Windows Media Player via UPnP I see the link: Code: http://xbmc:58520/%2525/%252Fmnt%252Fthings%252Ffilms%252F2%2520Fast%25202%2520Furious.avi?WMContentFeatures=DLNA.ORG_PN=AVI;DLNA.ORG_OP=01;DLNA.ORG_CI=0;DLNA.ORG_FLAGS=01000000000000000000000000000000&WMHME=1&WMQ=1&WMHMETitle=MgAgAEYAYQBzAHQAIAAyACAARgB1AHIAaQBvAHUAcwA= RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Millencolin007 - 2012-07-22 I am not familiar with the upnp protocol neither. I just had a look at a network trace myself. Streaming from one xbmc instance to another I get something like the following url. The problem is that the url is not persistent as it is not valid anymore when xbmc is restarted. Code: http://xbmc:55001/%2525/80D45637116C76376F873DC092217A23%252F12%2520-%2520Alain%2520Souchon%2520-%2520C'est%2520d%25C3%25A9j%25C3%25A0%2520%25C3%25A7a.mp3 BTW: I think that we already get a http url using json-rpc Files.PrepareDownload which could be used to send to a Upnp Renderer. The problem is that the xbmc webserver does not support partial http requests (whereas the upnp lib from xbmc does) which prevents seeking inside a file. RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - gertjanzwartjes - 2012-07-23 I was testing out pre-Frodo builds on OS X. I have a test library with ~900 (fake) movies in it. When I do a simple Code: VideoLibrary.GetMovies I saw some chatter in this topic about slow movie queries; is this a known issue still? The library + request works perfectly fine on both Dharma and Eden. Just wanted to check if I might be doing something stupid. Thanks guys, lot's of interesting and useful new stuff coming into the JSON-RPC interface for Frodo! Keep up the good work! RE: JSON-RPC (JSON Remote Procedure Call) interface protocol in development for XBMC - Montellese - 2012-07-23 There seems to be an issue with JSON-RPC and OSX but I have no clue what the problem is. I can only test on win32 and linux and at least on win32 JSON-RPC requests are faster in Frodo than they are in Eden. Haven't done any comparisons on linux. Furthermore there's no platform specific code in JSON-RPC so the only place where the problem could be located is the webserver. Will have to find someone on the team to help me debug this on OSX. |