mirror of
https://github.com/flynx/ImageGrid.git
synced 2025-10-29 18:30:09 +00:00
...
Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>
This commit is contained in:
parent
04a1802e1a
commit
520fe25116
@ -149,6 +149,17 @@ function(protocol, func){
|
|||||||
// - rpc (???)
|
// - rpc (???)
|
||||||
// - mq (???)
|
// - mq (???)
|
||||||
// - ...
|
// - ...
|
||||||
|
// XXX there seem to be two ways to go with peers:
|
||||||
|
// - proxy a set of actions...
|
||||||
|
// + simple
|
||||||
|
// - non-transparent in most cases...
|
||||||
|
// ...considering that all peer calls are async, making this
|
||||||
|
// transparent for actions that do not return a promise
|
||||||
|
// will be problematic...
|
||||||
|
// - custom actions that communicate with a peer...
|
||||||
|
// + no need to be compatible with existing actions
|
||||||
|
// - manual...
|
||||||
|
// Need to play around with use-cases and see what fits best...
|
||||||
// XXX should this do "sync"???
|
// XXX should this do "sync"???
|
||||||
// XXX should the couch api be implemented over this of independently???
|
// XXX should the couch api be implemented over this of independently???
|
||||||
var PeerActions = actions.Actions({
|
var PeerActions = actions.Actions({
|
||||||
@ -228,17 +239,6 @@ var PeerActions = actions.Actions({
|
|||||||
peerList: ['- System/Peer/',
|
peerList: ['- System/Peer/',
|
||||||
function(){ return Object.keys(this.__peers || {}) }],
|
function(){ return Object.keys(this.__peers || {}) }],
|
||||||
|
|
||||||
// XXX there seem to be two ways to go with peers:
|
|
||||||
// - proxy a set of actions...
|
|
||||||
// + simple
|
|
||||||
// - non-transparent in most cases...
|
|
||||||
// ...considering that all peer calls are async, making this
|
|
||||||
// transparent for actions that do not return a promise
|
|
||||||
// will be problematic...
|
|
||||||
// - custom actions that communicate with a peer...
|
|
||||||
// + no need to be compatible with existing actions
|
|
||||||
// - manual...
|
|
||||||
// Need to play around with use-cases and see what fits best...
|
|
||||||
// XXX do we need these???
|
// XXX do we need these???
|
||||||
// XXX format spec!!!
|
// XXX format spec!!!
|
||||||
peerSpec: ['- System/Peer/',
|
peerSpec: ['- System/Peer/',
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user