Just starter work on SpikeNet. Let me explain what it is.This how the whole system will work:
SpikeNet is going to be a federated BBS network that uses basic TCP for some tasks and also using HTTP to transport messages. Each user runs the Spike software and then peers with another user using the software and a link is established. Messages will then be distributed all over on the network.
It sounds more like decentralization.
Anyway. The only things you will need to open are a few ports which will be used for the whole system.
Just starter work on SpikeNet. Let me explain what it is.
SpikeNet is going to be a federated BBS network that uses basic TCP for some tasks and also using HTTP to transport messages. Each user runs the Spike software and then peers with another user using the software and a link is established. Messages will then be distributed all over on the network.
It sounds more like decentralization.
Anyway. The only things you will need to open are a few ports which will be used for the whole system.This how the whole system will work:
You run the client and get the IP:port of a peer and then within the client you add the peer. Then your client makes a TCP/IP socket connection to that peer at the `addPeer` port where yoh will send your IP address to the peer and the port that your BBS http server is running on. The peer can now get your posts. Then what will happen is he will add you as the packet will contain your `addPeer` address:port. Then you can exchange your http addresses:ports and will be able to sync messages.
Just starter work on SpikeNet. Let me explain what it is.
SpikeNet is going to be a federated BBS network that uses basic TCP for some tasks and also using HTTP to transport messages. Each user runs the Spike software and then peers with another user using the software and a link is established. Messages will then be distributed all over on the network.
It sounds more like decentralization.
Anyway. The only things you will need to open are a few ports which will be used for the whole system.This how the whole system will work:
You run the client and get the IP:port of a peer and then within the client you add the peer. Then your client makes a TCP/IP socket connection to that peer at the `addPeer` port where yoh will send your IP address to the peer and the port that your BBS http server is running on. The peer can now get your posts. Then what will happen is he will add you as the packet will contain your `addPeer` address:port. Then you can exchange your http addresses:ports and will be able to sync messages.
When you have peered with each other, your client will fetch the posts your peer has made on his side and he will fetch the posts you have made on your side. Posts are numbered chronologically. When the client downloads remote posts he will number them chronologically on his side, hence if you were the only person on the network a new peer could then easily get up-to-date.
Thats a rough idea of how it should work. Also. basically the network should grow from one peer if you see what i mean and grow onwards from there onwards.
Just starter work on SpikeNet. Let me explain what it is.
SpikeNet is going to be a federated BBS network that uses basic TCP for some tasks and also using HTTP to transport messages. Each user runs the Spike software and then peers with another user using the software and a link is established. Messages will then be distributed all over on the network.
It sounds more like decentralization.
Anyway. The only things you will need to open are a few ports which will be used for the whole system.This how the whole system will work:
You run the client and get the IP:port of a peer and then within the client you add the peer. Then your client makes a TCP/IP socket connection to that peer at the `addPeer` port where yoh will send your IP address to the peer and the port that your BBS http server is running on. The peer can now get your posts. Then what will happen is he will add you as the packet will contain your `addPeer` address:port. Then you can exchange your http addresses:ports and will be able to sync messages.
;When you have peered with each other, your client will fetch the posts your peer has made on his side and he will fetch the posts you have made on your side. Posts are numbered chronologically. When the client downloads remote posts he will number them chronologically on his side, hence if you were the only person on the network a new peer could then easily get up-to-date.
Thats a rough idea of how it should work. Also. basically the network should grow from one peer if you see what i mean and grow onwards from there onwards.
Another thing that this system holds is that it can automatically discover new peers by downloading a list of peers on your peers list.
Just starter work on SpikeNet. Let me explain what it is.
SpikeNet is going to be a federated BBS network that uses basic TCP for some tasks and also using HTTP to transport messages. Each user runs the Spike software and then peers with another user using the software and a link is established. Messages will then be distributed all over on the network.
It sounds more like decentralization.
Anyway. The only things you will need to open are a few ports which will be used for the whole system.This how the whole system will work:
You run the client and get the IP:port of a peer and then within the client you add the peer. Then your client makes a TCP/IP socket connection to that peer at the `addPeer` port where yoh will send your IP address to the peer and the port that your BBS http server is running on. The peer can now get your posts. Then what will happen is he will add you as the packet will contain your `addPeer` address:port. Then you can exchange your http addresses:ports and will be able to sync messages.
When you have peered with each other, your client will fetch the posts your peer has made on his side and he will fetch the posts you have made on your side. Posts are numbered chronologically. When the client downloads remote posts he will number them chronologically on his side, hence if you were the only person on the network a new peer could then easily get up-to-date.
Thats a rough idea of how it should work. Also. basically the network should grow from one peer if you see what i mean and grow onwards from there onwards.
Another thing that this system holds is that it can automatically discover new peers by downloading a list of peers on your peers list.;
Replies to posts will wotk just likr here, like an emailing thread, we will append to the post's text file.
DEAVMI wrote to ALL <=-
SpikeNet is going to be a federated BBS network that uses basic TCP for some tasks and also using HTTP to transport messages. Each user runs
the Spike software and then peers with another user using the software
and a link is established. Messages will then be distributed all over
on the network.
It sounds more like decentralization.
DEAVMI wrote to DEAVMI <=-
When you have peered with each other, your client will fetch the posts your peer has made on his side and he will fetch the posts you have
made on your side. Posts are numbered chronologically. When the client downloads remote posts he will number them chronologically on his side, hence if you were the only person on the network a new peer could then easily get up-to-date.
Thats a rough idea of how it should work. Also. basically the network should grow from one peer if you see what i mean and grow onwards from there onwards.
Yeah, probably.DEAVMI wrote to ALL <=-
SpikeNet is going to be a federated BBS network that uses basic TCP for some tasks and also using HTTP to transport messages. Each user runs the Spike software and then peers with another user using the software and a link is established. Messages will then be distributed all over on the network.
It sounds more like decentralization.
It sounds more like the way UseNet has always worked to me.
... Gone crazy, be back later, please leave message.
I know it's similiar, but I have different ideas i mind.DEAVMI wrote to DEAVMI <=-
When you have peered with each other, your client will fetch the posts your peer has made on his side and he will fetch the posts you have made on your side. Posts are numbered chronologically. When the client downloads remote posts he will number them chronologically on his side, hence if you were the only person on the network a new peer could then easily get up-to-date.
Thats a rough idea of how it should work. Also. basically the network should grow from one peer if you see what i mean and grow onwards from there onwards.
Before you reinvent the wheel, I would take a look at the NNTP RFCs first
as to me this sounds like you are trying to do the same thing Usenet
does.
... "42? 7 and a half million years and all you can come up with is 42?!"
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 333 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 16:21:52 |
| Calls: | 574 |
| Calls today: | 1 |
| Messages: | 235853 |