[Seaside-dev] P2P CMS/PM system with SeaSide and TeaTime
aran at organicdesign.co.nz
Wed Jan 12 19:18:05 UTC 2011
The application would be from the users perspective no different than
using any other web-based CMS/PM tool, in fact there would be an
instance running on a normal server so that people who haven't
downloaded the p2p app can still use the system too.
People who have downlaoded the p2p app would see the same thing, but the
domain would resolve to localhost and the browser content sould be
served by the p2p app.
So the app itself would be served by a local squeak/seaside to each
local browser, but the persistent storage (apart from cached items etc)
would be a DHT and/or some other p2p synchronising technology.
We have a method which we're writing into our spec to allow network
queries such as "top ten most recent posts in project X" to be work
without having to wait for responses from many peers.
A big part of our application involves being able to build simple
workflow sequences which can be nested to build more complex functionality.
I may be wrong but it seems like this application (apart from the p2p
aspect) would be a very natural fit for squeak and Seaside.
If necessary we can build the p2p part of the system ourselves, but
obviously we'd prefer to work with as many existing components as we can.
On 12/01/11 23:23, Torsten Bergmann wrote:
>> out including Seaside which seems like it could the ideal
>> technology to build our system in.
> Yes, but it really depends on what you want to achieve.
> Note that Seaside is web server based ... and you want
> a P2P system
> A decentralized approach could make a good replacement
> for Dispora, which is a nice and funded idea
> - but nothing more than that
> - it has too many bugs and security problems
> - too complicated to install and setup in an environment
> (compared to Pharo/Seaside/PierCMS one click images)
> Maybe they should have choosen a more productive
> and easier to use technology like Smalltalk ;)
> Phillipe wrote:
>> I didn't get which part would be browser based and which
>> part would be P2P.
> Yes. Tell us more how the system should look like from your
> What about a local server (standalone comanche with seaside)
> that is usable via webbrowser from your machine and that
> can also server others via network. If they setup their own
> machine assets like projects, blog contents (bound to users)
> could be moved.
> P.S: Auckland is a nice place, was there two times and
> I really enjoyed it!
More information about the seaside-dev