[dev] vfs/ftp

[Marko]

yes i see what both you and chuck mean, but i still see an extra part missing 
which would do the setting up of any RPC protocol between two hordes.

it shouldn't be a fixed thing (setting up backends, conf etc), but more like
typing in a url and getting info on what the other horde can offer. ie. i don't
want to set up a calendar which is only fixed on talking to a remote horde using
a set up RPC backend. but something more user level - maybe in options i type in
a url of a remote horde and i see that i am allowed to use it's calendar,
selecting it, it appears in my calendar list.

or maybe in the admin of a horde several remote hordes could be specified which
would propagate their "offerings" to respective users/groups in their options.

so we'd still need something to handle this, no? even if it is using RPC as as
the underlying protocol... something like a horde handshake.

m.



Quoting Jan Schneider <jan@horde.org>:

> Zitat von Marko <marko@oblo.com>:
> 
> > not talking about summaries... i want to be able to share a calendar for
> > example, like i do now with other users on a horde setup, but with a
> > specific
> > other horde remotely and a user/group within that horde. and that
> > user/group
> > should be able to use that calendar transparently on their horde without
> > realising that it is actually sitting on a completely different server,
> > architecture, backend and only talking through some horde api calls.
> 
> I know what you were talking about. The summaries are only an example usage
> for the Horde RPC server/client. All you need to do (a bit optimistic
> perhaps) is to write a backend driver that works with the RPC client instead
> of say sql or mcal.
> 
> Jan.
> 
> --
> http://www.horde.org - The Horde Project
> http://www.ammma.de - discover your knowledge
> http://www.tip4all.de - Deine private Tippgemeinschaft
> 
> --
> Horde developers mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe@lists.horde.org
>