Rasjid > On Apr 12, 5:50 am, Gloria W <strang...@comcast.net> wrote: > >> This monolithic PHP model just isn't sustainable, and may end-users >> don't realize it until (1) they're in the thick of it and need to >> upgrade a year later, or (2) they try to do something very advanced in >> this framework. I think Python and Kamaelia can get us out of this mess, >> and I want to put together a simple example for the Open Web conference >> to demonstrate this. >> > > Hi Gloria, > > This may be of interest to you. I'm currently working on (and mostly > finished) a fully bi-directional fully asynchronous json-rpc server > and client written with Kamaelia, and have already successfully got a > Python web framework (CherryPy) talking to the json-rpc server which > then does all the business logic and talks to the database. The nice > thing about it is that *anything* that can speak json-rpc can be the > front-end. You are able to have multiple front-ends (potentially > written in pretty much any language you like) all able to speak to the > same json-rpc server and so have the same business logic (written in > Python) working for all clients. It is fully bi-directional so things > like callbacks are possible - although this is more relevant for > standard GUI clients than for web-based clients (unless you use > Orbited). It looks like there are already a couple of json-rpc > libraries for PHP, although they might need a little adjusting. > > I have permission to open-source it, and hope to have something up > somewhere within a few weeks. If you are interested I could send it > to you directly in its current state just to give you an idea. > > *** Note to Michael *** > > Kamaelia is fantastic! I had my first version of a working json-rpc > server in under a day, and that includes the time spent learning > Kamaelia. Getting it fully bi-directional and asynchronous took a few > more days, but was generally easy and a lot of fun. The only gotcha's > I had was that at one point I was passing Axon.Ipc.producerFinished > instead of Axon.Ipc.producerFinished() and was wondering why my server > did not disconnect, and working out that my threaded components had to > be activated manually because they were not part of a Pipeline/ > Graphline etc. I have currently spent less than 5 days full time on > the project. I think I spent more time than that just trying to get > my head around Twisted and it's Perpsective Broker a couple of years > ago - only to discover that running it on a background thread was > strongly discouraged - and my desire to have something like Axon's > Component Handles was dismissed as being unnecessary. > > One of the biggest wins for me with Kamaelia is that I can *draw* my > component design on paper before I start coding. In moving my > original uni-directional synchronous rpc server to being bi- > directional and asynchronous, once I got the 'circuit diagram' right, > I pretty much knew it would all work even before I started changing > the code. Beautiful! :-) > > Cheers, > > Rasjid. > Hi Rasjid,
This sounds awesome. I would love to see it. I hear that PHP 4 json-rpc is broken, so we'd have to make a decision to fix/support it or not. I had in mind an HTTP ReST interface, but aside from the transport layer, they can be exactly the same at the JSON structure layer. This sounds like a great tool to use for this purpose. Can you pose the code in pastebin somewhere, or attach it? It would be great to see it and start playing with it in the context of DBI and Authorization logic replacement of Drupal and Wordpress. Thank you, Gloria --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to kamaelia@googlegroups.com To unsubscribe from this group, send email to kamaelia+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en -~----------~----~----~----~------~----~------~--~---
