web applications - When to use "client-side routing" or "server-side routing"? -


i'm little bit confused this, , feel stupid asking question, want understand it.

so, i'm working client side web framework, backbone, angular or durandal. framework includes routing.

but of course still have server database stuff, , on, has routing.

my question is:

when use "client-side routing" or "server-side routing"?

how "decided" whether routing performed on client side or whether request first sent web server?

i have particularly hard time imagining because client side routing before server ever gets know request.

i'd thankful if explain how these 2 routing systems work together.

p.s.: have not included code samples because i'm not looking answer concerning particular framework, concerning routing process in general.

tl;dr:

  • with server-side routing download entire new webpage whenever click on link,
  • with client-side routing webapp downloads, processes , displays new data you.

imagine user clicking on simple link: <a href="/hello">hello!</a>

on webapp uses server side routing:

  • the browser detects user has clicked on anchor element.
  • it makes http request url found in href tag
  • the server processes request, , sends new document (usually html) response.
  • the browser discards old webpage altogether, , displays newly downloaded one.

if webapp uses client side routing:

  • the browser detects user has clicked on anchor element, before.
  • a client side code (usually routing library) catches event, detects url not external link, , prevents browser making http request.
  • the routing library manually changes url displayed in browser (using html5 history api, or maybe url hashbangs on older browsers)
  • the routing library changes state of client app. example, can change root react/angular/etc component according route rules.
  • the app (particularly mvc library, react) processes state changes. renders new components, , if necessary, requests new data server. time response isn't entire webpage, may "raw" data, in case client-side code turns html elements.

client-side routing sound more complicated, because is. libraries make easy these days.

there several upsides of client-side routing: download less data display new content, can reuse dom elements, display loading notifications user etc. however, webapps generate dom on server side easier crawl (by search engines), thereby making seo optimization easier. combining these 2 approaches possible, excellent flow router ssr example that.


Comments

Post a Comment

Popular posts from this blog

commonjs - How to write a typescript definition file for a node module that exports a function? -

consider, toml node module can use: // toml.d.ts declare module toml { export function parse(value:string):any; } declare module "toml" { export = toml; } then: /// <reference path="../../../../../defs/toml/toml.d.ts"/> import toml = require('toml'); toml.parse(...); however, node module export single function, such 'glob' ( https://github.com/isaacs/node-glob ). the node usage of module be: var glob = require("glob") glob("*.js", {}, callback(err, files) { ... }); you'd naively expect this: // glob.d.ts declare function globs(paths:string, options:any, callback:{(err:any, files:string[]):void; ...but because typescripts 'import' semantics bit strange, seems can use 'import .. = require()' statement alias modules . trying call: /// <reference path="../../../../../defs/glob/glob.d.ts"/> import blog = require('glob'); results in: error ts2072: mod
Read more

openid - Okta: Failed to get authorization code through API call -

i'm integrating okta own idp server using okta's api. i'm implementing authorization code flow following steps below: in own server, use /api/v1/authn endpoint sessiontoken. use sessiontoken obtain authorization calling endpoint: /oauth2/v1/authorize?client_id=" + clientid + "&sessiontoken=" + sessiontoken + "&response_type=code&response_mode=query&scope=openid&redirect_uri=" + redirecturl + "&state=evanyang&nonce=" it's supposed return response status code 302 , location header containing redirect url code value. however, keep getting response status code 200 , without location header, html body saying "you using unsupported browser." , "javascript disabled on browser." according api documentation: http://developer.okta.com/docs/api/resources/oidc.html#authentication-request , sessiontoken parameter sufficient this: an okta one-time sessiontoken. allows api-based
Read more

thorough guide for profiling racket code -

did googling ("racket profiling", "racket measure performance"), didn't find , there no examples in docs. did google "profile" search on htdp - no luck. (profile (f ...)) output isn't obvious other small snippets. ideally want python's python -m cprofile usage examples. when search "python profiling", both duckduckgo , google give top result: 26.4. python profilers . (although scanned quickly, seems more of reference "thorough usage guide" examples. if had else in mind, perhaps please link that?) the equivalent racket documentation be: profile: statistical profiler . a usage example: #lang racket (require profile) (profile-thunk (thunk (function-to-profile arg0 arg1) )) here (thunk e) convenience (lambda () e) . bigger example: #lang racket (module mod racket (provide f) (define (f) (for/list ([i 10000]) i))) (require (prefix-in mod: 'mod)) (define (f) (for ([i 10000
Read more