Charlie wrote:Also: ... JSONP ... mutter ... cross domain requests ... mutter ... mutter ...
Lol
Charlie wrote:Also: ... JSONP ... mutter ... cross domain requests ... mutter ... mutter ...
Charlie wrote:I briefly considered some sort of co-deployment so that a .NET client could fire up the server as a surrogate process. That would be possible but complicated and the deployment footprint would be untenable.
Yes, other clients can use the JSON translator, but I don't have much interest in other clients. I'm not going to stop people from writing them, but I don't plan to actively help them either.
I'm fine with an open source HTML client. As long as a good HTML in-browser client is written, I'll be very happy.
SpongeBob wrote:This sounds as if WMS has no interest in an iOS client, despite the fact that so many people are desperately waiting for it. Strange, isn't it?
oren wrote:... and anyone interested in programming an iOS KGS app now can.
KGS wrote:For people who are interested in the KGS JSON protocol, I've set up a mailing list at https://groups.google.com/forum/#!forum/kgs-client-coding
Please visit there and sign up if you have any interest in writing a client!
Drew wrote:It seems evident to me that the biggest threat to KGS' future is its own parent. Sad, really.