You have a VB or VC++ application that needs to log in to a remote server, send a few commands and read back what comes out, and you would rather not wrestle with raw sockets or a terminal emulator's scripting language. EasyCom from Studioware is an ActiveX control built for that job.
Quick facts
- Version: 3.4
- Type: Winsock/Telnet communication ActiveX control
- Languages: Visual Basic and Visual C++ (any environment that can host ActiveX controls)
- Licensing: design-time license owner and key
Key features
Wait for the answer you expect, with a time-out
The Read method waits until one of the strings you list is received, then hands control back. If nothing arrives, it stops at the time-out you set. When several answers are possible, it tells you which one came back, so your code can branch on a "login failed" or "unknown customer" reply.
One interface for TCP/IP and serial links
Whichever communication layer you use, the methods stay the same. Only the string you pass to Open changes. TCP/IP runs over Windows sockets 2.0 and includes minimal Telnet emulation, which refuses the remote machine's service requests and hides the Telnet protocol characters from Read. Asynchronous links use Microsoft's freely redistributable Mscomm32.ocx, and assume a PAD device following the ITU-T X3 recommendation.
Run unattended or show a terminal view
Errors appear as messages for a duration you choose, so a job can run with no user intervention. If you want feedback, a terminal view window shows the characters exchanged and has a Cancel button to end the connection early.
Get notified when data arrives
You can skip waiting for a specific string. Call CheckIncoming with a true parameter and the Incoming event fires when characters come in from the remote computer.
A short, predictable call sequence
The order is Open, Connect, then as many Write, WriteNoEcho and Read calls as you need, then Disconnect and Close. WriteNoEcho keeps passwords out of the terminal view. A Version method returns the component's version at any time.
Who it's for
EasyCom suits VB and VC++ developers who need to automate conversations with network equipment or servers, such as configuring remote devices or pulling information from them. The vendor's own comparison is that you get more control than a terminal emulator's built-in scripting. You can detect different possible replies and process the characters received yourself.
Pros and cons
Pros
- Simple method set with a documented VB sample
- Handles multi-answer reads and time-outs
- Works unattended or with visible feedback
- Same interface across layers
Cons
- Telnet support is minimal: it denies the remote machine's option requests
- The serial option depends on Mscomm32.ocx and a PAD-style device
- The X25 and Wincom layers are legacy. They are not in the base release and are provided only on request
- It is an ActiveX control, so it only suits environments that can host one
FAQs
Which languages can I use it with?
It is aimed at VB and VC++. Any development environment that can use ActiveX full controls should work.
Does it support Telnet?
Yes, in a minimal form. Open the connection as "Telnet" and the control hides the protocol characters from your reads.
Can I use a serial connection?
Yes. Asynchronous communication goes through Microsoft's Mscomm32.ocx and assumes a PAD device using the ITU-T X3 recommendation.
Can I see what is being exchanged?
Yes. The optional terminal view window displays the characters sent and received.
System requirements
EasyCom runs on Windows. TCP/IP use relies on Windows sockets version 2.0. Serial use needs the Mscomm32.ocx component.