Argent Stonecutter wrote: > On 2010-03-17, at 10:21, Dzonatas Sol wrote: >> Ricky wrote: >>> So far, barring any LL concepts, we have (as far as I know so far!) >>> two designs of plugin system: >>> 1: Socket-based plugins - as�suggested�by Morgaine. >>> 2: D-Bus or similar existing IPC tool. >>> 3: C++ Dynamically Shared Objects - my suggestion. >> >> 4. REST/HTTP > > That's just a specific design for category 1. > > REST doesn't need to be based on sockets. It's just commonly used with sockets/HTTP. REST is not the transport layer.
Here is the architecture so it can be better understood: http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm HTTP could be said to be a specific design category, but not REST. D-Bus uses XML/socket encapsulation, and is slower (due to conversions). You could say D-Bus is a specific design category for 1, also. Design should also include if the plugin/scripts are in separate processes. #3 doesn't allow that easily until made portable. REST/HTTP is already portable. D-Bus is somewhat portable, yet harder to interface. _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
