beagle r3797 - in branches/beagle-cutting-edge-branch: BeagleClient Util beagled tools
- From: dbera svn gnome org
- To: svn-commits-list gnome org
- Subject: beagle r3797 - in branches/beagle-cutting-edge-branch: BeagleClient Util beagled tools
- Date: Fri, 6 Jul 2007 07:42:59 +0100 (BST)
Author: dbera
Date: 2007-07-06 07:42:58 +0100 (Fri, 06 Jul 2007)
New Revision: 3797
ViewCVS link: http://svn.gnome.org/viewcvs/beagle?rev=3797&view=rev
Modified:
branches/beagle-cutting-edge-branch/BeagleClient/Client.cs
branches/beagle-cutting-edge-branch/BeagleClient/Message.cs
branches/beagle-cutting-edge-branch/Util/DateTimeUtil.cs
branches/beagle-cutting-edge-branch/beagled/BeagleDaemon.cs
branches/beagle-cutting-edge-branch/beagled/Server.cs
branches/beagle-cutting-edge-branch/tools/Query.cs
Log:
Make network querying work. Run beagled with --networked, add some host:port Neighbourhood beagle node via beagle-config (FSQ is enabled in Neighbourhood domain), run beagle-query with "--local no --network yes" and watch beagle return results over http.
Minor points to remember:
- beagled http listens on port 4000 (add 127.0.0.1:4000 as a node)
- beagle-query reads the list of remote nodes from config, hence it needs a valid beagle-storage directory. However, you can pass it any .beagle directory with a valid config/networking.xml (not necessary the one where beagled is running) and it will query over http (set --local no)
Note that I merely added the source files from GSoC06, making changes to the client and server logic. The actual networking logic is completely untouched - if there is some problem in them, may the force be with you.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]