Re: [E-devel] state of ecore_dbus

2007-03-02 Thread The Rasterman
On Mon, 26 Feb 2007 17:15:00 +0100 Hannes Janetzek [EMAIL PROTECTED] babbled:

 Hi,
 I have started to make a module for e17 to control NetwokManager. I

WOOHOO! :)

 would like to use ecore_dbus for that, but it seems
 ecore_dbus_message_new_method_return doesn't work correctly. (I need
 this function since NetworkManager gathers user preferences from the
 client.) so when the return message is sent a
 ECORE_DBUS_EVENT_SERVER_DEL is produced on the sending side and a dbus
 timeout is recieved on the other (method calling side). 
 Am i doing soemthing wrong or is this the expected behavior atm? If so,
 do you have any hints what needs to be
 done to fix this?

not sure. ecore_dbus right now is not perfect - it's a from-principles
implementation of dbus protocol handling. it's still a bit up in the air.

 Regards,
 Hannes 
 
 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 enlightenment-devel mailing list
 enlightenment-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
 


-- 
- Codito, ergo sum - I code, therefore I am --
The Rasterman (Carsten Haitzler)[EMAIL PROTECTED]
裸好多
Tokyo, Japan (東京 日本)

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] state of ecore_dbus

2007-03-02 Thread The Rasterman
On Mon, 26 Feb 2007 13:33:11 -0600 Brian Mattern [EMAIL PROTECTED]
babbled:

 On Mon, Feb 26, 2007 at 08:10:48PM +0100, Sebastian Dransfeld wrote:
  Hannes Janetzek wrote:
   Hi,
   I have started to make a module for e17 to control NetwokManager. I
   would like to use ecore_dbus for that, but it seems
   ecore_dbus_message_new_method_return doesn't work correctly. (I need
   this function since NetworkManager gathers user preferences from the
   client.) so when the return message is sent a
   ECORE_DBUS_EVENT_SERVER_DEL is produced on the sending side and a dbus
   timeout is recieved on the other (method calling side). 
   Am i doing soemthing wrong or is this the expected behavior atm? If so,
   do you have any hints what needs to be
   done to fix this?
  
  Can you show some sample code? And check whether the dbus samples work.
  
  Sebastian
  
 
 The ecore_dbus_receive_test sample (in test/orig/ecore) doesn't actually
 send a reply. (Which would definitely cause the other end to eventually
 time out if it was expecting one). So, the method_return code probably
 has never been tested.
 
 Ecore_DBus is pretty young, and still missing some functionality. If you
 want to use it, you'll probably want to get familiar with its code so
 you can fix any bugs you run across and implement any missing
 functionality you need.
 
 As an alternative approach, I started a simple wrapper around dbus that
 hooks it into e's main loop. It provides a few convenience functions for
 setting up method receivers, etc, but requires using the lowlevel
 libdbus api for many things. 
 
 I probably won't have any time in the next couple months to work on
 this, so I've put up a tarball at:
   http://rephorm.com/files/code/e_dbus-0.0.1.tar.gz
 
 It includes part of the hal dbus api wrapped up into a lib and a demo
 ewl app using that.
 
 I would love to see someone take this and ecore_dbus and do some
 benchmarks. In my opinion, unless we can get some significant
 speed/memory gain from ecore_dbus as opposed to libdbus, I don't see the
 point of having an independant implementation of the spec.

i don't think there would be a problem with ecore_dbus using libdbus - maybe
just be a thin namespace wrapper on top of the libdbus api and otherwise do all
the buffering/fd handler etc. hooks for you.

 rephorm
 
 
 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 enlightenment-devel mailing list
 enlightenment-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
 


-- 
- Codito, ergo sum - I code, therefore I am --
The Rasterman (Carsten Haitzler)[EMAIL PROTECTED]
裸好多
Tokyo, Japan (東京 日本)

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] state of ecore_dbus

2007-02-27 Thread Hannes Janetzek
Am Mon, 26 Feb 2007 13:33:11 -0600
schrieb Brian Mattern [EMAIL PROTECTED]:

 On Mon, Feb 26, 2007 at 08:10:48PM +0100, Sebastian Dransfeld wrote:
  Hannes Janetzek wrote:
   Hi,
   I have started to make a module for e17 to control NetwokManager.
   I would like to use ecore_dbus for that, but it seems
   ecore_dbus_message_new_method_return doesn't work correctly. (I
   need this function since NetworkManager gathers user preferences
   from the client.) so when the return message is sent a
   ECORE_DBUS_EVENT_SERVER_DEL is produced on the sending side and a
   dbus timeout is recieved on the other (method calling side). 
   Am i doing soemthing wrong or is this the expected behavior atm?
   If so, do you have any hints what needs to be
   done to fix this?
  
  Can you show some sample code? And check whether the dbus samples
  work.
  
  Sebastian
  
 
 The ecore_dbus_receive_test sample (in test/orig/ecore) doesn't
 actually send a reply. (Which would definitely cause the other end to
 eventually time out if it was expecting one). So, the method_return
 code probably has never been tested.
 
 Ecore_DBus is pretty young, and still missing some functionality. If
 you want to use it, you'll probably want to get familiar with its
 code so you can fix any bugs you run across and implement any missing
 functionality you need.

