search

DhavalW / octopus

Lightweight, bi-directional RPC, for Node JS & browser - with namespaces, and swappable, arbitrary mix of transports !
MIT License
1 stars 0 forks source link

Octopus & Wildcard #3

Open brillout opened 4 years ago

brillout commented 4 years ago

Hi @DhavalW!

Looks interesting what you've built! Do you have plans to further push Octopus RPC?

I also implemented an RPC tool: Wildcard API. What do you think?

DhavalW commented 4 years ago

Hey @brillout Wildcard looks great and pretty well done ! Could use a simpler initial readme though. Looks daunting at the outset. But I think you've got the concept on point and your api seems well / better designed too. Haven't had a chance to go through the code yet, but will soon.

Octopus was built as a base for an internal project and i did have plans to further it, but have been focused on more pressing matters since.

Open to any ideas though, whats on your mind ?

brillout commented 4 years ago

Hi!

whats on your mind ?

I really like the bi-directional and 1:n capability of Octopus. Although it could be nice to make it easier for simpler use cases that don't need bi-directional communication?

Octopus expects a ready socket connection and does not handle connection/reconnections. That is left to the user to implement.

Why not automatically handling this for the user?

Could use a simpler initial readme though. Looks daunting at the outset.

What would you do differently?