I came across this article post called Neutron Protocol: Separating UI From The CMS which discusses a protocol that exists for essentially allowing client access to the CMS so that developers may create a completely separate UI from that of data submitted/entered into the CMS. There is no problem with this except that it pretty much already exists in the form of XML-RPC. The author makes it seems as if this is a problem but indeed I believe the Neutron Protocol died because it simply wasn't needed. Right now, today, with Zope/CMF or Plone in general. I can expose any method/function/class/object that I want via XML-RPC and even provide get/set methods for data in the context it exists. So for example; if I want to get the top 100 models from a CMS install all I have to do is from zope.app.publisher.xmlrpc import MethodPublisher and derive a class with MethodPublisher as an argument. From here I can use whatever language I want to call these methods effectively allowing me to create a brand new UI. So this stuff is pretty simple using XML-RPC but it'll be interesting to see what if any thing comes of this. If it's light enough it could be useful as an interim to XML-RPC exposure of data/content. At the very least it'd be useful for developers who aren't necessarily intimately familiar with the codebase but want to have their own UI available for content.
Christopher Warner is part genius, part idiot. This makes him well balanced. He's worked on numerous opensource projects with great people and has generally led an eventful and fulfilling life. He hopes to retire an old man in a rocking chair should he be so fortunate.
Neutron Protocol
I came across this article post called Neutron Protocol: Separating UI From The CMS which discusses a protocol that exists for essentially allowing client access to the CMS so that developers may create a completely separate UI from that of data submitted/entered into the CMS. There is no problem with this except that it pretty much already exists in the form of XML-RPC. The author makes it seems as if this is a problem but indeed I believe the Neutron Protocol died because it simply wasn't needed. Right now, today, with Zope/CMF or Plone in general. I can expose any method/function/class/object that I want via XML-RPC and even provide get/set methods for data in the context it exists. So for example; if I want to get the top 100 models from a CMS install all I have to do is from zope.app.publisher.xmlrpc import MethodPublisher and derive a class with MethodPublisher as an argument. From here I can use whatever language I want to call these methods effectively allowing me to create a brand new UI. So this stuff is pretty simple using XML-RPC but it'll be interesting to see what if any thing comes of this. If it's light enough it could be useful as an interim to XML-RPC exposure of data/content. At the very least it'd be useful for developers who aren't necessarily intimately familiar with the codebase but want to have their own UI available for content.
Related Posts:
About Christopher Warner
Christopher Warner is part genius, part idiot. This makes him well balanced. He's worked on numerous opensource projects with great people and has generally led an eventful and fulfilling life. He hopes to retire an old man in a rocking chair should he be so fortunate.