ok. i invested already a few hours staring at the code of
ecore_dbus but couldn't find where the problem is exactly. As far as i
can interpret dbus-monitor's output the reply message is not even sent,
but dbus(the daemon) knows that we sent something, since
otherwise the timeout is not recieved.  
 
 As an alternative approach, I started a simple wrapper around dbus
 that hooks it into e's main loop. It provides a few convenience
 functions for setting up method receivers, etc, but requires using
 the lowlevel libdbus api for many things. 

thanks, i'll have a look at this one. using low-level dbus makes porting
simple (ie. just copy n paste). 
 
 I probably won't have any time in the next couple months to work on
 this, so I've put up a tarball at:
   http://rephorm.com/files/code/e_dbus-0.0.1.tar.gz
 
 It includes part of the hal dbus api wrapped up into a lib and a demo
 ewl app using that.
 
 I would love to see someone take this and ecore_dbus and do some
 benchmarks. In my opinion, unless we can get some significant
 speed/memory gain from ecore_dbus as opposed to libdbus, I don't see
 the point of having an independant implementation of the spec.
 

memory and performance wise there is probably not much to gain, but
I have to say that the api of ecore_dbus is really handy.  I would like
to use it for stuff i write from scratch. but anyway, it would probably
be possible to have the same api with your wrapper.

Regards,
Hannes



 rephorm
 
 
 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to
 share your opinions on IT  business topics through brief surveys-and
 earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___ enlightenment-devel
 mailing list enlightenment-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


[E-devel] state of ecore_dbus

2007-02-26 Thread Hannes Janetzek
Hi,
I have started to make a module for e17 to control NetwokManager. I
would like to use ecore_dbus for that, but it seems
ecore_dbus_message_new_method_return doesn't work correctly. (I need
this function since NetworkManager gathers user preferences from the
client.) so when the return message is sent a
ECORE_DBUS_EVENT_SERVER_DEL is produced on the sending side and a dbus
timeout is recieved on the other (method calling side). 
Am i doing soemthing wrong or is this the expected behavior atm? If so,
do you have any hints what needs to be
done to fix this?

Regards,
Hannes 

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] state of ecore_dbus

2007-02-26 Thread Sebastian Dransfeld
Hannes Janetzek wrote:
 Hi,
 I have started to make a module for e17 to control NetwokManager. I
 would like to use ecore_dbus for that, but it seems
 ecore_dbus_message_new_method_return doesn't work correctly. (I need
 this function since NetworkManager gathers user preferences from the
 client.) so when the return message is sent a
 ECORE_DBUS_EVENT_SERVER_DEL is produced on the sending side and a dbus
 timeout is recieved on the other (method calling side). 
 Am i doing soemthing wrong or is this the expected behavior atm? If so,
 do you have any hints what needs to be
 done to fix this?

Can you show some sample code? And check whether the dbus samples work.

Sebastian

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


Re: [E-devel] state of ecore_dbus

2007-02-26 Thread Brian Mattern
On Mon, Feb 26, 2007 at 08:10:48PM +0100, Sebastian Dransfeld wrote:
 Hannes Janetzek wrote:
  Hi,
  I have started to make a module for e17 to control NetwokManager. I
  would like to use ecore_dbus for that, but it seems
  ecore_dbus_message_new_method_return doesn't work correctly. (I need
  this function since NetworkManager gathers user preferences from the
  client.) so when the return message is sent a
  ECORE_DBUS_EVENT_SERVER_DEL is produced on the sending side and a dbus
  timeout is recieved on the other (method calling side). 
  Am i doing soemthing wrong or is this the expected behavior atm? If so,
  do you have any hints what needs to be
  done to fix this?
 
 Can you show some sample code? And check whether the dbus samples work.
 
 Sebastian
 

The ecore_dbus_receive_test sample (in test/orig/ecore) doesn't actually
send a reply. (Which would definitely cause the other end to eventually
time out if it was expecting one). So, the method_return code probably
has never been tested.

Ecore_DBus is pretty young, and still missing some functionality. If you
want to use it, you'll probably want to get familiar with its code so
you can fix any bugs you run across and implement any missing
functionality you need.

As an alternative approach, I started a simple wrapper around dbus that
hooks it into e's main loop. It provides a few convenience functions for
setting up method receivers, etc, but requires using the lowlevel
libdbus api for many things. 

I probably won't have any time in the next couple months to work on
this, so I've put up a tarball at:
  http://rephorm.com/files/code/e_dbus-0.0.1.tar.gz

It includes part of the hal dbus api wrapped up into a lib and a demo
ewl app using that.

I would love to see someone take this and ecore_dbus and do some
benchmarks. In my opinion, unless we can get some significant
speed/memory gain from ecore_dbus as opposed to libdbus, I don't see the
point of having an independant implementation of the spec.

rephorm


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel