Does Ejabberd/Erlang support any thumbnail generation by any means (compression logic)?

Hi,

I am dubious about the approach usually followed by popular Chat applications like Whatsapp, Wechat etc. It is seen that these apps share a low -resolution blurred out image of the actual image/video file. How is this managed?

My concern is the space management at the server end. Does the client process the original image and create a low-res version and sends 2 requests (Original+blurred file) to the server? Following which, the blurred image being lower in size is shared with others who trigger a GET request for the original image/video file.

Or does the server itself does some processing one the Original file received and make a low-res version out of it. And proceeds as above.

In both cases i could think of, space is being eaten up at the server end with 2 instances of each image/video being shared.

Ques 2:
Does ErlangOTP support any compression logic which would generate a fuzzy/blurred thumbnail image of the original image. Because in that case 2 requests won't be required but processing can be done using OTP.

Kindly let me know how this is genrally carried out. Would be grateful!

Image transfer typically

Image transfer typically happen out-of-band, with transfer negotiation being done over XMPP. So, ejabberd is not doing any image manipulation.

Syndicate content