Description

ALMailSlot is a component which allows applications to communicate across a network using mailslots.

Informations

• Status: Fully functional
• Source: Included
• Size: 6kB

Platforms: D2, D3, D4, D5, D6, D7

Description

This component set implements a Modbus master and slave component to communicate via Modbus over TCP/IP. The components are based on the Indy components included by a standard Delphi installation. Demo sources are included to show implementation of both a Modbus master and a Modbus slave.

Informations

• Status: Fully functional
• Source: Included
• Size: 432kB

Platforms: D2005, D2006, D2007, D2009, D2010, D5, D6, D7, DXE, DXE2, DXE3, DXE4, DXE5, DXE6

Description

Growl Notification is Class to send notifications to the popular MacOS Program "Growl".

It uses Indy 10 and MD5.pas.

Informations

• Status: Fully functional
• Source: Included
• Size: 5kB

Platforms: D1, D2, D2005, D2006, D3, D4, D5, D7

Description

Includes three components that provide send / receive data for interprocess comunication, either in a standalone computer or within computers in a Windows Network.

Informations

• Status: Fully functional
• Source: Included
• Size: 29kB

Platforms: D3, D4, D5, D6, D7

Description

NTLM Class Authentication. This class is very simple, it has 3 Methods: GetMessage1, GetMessage2 and GetMessage3.

• GetMessage1 is the first message with the host and domain name
• GetMessage2 returns a TNTLM_Message2 with Nonce string
• GetMessage3 is the last message with Host, Domain, User, LM_Hash and NT_Hash.

Informations

• Status: Fully functional
• Source: Included
• Size: 8kB

Platforms: D5, D6, D7

Description

Remote procedure call (RPC) is a technology that allows a computer program to cause a subroutine or procedure to execute in another address space (commonly on another computer on a shared network) without the programmer explicitly coding the details for this remote interaction. That is, the programmer would write essentially the same code whether the subroutine is local to the executing program, or remote. When the software in question is written using object-oriented principles, RPC may be referred to as remote invocation or remote method invocation. All communications is transparent for developer. You need write code like for local object. You don�t see differences between local and remote objects.

Routix software develop own RPC technology known as Routix.RPC. This technology based on TCP-transport and XML-packets (messages). Our technology differs from other implementations in the high speed of calls, ease of use, support of callback-objects.

Features:

• support any objects with IDispatch (Automation, ActiveX);
• username/password authentication;
• objects request control (possible to block object creation);
• support any programming languages with COM support (VBScript and Delphi examples included);
• Can be licensed with Delphi source code;
• communications compression and encryption;
• high speed of calls;
• support creation of multiple remote objects via single connection;
• support callbacks;
• XML-based protocol can be easy extented;
• multithreading with automatic synchronization of calls;
• structure of objects detected at runtime dynamically, no need recompile RPC engine if objects changed;
• supports any Microsoft Windows version;

You can use special COM-objects (RoutixRPCServer.dll and RoutixRPCClient.dll) or compile directly in the your software (if source code purchased). Multithreading supported: you can create multiple objects over single connection and use each object with own separated thread, Routix.RPC serialize all calls automatically.

Note: if you want use one object in the multiple threads - you must synchronize calls. You can use Routix.RPC with any programming languages that supports COM technology. Client and Server can be used with any Microsoft Windows version.

Routix.RPC can be used in distributed N-tier applications, service-console applications, remote management software. Routix NetCom console uses Routix.RPC for remote service management for example.

Informations

• Status: Partially restricted
• Source: On purchase/registration
• price: $299.95
• Source price: $899.95
• Size: 1 373kB

Platforms: C2k6, C2k7, CB1, CB4, CB5, CB6, D2005, D2006, D2007, D3, D4, D5, D6, D7

Description

Features:

• TCP/IP Server, TCP/IP Client Component, (Server and Client Component working unblocking mode)
• UDP Component,
• ICMP (Ping) Component, (Without ICMP.dll, direct using Winsock library)
• ARP (Address Resolution Protocol) Windows Table Management,
• Easy To Use:
• TCP Srv. Start => TdTCPServer1.Start;
• TCP Srv. Stop => TdTCPServer1.Stop;
• TCP Client Connect => TdTCPClient.Connect;
• TCP Client DisConnect => TdTCPClient.DisConnect;
• From TCP Srv, Client DisConnect => TdTCPServer1.Disconnect(ClientSocket);

Informations

• Status: Demo only
• Source: On purchase/registration
• price: $100
• Source price: $200
• Size: 1 091kB

Platforms: D2006

Description

With this component you can communicate between processes either on the same machine and/or across different machines. The component runs under all Windows operating systems giving you the ability to communicate with a wide variety of different machines across a LAN. It also gives the ability to do point-to-point and broadcast messaging. It is very simple to use, you can create a program that sends and receives messages over a LAN in just four lines of code.

Informations

• Status: Fully functional
• Source: Included
• Size: 5kB

Platforms: CB3, CB4, CB5

Description

Mailslot component. Local Network data exchange.

Informations

• Status: Fully functional
• Source: Included
• Size: 8kB

Platforms: CB3, CB4, D2, D3, D4

Description

The mdMailSlot component package gives different ways to communicate via mailsots in Delphi. The package contail generic mailslot, WinPopup compatible and a "secure mail" communication component.

Informations

• Status: Fully functional
• Source: Included
• Size: 17kB

Platforms: D2, D3, D4