From: Mike B. <mi...@ze...> - 2010-11-09 01:30:39
|
On Mon, 8 Nov 2010 20:25:03 -0500 Mike Blumenkrantz <mi...@ze...> wrote: > On Tue, 9 Nov 2010 09:39:58 +0900 > Carsten Haitzler (The Rasterman) <ra...@ra...> wrote: > > > New thread. exchange. it's in bad shape. > > > > what do we do? as such right now we need to kill off what is there. i would > > want to focus on it being a code-side accessible service. not web page. that > > means that e's wallpaper/theme etc. dialogs access it. if you want to > > upload - lets make a client that lets you upload/contribute. lets remove > > the web part and just focus on the "extend e/efl content into web hosted > > and shared content". this makes it simpler, gets rid of the "framework" and > > leads to a nice http+text or soap etc. etc. server and everything done > > nicely via that and lib exchange + an app front end. some stand-alone elm > > based apps to do the upload + listing of content and download for now would > > be a good start. > > > Gonna go ahead and promote my new lib, Azy, here, because it does xmlrpc and > jsonrpc very easily (and async without threads!) and uses EFL, so it will work > on phones and whatnot client side. It can do both client and server > connections, and all the server methods are written using a simple C-like > parsed language which looks something like this: > > boolean rastersrpcfunction(int an_int, string a_string) > <% > printf("%i, %s\n", an_int, a_string); > return EINA_TRUE; > %> I forgot to mention that the parser also generates client side bindings for all server methods, so that the above method can be called by a client running rastersrpcfunction(5, "ilikestuff") once connected. -- Mike Blumenkrantz Zentific: Our boolean values are huge. |