Thiago Arrais wrote:
I would agree that on a LAN scenario the centralized architecture
would be much easier to set up, manage and even more efficient. The
main concern here wouldn't be usage over a LAN (although it is
obviously possible to do), but over worse-connected hosts through the
Internet, like the other ones you cited (DSL and the likes).
This is actually a reality at my place. People can pay for a DSL or
cable connection, greater bandwidth connections prices are
prohibitive.
One of the things I had played around with but never completed was using
Jabber (Open-Source XML-based Instant Messaging) for darcs
communications. The design plan was to create a simple Jabber "bot"
that would communicate with your local repositories and a simple Jabber
client that could talk to others' repository bots (and would also
provide the overloading for $DARCS_APPLY_JABBER).
Once that was complete it would be cool to see plugins written for
Jabber clients to present a GUI view.
I think that IM is a good model of how a distributed project (such as
you seem to be describing, Thiago) would work: push/pull from
"[EMAIL PROTECTED]'s thisProject repository". The workflow would
work pretty well coupled as well, since you would probably be using IM
to coordinate design efforts anyway.
Sadly I don't have much in the way of completed code to show, just yet,
as classes keep me busy enough...
--
--Max Battcher--
http://www.worldmaker.net/
"History bleeds for tomorrow / for us to realize and never more follow
blind" --Machinae Supremacy, Deus Ex Machinae, Title Track
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
