Best weonlydo software for free download

WeOnlyDo! COM ImapServer ActiveX control is component that can be easily integrated into your applications to provide full IMAP4rev1 protocol server implementation. All you need to do is to put it on VB form, call it's Start method and it's immediately accepting connections by your clients! It fully supports commands defined in RFC2060.

Since wodImapServer is COM object and not the full application, there's few things developer should look after - simply because COM objects cannot deal with information that should be preserved between the sessions. Most important is to keep UID information (UNIQUE ID) for folders and messages. If you do so - wodImapServer will work flawlessly with any client that connects to it. On each client action wodImapServer will fire appropriate event where you can internally handle the action and return positive or negative result. You should also deal with message flags.

wodImapServer does not deal with message storage - you should do it by yourself. It will deal with structures and references to folders and messages - but actual contents of messages cannot be handled by wodImapServer. Rather, it will depend on your code when messages are accessed, hoping that you provided properly formatted messages and proper flag information. If you don't - it will not complain, but IMAP clients may...

You should consider all wodImapServer folder as virtual folders - none of them doesn't necessarily exist on your system. Each time wodImapServer requires list of folders, or list of messages - event is fired to notify you to populate his collections with appropriate information - and that's all. You can keep messages in database, on external system, or wherever you need - as long as you can provide necessary information on wodImapServer's request.

Related software: wodimapserver, component, mail, server, encrypted, secure, security, protocol, ssl, …

ActiveX Component that implements server side of following protocols: FTP, FTP/S (FTPS or FTP+SSL) both in explicit and implicit modes, and SFTP (secure ftp subsystem on SSH2 secured channel).
Support for all 3 protocol is transparent for your programming - you have same set of events, same set of properties and methods, same control over connected users - and just one property to change to switch from one protocol to another - Protocol property!

Unlike old FTP protocol support, FTPS and SFTP protocols provide security, privatekey/certificate authentication and strong encryption of data - great for insecure networks. wodFTPServer can be easily setup (using provided samples) to listen and accept such clients.

Features include

support for FTP, SFTP and FTPS protocols
support for certificate and privatekey authentications (required or optional)
set of events to control every aspect of client's connection - when he changes directory, lists directory contents, downloads file....
support for large files (larger than 4.2gb)
transparent interface - interface is the same for all supported protocols
debug log showing entered commands and replies sent to the user (in SFTP protocol wodFTPServer creates these messages for you!)
NT style authentication - you don't need to create accounts on your server at all, use users registered on your NT system
great speed
complete information on connected users - get their originating IP address, originating port, total connected time...
custom initial messages sent to the client - you can hide WeOnlyDo! origin completelly
easy interface - almost to say 'plug and play'

wodKeys component is included in our setup package free of charge. It can be used for private key management - to Generate new keys, Load/Save the, obtain public keys etc..

Related software: weonlydo, ftp, sftp, server, avtivex, security, protocol, general, ftp/s, ssl, …

Lightweight component that provides strong encryption for your applications. It provides supports for most common crypto algorithms, such as
AES
DES, TripleDES
Blowfish
Cast
RC2
RC4
RC5
for symmetric encryption and decryption,
RSA
DSA
for making and verifying signatures, and
MD5
SHA1
for creating hashes.

Working with Blobs

wodCrypt works with Blobs - Binary Large Objects (it doesn't have to be big, of course) when it comes to data manipulation. Blob is our object that can read files, string variables and bytes array, and provide the same as their output. Even more, it can present the information in BASE64 and HEX encoded data - in case your environment just doesn't like to work with binary data.

Optimized code

Besides working in regular way - without random padding and internal wrapping, wodCrypt can work in Optimized mode as well. In that case most probably no other encryption tool will be able to access (directly) your encrypted data - because wodCrypt will add specific information to it - such as size of blob. This way when decryption is done, you will get exactly the same plaintext as it was before encryption. In regular way, wodCrypt has to look after block sizes for each protocol, key sizes etc.. so any empty space needs to be filled with zeros. It's not smart way to protect the data - but it's necessary to make encrypted text open to other decryption tools, for you to get the results as expected.

Licensing - royalty free

wodCrypt is royalty free - once you make your application, you can distribute binary versions of wodCrypt free of charge. Licenses are purchased only for design-time development, one license per each developer on the project - and that's all!
Besides ActiveX version (which can be used even in FoxPro), wodCrypt has COM object as well, which can be used from many environments, such as VB, VC, Delphi, VBS, ASP etc..

Related software: weonlydo, wod, crypt, component, activex, security, encryption, …

ActiveX component is a peer-to-peer connection convenient to label each peer to behave in context of Listener(Server) or Initiator(Client). Component comes with several profiles included such as: SINK/ECHO profiles for testing, ROT13 profile that will grap message data, ZIP Tuning profile that will compress cocntents of messages on the fly, SYSLOG Raw and Cooked profiles for transmitting (and recieving) syslog messages....

BEEP protocol is a generic application protocol for connection oriented, asynchronous interactions. It permits simultaneous and independent exchanges within the context of a single application user-identity.
It supports both textual and binary messages.

BEEP peers communicate with MESSAGES over predefined CHANNELS. Messages are generated by application defined PROFILES. Before message is sent, and once message is recieved by the peer, Profile defines parsing to provide necessary information.

MESSAGES
Messages are initiated by application, and are prepared by defined Profile. Corresponding profile awaits on other side to parse the message and provide only necessary information.

CHANNELS
All exchanges occur in the context of a channel -- a binding to a well-defined aspect of the application, such as transport security, user authentication, or data exchange.

PROFILES
Each channel has an associated "profile" that defines the syntax and semantics of messages exchanged. Implicit in the operation of BEEP is the notion of channel management. Except for few profiles defined internally in wodBeep you can define your own profiles: for data exchange, tuning parameters etc...

TRANSPORT
A BEEP session is mapped onto an underlying transport service. It can be single TCP connection, but also UDP or any higher level two-way transport service-SMTP arhitecture... wodBeep implements TCP transport for you - you can implement easily any other transport just by implementing IBeepTransport interface!!

Related software: wodbeep, beep, weonlydo, peer, communicate, secure, security, protocol, connection, asynchronus, …