Changes

Jump to navigation Jump to search
Line 54: Line 54:  
* '''[Code-Requirements] Client XO wishes to access the share of Server XO'''
 
* '''[Code-Requirements] Client XO wishes to access the share of Server XO'''
 
** Mapping a neighborhood-buddy to its IP Address
 
** Mapping a neighborhood-buddy to its IP Address
*** Luckily, in the method "def __buddy_updated_cb(self, account, contact_id, properties):" in "jarabe/model/neighborhood.py", there is the "properties['ip4-address']", which contains the IP address of the buddy. All that is needed is to persist in the "BaseBuddyModel" in "jarabe/model/buddy.py".  
+
*** Luckily, in the method "def __buddy_updated_cb(self, account, contact_id, properties):" in "jarabe/model/neighborhood.py", there is the "properties['ip4-address']", which contains the IP address of the buddy. All that is needed is to persist it in the "BaseBuddyModel" in "jarabe/model/buddy.py".  
 
*** When the client clicks on "Access Share" on the buddy, this IP Address can be easily retreived, and the URI formed "https://<IP Address>/webdav"
 
*** When the client clicks on "Access Share" on the buddy, this IP Address can be easily retreived, and the URI formed "https://<IP Address>/webdav"
 
** Opening up the server's webdav
 
** Opening up the server's webdav
 
*** The generated URI would be passed to the "Browse" activity; and thereafter, "Browse" would take over.
 
*** The generated URI would be passed to the "Browse" activity; and thereafter, "Browse" would take over.
 
** A minor query, regarding the last point, has been posted at http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036425.html
 
** A minor query, regarding the last point, has been posted at http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036425.html
  −
  −
      
== [ARCHIVE] Possible options ==
 
== [ARCHIVE] Possible options ==
525

edits

Navigation menu