Difference between revisions of "Talk:Seaside"
From Organic Design wiki
(Our main vision for the 3D environment is the modern Geoscope) |
(3D comment moved to Talk:OpenCobalt) |
||
| Line 1: | Line 1: | ||
== Integration of Seaside with OpenCobalt == | == Integration of Seaside with OpenCobalt == | ||
Some questions/thoughts that came to mind that I would like to clarify: | Some questions/thoughts that came to mind that I would like to clarify: | ||
| + | |||
=== 3D === | === 3D === | ||
| − | + | ''3D comment moved to [[Talk:OpenCobalt]]'' | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== seaside<-->browser bridge === | === seaside<-->browser bridge === | ||
As I understand it, seaside, in its current implementation, is the browser and repository. In other words it is a peer in the peer to peer network and contributes to the dht storage as well as the virtual routing system. I can see how it can also become an http server, acting as a bridge between the peer to peer network and traditional browser clients. However browser users, since they are not using the seaside client, will only be able to consume and contribute content, but will not be contributing storage or routing. What sort of incentives will there be to run the peer to peer client? Perhaps the capabilities offered by the bridge will be limited? | As I understand it, seaside, in its current implementation, is the browser and repository. In other words it is a peer in the peer to peer network and contributes to the dht storage as well as the virtual routing system. I can see how it can also become an http server, acting as a bridge between the peer to peer network and traditional browser clients. However browser users, since they are not using the seaside client, will only be able to consume and contribute content, but will not be contributing storage or routing. What sort of incentives will there be to run the peer to peer client? Perhaps the capabilities offered by the bridge will be limited? | ||
Revision as of 19:31, 18 January 2011
Integration of Seaside with OpenCobalt
Some questions/thoughts that came to mind that I would like to clarify:
3D
3D comment moved to Talk:OpenCobalt
seaside<-->browser bridge
As I understand it, seaside, in its current implementation, is the browser and repository. In other words it is a peer in the peer to peer network and contributes to the dht storage as well as the virtual routing system. I can see how it can also become an http server, acting as a bridge between the peer to peer network and traditional browser clients. However browser users, since they are not using the seaside client, will only be able to consume and contribute content, but will not be contributing storage or routing. What sort of incentives will there be to run the peer to peer client? Perhaps the capabilities offered by the bridge will be limited?
