Timeline for Image resizing client side vs server side
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2016 at 2:12 | history | edited | XaolingBao | CC BY-SA 3.0 |
added 61 characters in body
|
| May 15, 2016 at 1:49 | vote | accept | Alex | ||
| May 15, 2016 at 1:44 | history | edited | XaolingBao | CC BY-SA 3.0 |
added 506 characters in body
|
| May 15, 2016 at 1:42 | comment | added | XaolingBao | I don't think there is any value in doing it client side, if the clients will be slow, and the servers are much faster. You should be able to do it much faster in Java, than doing it in Javascript, so I would say Server-Side would be a lot better. The thing is you will have to, most likely, save the images, read them, alter them, then resave them (overwriting the old one, or deleting and creating a new one), so there are a few additional steps on the server, than just saving it straight. | |
| May 15, 2016 at 1:37 | comment | added | Alex | So there isn't any specific 'value' to do it on the client side other than reducing the load from the server. The server (JAVA back end) can handle lots of request and there will be multiple users upload images here and there. I guess to make a better user experience it would be preferable to do it server side as I think most of the users have slow pc. | |
| May 15, 2016 at 0:45 | review | First posts | |||
| May 16, 2016 at 14:04 | |||||
| May 15, 2016 at 0:38 | history | answered | XaolingBao | CC BY-SA 3.0 |