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

Is locomotive active ? And what about cluster? #12

Closed
lundin opened this issue Apr 29, 2012 · 3 comments
Closed

Is locomotive active ? And what about cluster? #12

lundin opened this issue Apr 29, 2012 · 3 comments

Comments

@lundin
Copy link

lundin commented Apr 29, 2012

Hi Jared,

Are you still working with locomotive ? I find it very good and easy to get up and running so a big thanks to you. But with Express 3.0 and future versions coming i am wondering what will happen with locomotive ?

I like the simple design of your MVC-architecture, mabey the geedy models can be handy sometimes, but having a good js framework on the client (like extjs) can overcome this instead.

Also, i am missing an app.js file to bind the models, views and controller and define globals like:

locomotive.application({
name: 'myApp',

appFolder: 'app',

controllers: [
'Users'
],
models:[
'Users''
],
launch: function() {
..
}

In here i would like to use some native nodejs function like cluster etc.How do use use cluster/workers with locomotive ?

After all, doing some work just to learn is fine, but do i dare to use locomotive on a real web app ?

@jaredhanson
Copy link
Owner

Of course, Locomotive is definitely still active!

Once Express 3 lands, Locomotive will be updated to be fully compatible with it. I've been testing Express 3.x for a few months now, and the changes will be minimal.

Regarding customizing the app, check out this discussion on the Google Group:
https://groups.google.com/d/topic/locomotivejs/WnKmRpr-i1k/discussion

Cluster support will be built in to Locomotive soon, so you can launch an app with lcm cluster. It seems like the cluster API in node is a bit in flux between 0.6.x and 0.8.x, so I'm letting that settle a bit before investing in building it into Locomotive. But the layering discussed in the above discussion should allow you to do it separately, if you want.

Above everything else, I intend to keep Locomotive as minimal as possible. Just enough to boot an Express instance with some MVC sugar, covering the 80% cases well, and then let the app layer on anything else it needs.

The currently filed issues are a good representation of my to-do list for Locomotive. And I'm attempting to tick one "big" item off every 2-3 weeks (usually in service to my own needs, at the moment).

Feel free to send feedback or requests, and I'll gladly accept patches!

@lundin
Copy link
Author

lundin commented May 1, 2012

Jared,

Thanks for your reply, good to know and it all make sense.

And for the app logic, doing it in myserver.js rather than using the lcm command i very much like it (that would also separate it from other MVC framworks having the same server start "feature") and encourage you to follow that path. It just makes it all transparent and clean.

Using express, locomotive and passport, it is amazing how rapid app prototypes can be made to check out your ideas!

@jaredhanson
Copy link
Owner

Cluster support will be available in Locomotive 0.4.0, scheduled for release this week. See this comment for further details.

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

No branches or pull requests

2 participants