When people think of the Secure Shell (SSH) protocol, interactive terminal sessions and secure file transfers are typically what to come to mind. In addition to these common functions, SSH also supports securely executing a command on a remote host and returning the output of that command back to the local system. The SSH component that is included with the SocketTools Secure Editions enables you to take advantage of this functionality through a single method call named Execute. Continue reading
The SocketTools 6.0 .NET Edition introduced the new InternetServer class that was designed to simplify the implementation of a TCP/IP server application. With only a few lines of code, you can create the framework for a multi-threaded server that is completely event driven. You only need to create event handlers and then write your server code to respond to those network events. Continue reading
SocketTools 6.0 introduced some new functionality as part of the existing file transfer API and components that enables applications to verify that the contents of a file on the local system are the same as a file on the server. This can be used to either ensure that a file was uploaded correctly, or to check whether or not a file should be downloaded. For example, an application could check to see if the contents of a local file were the same as a remote file the user has requested to download, and if they match, the application knows it’s not necessary to download the file again. Continue reading
One of the new features in SocketTools 6.0 is the Message Store API which is designed to make it simple to store and manage email messages on the local system. For developers who use the POP3, IMAP4 and NNTP components to retrieve messages, the storage API enables those messages to be easily stored in a single file, rather than storing them individually in separate text files. The actual message store format is similar to the standard UNIX mbox format, and the API can actually be used to open mailboxes that were created on a UNIX or Linux system. Continue reading
One typical requirement for many applications today is the ability to transfer files between the local system and a remote server, and the File Transfer Protocol (FTP) and Hyptertext Transfer Protocol (HTTP) are the two most commonly used Internet protocols for this purpose. SocketTools has components that support both of these protocols, making it a simple task to integrate this functionality into your own software.
PowerShell is Microsoft’s new command line shell and scripting development environment for the Windows platforms. It primarily serves as both a replacement for the classic command line (cmd.exe) and as an administrative tool that integrates much of the functionality that was previously found in other tools like Windows Scripting Host (WSH) and the Network Shell (netsh). PowerShell was released in November 2006, and is available as a free download for Windows XP, Windows Server 2003 and Windows Vista. Microsoft has announced that it will also be included as part of Windows Server 2008. In this article, we’ll talk about how you can use SocketToolsÂ withÂ PowerShell.
A number of years ago, we published a newsletter called SocketTips which provided general programming tips, how-toâ€™s and code snippets to help developers make the most of SocketTools in their applications. Weâ€™re going to pick up where we left off, and start with covering some of the new features and functionality that was introduced in SocketTools 5.0. Each of these articles will be categorized as SocketTips, so theyâ€™ll be easy to search and reference in the future. If anyone has any ideas about articles they would like to see written, please let us know. For the first tip, weâ€™ll talk about how to simplify your code using URLs with the FTP and HTTP components.