Skip to main content
added 215 characters in body
Source Link

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

My concerns are traits such as ease of deployment, security and scalability for example.

With that in mind, which of the 2 technologies are best suited to this task - or rather, am I missing a technology from the list altogether that would be better suited to the job?

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

My concerns are traits such as security and scalability.

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

My concerns are traits such as ease of deployment, security and scalability for example.

With that in mind, which of the 2 technologies are best suited to this task - or rather, am I missing a technology from the list altogether that would be better suited to the job?

deleted 208 characters in body; edited title
Source Link

Which technologies are commonly used to 'phone home' usage data fromis technology is preferably for uploading desktop appsapplication usage statistics, and what are their associated pros/consSFTP, or HTTPS?

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

Which technologies are commonly used to achieve such tasks in a desktop application, and what are the pros and cons associated with these? My concerns are things such as security and scalability.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

I feel I must be missing a plethora of different techniques usedMy concerns are traits such as security and scalability.

Which technologies are commonly used to 'phone home' usage data from desktop apps, and what are their associated pros/cons

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

Which technologies are commonly used to achieve such tasks in a desktop application, and what are the pros and cons associated with these? My concerns are things such as security and scalability.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

I feel I must be missing a plethora of different techniques used.

Which is technology is preferably for uploading desktop application usage statistics, SFTP, or HTTPS?

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

My concerns are traits such as security and scalability.

added 176 characters in body
Source Link

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

Which technologies are commonly used to achieve such tasks in a desktop application, and what are the pros and cons associated with these? My concerns are things such as security and scalability.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

I feel I must be missing a plethora of different techniques used.

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

Which technologies are commonly used to achieve such tasks in a desktop application, and what are the pros and cons associated with these? My concerns are things such as security and scalability.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc)
  • HTTP (S?) PUSH or PUT to a web server

I feel I must be missing a plethora of different techniques used.

I would like to add functionality to an existing .NET 6, WinForms app (currently migrating to .NET 8 if that is of any relevance), to periodically upload user usage metrics, in addition to providing capability for users to 'push' log files etc to a server where we can access them immediately, rather than users exporting logs and emailing them etc.

Which technologies are commonly used to achieve such tasks in a desktop application, and what are the pros and cons associated with these? My concerns are things such as security and scalability.

The files are typically small (10s of KB), and no more than a few hundred concurrent users. Users need to be able to upload, but not download, or see any data on the server.

The files themselves are plain text log files, which will then be downloaded and processed by various tools on-premises.

My current thinking is:

  • SFTP to a SFTP server either hosted on-prem, or in cloud (AWS, etc) - this option I am far more familiar with, including hosting the FTP server on-prem.
  • HTTP (S?) PUSH or PUT to a web server. This option I am far less familiar with, notably where/how to host the web server itself.

I feel I must be missing a plethora of different techniques used.

Source Link
Loading