Skip to content
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.

Structuring rocketnode #27

Open
wants to merge 91 commits into
base: develop
Choose a base branch
from

Conversation

madguy02
Copy link
Contributor

@madguy02 madguy02 commented Jul 14, 2018

testing-1
testing-2

Rocketnode code now exists inside client.js file in federationclient.js package /server/client.js .
There is no need to start the rocketnode.js manually/separately
test-fed

@madguy02
Copy link
Contributor Author

@Hudell i have updated the code to exist inside the package, thereby not needing to start it separately. There are few things i need to structure as well, this is now a WIP

@madguy02 madguy02 changed the title Structuring rocketnode Structuring rocketnode[WIP] Jul 14, 2018
@Hudell Hudell self-assigned this Jul 15, 2018
@madguy02
Copy link
Contributor Author

[update] a single message can be sent from one Server-instance to another. Working on improving it

@madguy02
Copy link
Contributor Author

@Hudell , you can test the demo federation(which was earlier done by rocketnode and was only for a single message), now the rocketnode is inside rocketchat-federationclient, and works for every message typed in by user on one server. Please review it whenever possible

@madguy02 madguy02 changed the title Structuring rocketnode[WIP] Structuring rocketnode Jul 22, 2018
@madguy02
Copy link
Contributor Author

@Hudell i am taking this off from WIP for the moment (untill reviewed)

@madguy02
Copy link
Contributor Author

Added a small module for peer discovery(still under experimentation)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants