we still guess it was up and try to get its name, if not possible then
try to start it and then get is name.
another way to do it would be to always request start and just then
get its name and just then start to listen to NameOwnerChanged. But
the current way is good enough and should save some roundtrips for
good cases (server is up).
SVN revision: 40955
If there are no other main loop activity than a idlers and one idler
adds a timer, the new (and unique) timer would be ignored since it's
flagged as "just_added" and thus next iteration will not consider it,
possible entering an infinite wait as it could be the only thing to do
in main loop.
Antognolli found this nasty bug while handling timeout-and-die in
Ethumb, where the "disconnect" event is dispatched by EDBus from idler
and it was adding a timer to shutdown the daemon after a while without
clients.
By: Rafael Antognolli <antognolli@profusion.mobi>
SVN revision: 40923
ethumbd is a server waiting for requests of thumbnails via dbus. A client
library is also provided, avoiding dbus burocracy (and with an API similar
to ethumb).
SVN revision: 40899
the connection from the fork (the cserve connection). it won't catch
threads... most of the time, but i need something else for that i think.
SVN revision: 40869
The old way we could run endless with the following case:
int my_buggy_idler(void *data) {
ecore_idler_add(my_buggy_idler, NULL);
return 0;
}
since it would append to that list, then the list would never end.
Now we just dispatch up to the last know idler, then go back to
regular processing, if nothing happens we'll be back to dispatch
again.
I tested it here and works fine, but might show issues with ecore
enterers/exiters of some applications that rely on the old (broken)
behavior.
SVN revision: 40847
hence we must use closesocket() to close a socket instead of
close(). In addition, we should improve the closing of the
socket (see http://tangentsoft.net/wskfaq/newbie.html#howclose)
* use PIPE_FD_INVALID for invalid fd / socket
* use PIPE_FD_ERROR for invalid result when sending / receiving
data on fd / sockets
next step is to manage correctly errno on Windows with WSAGetLastError()
(see http://tangentsoft.net/wskfaq/articles/bsd-compatibility.html)
SVN revision: 40846
* fix the way AC_INIT macros are parsed to consider [] as well.
* set both LDFLAGS and CFLAGS on the libs I use and I know support -fvisibility=hidden.
SVN revision: 40838
The ethumb_generate() function now just returns 0 if there is already a
generation in progress (and in that case, the callback isn't called).
SVN revision: 40738