Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

RFFI Rugby

 [1/2] from: maarten::koopmans::surfnet::nl at: 11-Mar-2003 21:03


RFFI = Request For Feature Input Anyone? --Maarten

 [2/2] from: jvargas:whywire at: 12-Mar-2003 19:35


Marteen, Besides multiple interfaces support I like to see Access Control Lists or Realms. My idea is that if you have users with different levels of access they get a different set of functions that they can call get-rugby-service. This is more secure than implementing access control within the functions, and has the side effect of not exposing all the functionality with one call. I imagine at least three levels, and had calls like this: ; This context gives access to all public functions on the server ; This functions work on data and don't change the behavior of the server all-users: context get-rugby-service http://broker.domain.dom ; This context gives access to administrative functions on the server ; This functions work on changing parameters associated with the public ; functions admin-users: context get-rugby-service http://admin:[pass--broker--domain--dom] ; This context gives access to root user on the server. This is for changes ; related to the server itself. Stop/Start/Restart, Mobile-code and exchange of ; encryption keys come to mind. root-users: context get-rugby-service http://root:[pass--broker--domain--dom] I am not sure if embbeding the user and password is the best, but at least if follows the URI standards. Thats all for now I will keep thinking on how to improve rugby, but for the moment it rocks, and with your new experimental release of multiple interfaces address even more. Thanks, Jaime On Tuesday, March 11, 2003, at 03:03 PM, Maarten Koopmans wrote: