I've looked again at Victor's implementation ("qxjsonrpc",
http://qooxdoo.org/documentation/0.6/user_manual/rpc/python), which was
a library that could again be hosted by two server environments:
* a stand-alone HTTP server based on Python's BaseHTTTPServer
* a WSGI interface
Now we have a CherryPy implementation.
Is this a general pattern: You have an RPC layer which in turn is hosted
by some HTTP-savvy environment? Could the RPC layer be abstracted away
from the HTTP environment, so that it would be general and then be
plugged into multiple environments, maybe by the use of adaptors? So you
have only one generic RPC layer and a set of adaptors to maintain?!
Or could we reduce ourselves on the WSGI interface, since it's widely
supported (Cherrypy, Django, TurboGears, Pylons, Zope, ..., mod_wsgi for
Apache)?!
If people tend to think we should account for different server
environments rather than just develop for WSGI, then maybe in the first
step we should try to isolate the two parts in, say, the RpcPython
contrib e.g. by creating submodules for the RPC layer and the Cherrypy,
.... adaptors, and if it seems sensible maybe later reduce RpcPython to
the RPC layer and put the adaptors in dedicated contributions.
What do you guys think?
T.
Delaney Gillilan wrote:
> I sent off my info to the contrib email I'll let the thread know when
> this is all setup.
>
> On Wed, Jun 24, 2009 at 7:58 AM, thron7 <[email protected]
> <mailto:[email protected]>> wrote:
>
>
>
> Delaney Gillilan wrote:
> > I have no problem putting my version in the contrib, just didn't
> know
> > if I'd be stepping on anyone's toes doing so. The thing I like
> about
> > my version is A) handles errors gracefully B) don't need to subclass
> > anything, just use add_service() function C) can place the rpc
> > controller in any URL scheme D) only one I saw that implements the
> > test functions laid out in the rpc server wiki page. Before I
> add it
> > to contrib has anyone tried running it to make sure it works? if you
> > don't use mercurial you can still get the source as a zip/gz from
> > http://bitbucket.org/delaney/cooks_do_cherry_pie/src/ to try out.
>
> I'd say go ahead and create the contrib. It doesn't prevent
> anybody from
> adding their own as an alternative if they feel it's substantially
> different, so there shouldn't be any toes hurt :). And it doesn't have
> to be polished, on the contrary: Once it is in qooxdoo-contrib it
> should
> be much easier for people to try out and give feedback. That's
> what the
> repository is for.
>
> T.
>
>
> >
> > On Wed, Jun 24, 2009 at 7:36 AM, thron7
> <[email protected] <mailto:[email protected]>
> > <mailto:[email protected]
> <mailto:[email protected]>>> wrote:
> >
> >
> >
> > Burak Arslan wrote:
> > > Andreas Ecker wrote:
> > >
> > >> qooxdoo/Python people speak up! ;-)
> > >>
> > >>
> > >>
> > >
> > > i keep repeating this but here it is again: i got a soap-rpc
> > server in
> > > the soap contrib.
> > > http://qooxdoo.org/contrib/project#soap
> > >
> >
> > i think it's good you keep repeating that, since i'm not
> sure people
> > know how to make use of that. Your contrib wiki docu could use
> > brush-up,
> > if you ask me (in fact there is none). You could add a
> section how to
> > plug the qooxdoo RPC classes to your server?!
> >
> > > it uses soaplib-lxml.
> > > http://github.com/plq/soaplib-lxml
> > >
> > > btw, http://qooxdoo-contrib.sf.net has a bad link.
> > >
> >
> > what's that?!
> >
> > t.
> >
> > > best regards,
> > > burak
> > >
> > >
> >
>
> ------------------------------------------------------------------------------
> > > _______________________________________________
> > > qooxdoo-devel mailing list
> > > [email protected]
> <mailto:[email protected]>
> > <mailto:[email protected]
> <mailto:[email protected]>>
> > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> > >
> > >
> > >
> >
> >
>
> ------------------------------------------------------------------------------
> > _______________________________________________
> > qooxdoo-devel mailing list
> > [email protected]
> <mailto:[email protected]>
> > <mailto:[email protected]
> <mailto:[email protected]>>
> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> >
> >
> >
> ------------------------------------------------------------------------
> >
> >
>
> ------------------------------------------------------------------------------
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > qooxdoo-devel mailing list
> > [email protected]
> <mailto:[email protected]>
> > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> >
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
