How to communicate the server to desktop?

The goal with connecting your server to your computer is to see the server as a shared volume on your Mac, PC or Linux client. That will allow you, for example, to create a video project (in your video editing application) on one computer, import some video files in the project and organize them. And if you store your project file on that shared volume (the server), you would be able to open that project from another client computer connected to the server. The action of connecting the server to the client and having it show up as a shared drive is called mounting.

Each OS has built-in, generic protocols of mounting network storage. These protocols have a base level of functionality that most any OS will understand. This makes connecting to new network storage easier, and also eliminates the need for custom drivers to access the network storage.

Networking protocols are like different languages that computers speak in order to communicate with each other and share files. The ones that are most commonly used for video post-production are NFS and SMB.

Assuming your server supports both, here is some comparison that might be helpful to identify what is best for your workflow and your environment.

NFS vs. SMB: Top Features and Known Issues

Stability and Connectivity

Generally speaking, NFS is more sustainable and robust when it comes to network interruptions. It is rarely affected by network adapter updates or OS updates which makes it more reliable and future proof.

Recycle Bin

With SMB shares, you have the option to enable a recycle bin that lives on the share itself. That means, that every time you delete a file from the share, it will be sent to that recycle folder and you can delete it from there later. That minimizes the possibilities for a user error.

I hope this answers your query!

Ben Martin

@Tamil RK

when we create web API/ Service , at that time only we create Authentication , for example there are many authentication schemes like basic, OAuth , if we secure our service with basic scheme then user will send userId and Password in Authentication header while communicating with the service, the service on the otherhand will check , from databse or anywhere saved in your sevice that user has send right userId and Password or not.

 

You need to understand SOAP request and response (if implementing web Service) or Http Request and Response if implementing Web API.

best of luck.

Thanks for helping @Sachin Singh and @Mageshwaran R

 

Hi Tamil,

Please refer this link,

 

https://www.c-sharpcorner.com/UploadFile/0c1bb2/consuming-wcf-service-in-wpf-application/ 

web service and web API are created for the same purpose you have, once you host your API you can communicate with any device whether it be desktop, laptop or mobile.

The Authentication will be handled by API itself, means you have to implement authentication while creating the api/service which will check all requests that it receives, if the request is valid then it will send appropriate response otherwise it will send UnAuthorized request status code.

I think , you got the solution.

now make your hand dirty and create a secure Web API or service and host that first.

best of luck.