Syncplify Server! v6.0 is OUT!

Our hearts are all full of joy while we officially announce that the long-awaited version 6.0 of our flagship product, Syncplify Server!, has finally been released today.

If you are running an older version 4.x or 5.x you will find the upgrade instructions in the knowledge base, as always.

This is our first cross-platform version, it’s been entirely redesigned, and it’s been the biggest development effort for our team to date. We hope you’ll love it as much as our previous versions, or even more. We already do.

If you’re curious to learn everything new about this major release, please take a look at this Medium article we published while development was ongoing.

Thank you all for your continued support and appreciation!


The next WebClient! will be capable of displaying thumbnails

Another commonly requested feature for WebClient! is the ability to display thumbnails for image/picture files, especially for the most common formats.

We’re glad to announce that we have, therefore, included an API in the new WebClient!’s back-end to do exactly that. It currently supports PNG, JPEG, GIF, and TIFF. And, in time, it will be expanded to support more formats.

Here above you can see a screenshot of a thumbnail generated by the next generation WebClient! API. Please note that the screenshot above shows the naked result from the API itself, inside of a development tool called Insomnia, this is not WebClient!’s user interface (just for clarity).


WebClient! v2: downloading multiple files at once as a “zip” archive

Syncplify Server! v6 will include (depending on the software edition you run) WebClient! version 2. Aside from a brand new set of much more streamlined APIs and a much tighter integration between the two pieces of software, WebClient! v2 will also feature the ability to let users download multiple files and folders in one single “zip” archive, pretty much like some of the cloud storage apps out there do.

For safety and security reasons, though, administrators will be able to set their own limits to that, of course.

Let’s say, for example, that a legitimate yet reckless user requests the download of the zipped contents of a folder containing 100,000 files, each file having an average size of 100 MB. We’re talking about 10TB of data to be compressed. We’re talking about a potential VM-killer.

So, with WebClient! v2, administrators will be able to limit the processing of the zip archive to a predefined maximum number of files and/or a predefined maximum size before compression, whichever comes first.

Here’s a few possible configuration examples:

  • zip downloads may not exceed 1,000 archived files
  • zip downloads may not exceed 200 MB of data (before compression)
  • zip downloads may not exceed 1,000 files or 200 MB of data, whichever limit is hit first

If a limit is hit, the client will still receive a perfectly functional zip archive, but a 206 response code (partial content) instead of the typical 200 response code (OK), to signify that the request was only partially fulfilled, and the limit that was hit will be clearly identified by a set of X- headers in the HTTP response.