Re: [Phli-developers] Backend/Frontend (was Re: Next real-world developer meeting)

[Johan V. <joh...@gm...>]

On 9/5/06, Andreas Sandberg <an...@sa...> wrote:
>
> On Mon, 4 Sep 2006, Johan Viklund wrote:
>
> >> Btw, I spoke to a guy at Update the other day. He was a bit interested in
> >> Phli and seems to have quite a few good ideas about GUI design. He
> >> suggested a few design changes to make the software perform better over
> >> slow links, e g modem or ADSL. The changes mainly involved making a more
> >> sophisticated server which does the resizing (to allow different
> >> thumbnail sizes or low-res images for previews) and caches the results.
> >> What do you think about this? Should we just go ahead with the current
> >> plans and make sure that backend - frontend separation is good enough to
> >> add something like this in the future? Or should we try to implement
> >> something like this in the first release?
> >
> > I've always thought about it like this in a way, with a good
> > separation between backend and frontend. And now we need to decide on
> > a protocol too, wohoo!
> I'd rather stick to using the client-server communication exposed by the
> database backend until after the first release. However, if we plan this
> carefully, creating a new "Phli server backend" will be pretty easy. I've
> been thinking about using XMLRPC or something the like for the client
> server communication, but I'm not sure...

Isn't XMLRPC kind of a meta-protocol. A protocol and syntax used to
transfer messages in another protocol. That's allways how i've seen it
anyway.

Yep. It should be fairly easy to create a not-so-server-backend
architecture that later can be split up.


-- 
Johan Viklund