No. Both the backend and browser needs to support http2 to get the benefit. 
If the browser does not but server does your web app will still work but 
won't get the performance improvements.  See below for http/2 browser 
support.

http://caniuse.com/#feat=http2


HTTP/2 protocol - OTHER <http://http2.github.io/http2-spec/index.html>

Networking protocol for low-latency transport of content over the web. 
Originally started out from the SPDY protocol, now standardized as HTTP 
version 2.

   - Global63.07%+6.8%=69.87%

Current alignedUsage relativeShow all
IE

   1. 8
   2. 11See notes:
      12
   
Edge* <http://caniuse.com/#>

   1. 13See notes:
      2
   2. 14See notes:
      2
   
Firefox

   1. 45See notes:
      2
   2. 46See notes:
      2
   3. 47See notes:
      2
   4. 48See notes:
      2
   5. 49See notes:
      2
   
Chrome

   1. 29
   2. 45See notes:
      2
   3. 48See notes:
      2
   4. 49See notes:
      2
   5. 50See notes:
      2
   6. 51See notes:
      2
   7. 52See notes:
      2
   8. 53See notes:
      2
   9. 54See notes:
      2
   
Safari

   1. 9.1See notes:
      23
   2. TPSee notes:
      23
   
Opera

   1. 37See notes:
      2
   2. 38See notes:
      2
   3. 39See notes:
      2
   
iOS Safari* <http://caniuse.com/#>

   1. 8.4
   2. 9.2See notes:
      2
   3. 9.3See notes:
      2
   
Opera Mini* <http://caniuse.com/#>

   1. 8

Android Browser* <http://caniuse.com/#>

   1. 4.3
   2. 4.4
   3. 4.4.4
   4. 50

Chrome for Android

   1. 50See notes:
      2
   

   - Notes
   - Known issues (0)
   - Resources (6)
   - Feedback

See also support for the SPDY protocol <http://caniuse.com/#feat=spdy>, 
precursor of HTTP2.

1Partial support in IE11 refers to being limited to Windows 10.

2Only supports HTTP2 over TLS (https)

3Partial support in Safari refers to being limited to OSX 10.11+

On Tuesday, June 7, 2016 at 10:02:09 PM UTC-7, Marco Stolle wrote:
>
> So if the backend supports it, the client will also?
>
> Op zondag 5 juni 2016 12:52:14 UTC+2 schreef Chuck Horton:
>>
>> Currently Firebase does not support http2 so you need to use bundled 
>> version. Once it does support http2 you could point public at 
>> build/unbundled. 
>>
>> On Sunday, June 5, 2016 at 2:19:10 AM UTC-7, Marco Stolle wrote:
>>>
>>> Thanks for the info Chuck,
>>>
>>> in case of Firebase i have to assume http2 server push is not supported 
>>> yet and serve the bundled versi.
>>>
>>>
>>>
>>> Op zaterdag 4 juni 2016 18:32:12 UTC+2 schreef Chuck Horton:
>>>>
>>>> In the case of Firebase when you do a firebase init point public to  
>>>> build/bundled.
>>>>
>>>> Below is example of firebase.json I created for PSK2 for hosting on 
>>>> Firebase.  See https://psk2-ec681.firebaseapp.com/ 
>>>> <https://www.google.com/url?q=https%3A%2F%2Fpsk2-ec681.firebaseapp.com%2F&sa=D&sntz=1&usg=AFQjCNFY5a9_timsvWaM6Qa3csHjc1SF8w>
>>>>
>>>> }
>>>>   "database": {
>>>>     "rules": "database.rules.json"
>>>>   },
>>>>   "hosting": {
>>>>     "public": "build/bundled",
>>>>     "rewrites": [
>>>>       {
>>>>         "source": "**",
>>>>         "destination": "/index.html"
>>>>       }
>>>>     ]
>>>>   }
>>>> }
>>>>
>>>>
>>>> On Wednesday, June 1, 2016 at 11:23:32 PM UTC-7, Marco Stolle wrote:
>>>>>
>>>>> i wander how does the backend know what version of your build to 
>>>>> serve, bundled or unbundled, and what if you use Firebase hosting?
>>>>>
>>>>> Gr Marco
>>>>>
>>>>>
>>>>>

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/c5756b23-7817-404d-a6af-6d43601b4ca7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to