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.

Sign up for GitHub

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

Jump to bottom

Server side rendering #110

Open
mitar opened this issue Dec 29, 2015 · 4 comments
Open

Server side rendering #110

mitar opened this issue Dec 29, 2015 · 4 comments

Comments

@mitar
Copy link
Member

mitar commented Dec 29, 2015

Preliminary testing looks pretty promising. Many tests are already passing. It seems that if the author is precise how they define components, things work. So no jQuery changes of DOM, and state local to the component instance, without global state.

This pull request would help that we do not have to copy too much code from the templating package: meteor/meteor#5903
@mitar
Copy link
Member Author

mitar commented Dec 30, 2015

Some questions with server side rendering:

  • what to do with *.html files which add things to <head> and <body>
  • can we use this for spiders?
  • and that content is rendered on the server, send to the client, and then replaced with the client dynamic version?
  • how to integrate routing, how to support rendering without routing?
  • when rendering the page, how to know what should be the value of Meteor.userId()
  • what to do with subscriptions from the component? should we just make component.subscribe immediately return, be a no-op, and pretend it is subscribed? how do we provide then things like subscription scope? also, publish functions tend to limit the fields available to the client, and client might assume that no extra fields are available and render everything available, with no-op implementation of subscribe, all fields would be available and this might reveal sensitive information (imagine a component which simply calls EJSON.stringify on documents)

mitar added a commit that referenced this issue Dec 30, 2015
@mitar
Preliminary support for server side rendering.
0a4f25d 
See: #110
mitar added a commit that referenced this issue Dec 31, 2015
@mitar
Support for <head> and <body> tags in server side templates.
6fd2454 
See: #110
@mitar mitar mentioned this issue Feb 27, 2016
Open
@mitar mitar mentioned this issue Mar 31, 2016
Closed
@thebarty
Copy link

thebarty commented Apr 4, 2016

I have a general question about SSR in Meteor in combination with BlazeComponents.

Let's say I have a shop and want everything to be static (SSR or Caching p.e. thru Ngnix), except the "add-to-shopping-cart"-functionality and "your-last-viewed-products-history"-functionality.

How would you approach this as a pro? is this currently possible in Meteor at all?

@mitar
Copy link
Member Author

mitar commented Apr 4, 2016

Not really sure. I have not looked yet much into server-side rendering.

@thebarty
Copy link

thebarty commented Apr 4, 2016

I created a topic for discussion on https://forums.meteor.com/t/ssr-rendering-wholepunching/20680

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mitar @thebarty