Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What should this project be called? #1

Closed
Nhowka opened this issue Jun 19, 2018 · 4 comments
Closed

What should this project be called? #1

Nhowka opened this issue Jun 19, 2018 · 4 comments
Labels
help wanted Extra attention is needed

Comments

@Nhowka
Copy link
Owner

Nhowka commented Jun 19, 2018

This project was born from the knowledge I got from working on Fable.Remoting. It's one of many amazing projects from @Zaid-Ajaj that I recommend if you don't know about it yet.

Now, it's time to leave the nest; the names are too similar and that will cause confusion.

On one hand, Fable.Remoting is a general use library. You can call functions over the wire and when done on the recommended guidelines is stateless. This project is designed to work on an Elmish environment. It's stateful and changes that state by exchanging messages between client and server (or server-server and client-client, but only the client-server travels through the magic channel WebSocket.

So. It's a client-server tool for communication with Elmish. Only Elmish. That is an important bit. The Remoting part? Well, I'll be sad to let it go, but we can live with another name. I even brought some options ready, but I'm not a creative person on naming things.

How about Elmish.Link? Or maybe Elmish.Wire? The project creates a way for messages to go on their way, traveling to change a state on a distant realm. (Or not that far, most action it got was on localhost.)

Enough of story time! Bring me your best names!

@Nhowka Nhowka added the help wanted Extra attention is needed label Jun 19, 2018
@chmuri
Copy link

chmuri commented Jun 19, 2018

Traveling is one thing but on the way needs two directions route so my vote is for Elmish.Route/Routing.

@MangelMaxime
Copy link

Please do not use Elmish.Route/Routing it's really confusing because in JS ecosystem this have another meaning. Where a router is in general responsible for managing the application state based on Url (aka Navigation).

You seems to use a lot the term Bridge in the program initialisation perhaps it can lead somewhere.

@Nhowka
Copy link
Owner Author

Nhowka commented Jun 19, 2018

@chmuri That also could clash with the elmish-browser feature.

@MangelMaxime That is mostly to things that expect the normal Elmish Program. It creates a bridge inside the ClientProgram to reach it, but it's mostly local and not used in the server context. I don't dislike Bridge, but I gave it the same meaning of compatibility layer. 🤔

@Nhowka
Copy link
Owner Author

Nhowka commented Jun 24, 2018

It's decided. The next version will be released as Elmish.Bridge.

@Nhowka Nhowka closed this as completed Jun 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants