Difference between revisions of "Talk:OpenCobalt"
From Organic Design wiki
(Lets see what these guys say about our P2P CMS/PM app :-)) |
(chop) |
||
| Line 5: | Line 5: | ||
rather than using a centralised web-server. | rather than using a centralised web-server. | ||
| − | We've researched existing CMS's such as Plone to see if they could be modified to operate on top of a DHT but found that they rely too heavily on querying methodologies that are incompatible with the P2P paradigm. | + | We've researched existing CMS's such as Plone to see if they could be |
| + | modified to operate on top of a DHT but found that they rely too | ||
| + | heavily on querying methodologies that are incompatible with the P2P | ||
| + | paradigm. | ||
| − | I realise that Cobalt is really intended as a virtual world system, but it seems that it has a lot of the P2P applicational functionality in place that could be developed to serve content to a local standard browser. | + | I realise that Cobalt is really intended as a virtual world system, |
| + | but it seems that it has a lot of the P2P applicational functionality | ||
| + | in place that could be developed to serve content to a local standard | ||
| + | browser. | ||
| − | We have a specific application in mind that we like to develop which is a project-management/workflow environment running in a CMS with some other standard tools such as wiki/blog, but rather than a web-server we'd be using a local P2P app as the backend. I'm wondering what you guys, the OpenCobalt developers, think of the practicalities of this idea? | + | We have a specific application in mind that we like to develop which |
| + | is a project-management/workflow environment running in a CMS with | ||
| + | some other standard tools such as wiki/blog, but rather than a | ||
| + | web-server we'd be using a local P2P app as the backend. I'm | ||
| + | wondering what you guys, the OpenCobalt developers, think of the | ||
| + | practicalities of this idea? | ||
We have a good budget available for this and will be developing it as a | We have a good budget available for this and will be developing it as a | ||
Revision as of 23:44, 4 January 2011
Lets see what these guys say about our P2P CMS/PM app :-)
Hi, I'm part of a development team who are helping an organisation to architect a CMS based project that they want to work in a P2P network rather than using a centralised web-server. We've researched existing CMS's such as Plone to see if they could be modified to operate on top of a DHT but found that they rely too heavily on querying methodologies that are incompatible with the P2P paradigm. I realise that Cobalt is really intended as a virtual world system, but it seems that it has a lot of the P2P applicational functionality in place that could be developed to serve content to a local standard browser. We have a specific application in mind that we like to develop which is a project-management/workflow environment running in a CMS with some other standard tools such as wiki/blog, but rather than a web-server we'd be using a local P2P app as the backend. I'm wondering what you guys, the OpenCobalt developers, think of the practicalities of this idea? We have a good budget available for this and will be developing it as a completely free open source component, so we'd also like to hear from developers who may be interested in working on the project too. Thanks a lot, Aran
