Ah ok that must have been my confusion too then.
In the current structure (mirroring the java's structure) i'm
implimenting a /gadgets/socialdata interface where it now retrieves the
social information ... Which is where that part of my reasoning and
assumptions was/were based on.
I'm under the impression we don't actually have a REST interface as of
yet, so i presumed this will stick around for a little bit longer..
Hence my desire to put the current /gadgets/socialdata under /social for
now, until we have a proper REST solution in place.
The main reason, is pretty much how i started all of this, it's a mess
in a lot of ways to mix these 2 things in the PHP code .. and the main
reason you were not able to put them under 2 seperate url's (/gadgets
and /social) was due to the requirement to have it all be one server /
project.... Which i believe now has been agreed on shouldn't be a
requirement anymore? (due to the rest and gadget stuff being split
anyhow)
-- Chris
On Thu, 2008-04-03 at 12:52 +0200, Cassie wrote:
> I'm sorry Chris but I didn't quite catch the difference between what
> goes under /social and what goes under /rest..
>
> Long term there would only be one server/code directory for serving
> social data. This would be the restful api server. Then, the
> javascript part of opensocial would talk restful wire format to that
> server. So, why do we need two directories when its all going to be
> the same thing? (I'm probably just missing something)
>
> Thanks.
>
> - Cassie
