[Cosmo-dev] Re: [Scooby-dev] Cosmo/Scooby Merge (Please read
mde at osafoundation.org
Fri Jul 14 12:28:14 PDT 2006
Actually, I didn't add this in my post because it seemed kind of
peripheral -- but since the Scooby frontend expects calendar event
objects in a pretty basic JSON format, it can consume calendar data from
any source that talks JSON.
It would be fairly easy to set up a thin proxying layer in the server
code to allow the Web client to grab JSON-formatted event info from
other sources (a remote Cosmo server might be a good place to start,
since it can already produce data in the right format).
Browser security prevents cross-domain XHR anyway, so requests to a
third party have to be proxied through the server. But the point is that
server-only or Web-client-only are both viable -- and that the data
source doesn't necessarily have to be CalDAV. As long as the client code
gets JSON-formatted objects, it's happy.
Brian Moseley wrote:
> On 7/14/06, Mikeal Rogers <mikeal at osafoundation.org> wrote:
>> One thing I wanted to bring up in this thread that I know was brought
>> up in one of our meetings but not on this thread is the viability of
>> running scooby without cosmo.
>> We are saying "you will still be able to cosmo without scooby" but
>> we're also saying "you won't be able to run scooby without cosmo".
>> If an outside developer wanted to use scooby without cosmo they would
>> have to re-implement all of scooby-interface.
>> I don't think this really matters, I certain don't see a problem with
>> it, but I wanted to make sure it was on the list.
> thanks. i too don't see it as an issue. as i mentioned before, our
> goals for scooby have changed over the last year. the architecture
> still allows for remote caldav access to be added back at a later
> date, when somebody needs it and is willing to maintain that code.
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
More information about the cosmo-dev