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

How many subscriptions is too many for this? #147

Open
jr69 opened this issue Jan 6, 2017 · 1 comment
Open

How many subscriptions is too many for this? #147

jr69 opened this issue Jan 6, 2017 · 1 comment

Comments

@jr69
Copy link

jr69 commented Jan 6, 2017

Does react-komposer reuse subscriptions, i.e. doing something like:

Meteor.subscribe('test');
Meteor.subscribe('test');
Meteor.subscribe('test');
Meteor.subscribe('test');
Meteor.subscribe('test');
Meteor.subscribe('test');

So can I have many small React components with containers? Or should I have one big container, and then have many small react components inside it, with less overhead

@janzenz
Copy link

janzenz commented Jan 19, 2017

I have somewhat similar question. Mine is about nested components, does it cause performance issue if we repeatedly connect each nested component, let's say with similar data or any data that can be derived from the ParentContainer? In Redux this is acceptable and encouraged I don't know with Komposer.

For example

function dataLoader() {
  Meteor.subscribe('test');
}

compose(dataLoader())(ParentContainer)

function dataLoader() {
  Meteor.subscribe('test');
}

compose(dataLoader())(GreatGrandChildContainer)

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

No branches or pull requests

2 participants