2014-02-16, 23:51
@Lunatixz : JSON is universal but absolutely not the way to access it ...
And this is the service part that crashes on XBMC. Again I repeat on Windows what is known to causes problem is Keep Alive on HTTP.
So there's nothing wrong with translations
I just give you fact, I don't know how Python access JSON, it may be by internal bindings, HTTP , TCP or Websockets all those works completely differently have more or less problems.
The major problem being HTTP with libmicrohttp that is outdated.
Just read : https://github.com/xbmc/xbmc/pull/2262 for example.
So I'm sorry but I do exactly know what I'm talking about despite your pre edit message
I have 2 years experience with different Xbmc remoting and have some PR included in XBMC so I do also know XBMC code base ....
And about the feature as explained earlier I can't since then Yatse would no more works.
@MilhouseVH : I never said XBMC is bad or I would not use it, I just say that it has numerous bugs and some well known not addressed by not enough time by the team. I'll let you see the PR linked above for exemple, or the problems told by Lunatixz
Don't try to change my words
About the rest, you remind me all those guys that are persuaded that you need to use task killer in Android and that apps must have exit buttons, despite the Android team telling everywhere no you should not this is not how android works in the end you'll use much more battery on well written apps.
Again I repeat I make choice based on experience and real numbers, you tells me it's wrong just because you are persuaded it's wrong but without any indicator or proof or knowledge to argue on it.
Now you tell me you could use 1/10 of notification and 9/10 pulling, and use tons of different hacks for each Xbmc version and for users of widgets / notification find something else ...
Now I will make it really clear, I do know what I do, I do choose what I do with Yatse (and if you hadn't look at Xbmc logs you'd never be aware of that, and never complained before since all works perfectly.)
So for the last time Yatse is efficient and it's proven by users feedback and numbers, show me a proof it's not ..
And for the last time : Please stop making people think that Yatse is bad and that what is used should not be used.
If you don't like how it works just do not use it.
And this is the service part that crashes on XBMC. Again I repeat on Windows what is known to causes problem is Keep Alive on HTTP.
So there's nothing wrong with translations
I just give you fact, I don't know how Python access JSON, it may be by internal bindings, HTTP , TCP or Websockets all those works completely differently have more or less problems.The major problem being HTTP with libmicrohttp that is outdated.
Just read : https://github.com/xbmc/xbmc/pull/2262 for example.
So I'm sorry but I do exactly know what I'm talking about despite your pre edit message
I have 2 years experience with different Xbmc remoting and have some PR included in XBMC so I do also know XBMC code base ....And about the feature as explained earlier I can't since then Yatse would no more works.
@MilhouseVH : I never said XBMC is bad or I would not use it, I just say that it has numerous bugs and some well known not addressed by not enough time by the team. I'll let you see the PR linked above for exemple, or the problems told by Lunatixz
Don't try to change my words
About the rest, you remind me all those guys that are persuaded that you need to use task killer in Android and that apps must have exit buttons, despite the Android team telling everywhere no you should not this is not how android works in the end you'll use much more battery on well written apps.
Again I repeat I make choice based on experience and real numbers, you tells me it's wrong just because you are persuaded it's wrong but without any indicator or proof or knowledge to argue on it.
Now you tell me you could use 1/10 of notification and 9/10 pulling, and use tons of different hacks for each Xbmc version and for users of widgets / notification find something else ...
Now I will make it really clear, I do know what I do, I do choose what I do with Yatse (and if you hadn't look at Xbmc logs you'd never be aware of that, and never complained before since all works perfectly.)
So for the last time Yatse is efficient and it's proven by users feedback and numbers, show me a proof it's not ..
And for the last time : Please stop making people think that Yatse is bad and that what is used should not be used.
If you don't like how it works just do not use it.
