LNet

This is an old revision of LNet, edited by Almindor at . The current revision is 14133.

0.5.1 news

About

lNet or LightWeight Networking Library is a collection of classes and components to enable event-driven TCP or UDP networking. lNet is released under a modified LGPL license. (permits static linking)

The package consists of base lNet units library, lTelnet for telnet protocol, lFTP for ftp protocol and lNetComponents libraries for providing visual and non-visual components for networking. As of 0.4.0 lHTTP and lSMTP components have been added. Since 0.5.1 there's a MIME support as part of the library mainly for creation of multipart messages for SMTP.

The non-visual console components were tested on Win32, Win64, Linux_x86_32, Linux_x86_64, Linux_PPC, Linux_PPC_64, FreeBSD_x86_32.

The visual (lazarus packages) components were tested in Win32, Linux_x86_32 and FreeBSD_x86_32.

Since 0.5.1 WinCE is considered an unstable but supported platform.

Homepage of the lNet base libraries is: http://members.chello.sk/ales (this site is main resource however)

As of version 0.3 the package is only single-threaded. I've dropped multithreaded version and now use exclusively LCL features to work.

As of version 0.4 the package has "eventers" which enable per-OS optimalizations and additional flexibility including watching for events on files additionaly to the sockets.

Version 0.5 changed some high level higher protocol API (ftp, http etc.)

Authors

Ales Katona (User: Almindor)
Micha Nelissen

License

Modified LGPL (read LICENSE and LICENSE.ADDON included in package).

Contact

You can contact me directly by email or go to #lnet channel on freenode.

News

1st of June 2007:

Released 0.5.1 according to schedule. New stuff:

This release has been mainly concentrated on the MIME support, the other issues are bug fixes and/or maintenance.

14th of April 2007:

Released 0.5.0 not according to schedule. New stuff:

This is mostly a bugfix and stabilization release. Many planned features got dropped until we got something we felt right with. Sorry for the delay as well but school was keeping me quite occupied lately.

Download

Change Log

Status

* FTP and Telnet still need some additional features like authentification methods.
** SMTP still needs proper MIME support for encoding attachments, but API should only grow from now on.

Roadmap

Dependencies / System Requirements

LNet 0.5+

LNet 0.4

Installation

LNet 0.5+:

NOTE: users who don't want to depend on LCL but use LNet in Lazarus (non-visually), can just compile lnetbase.lpk, which adds all the base units to path.

LNet 0.4:

NOTE: older lNet is extraced to "lnetpackage" dir. Since 0.4.0 the "visual" and "non visual" packages are in one distribution file.

Ubuntu special notice

On Ubuntu lazarus components folder is "/usr/lib/lazarus/components". You must copy the lNetpackage in this folder and unzip in this folder to generate lnetpackage folder.

On this distribution your may have issues if you don't use the root account because you won't have writing rights on this folder... Activate the root account management and log in with the root account before doing any operation.

Some "missing files" are, in fact, in the "/net" subfolder and are not found by the fpc compiler. Simply copy missing files from the subfolder (lnet.pas, tomwinsock.pas, lfunc.inc...) "/usr/lib/lazarus/components/lnetpackage/lnet" in the "/usr/lib/lazarus/components/lnetpackage" folder. Then complete the setup by following the installation procedure.

by Steph12358

Documentation

Documentation of lNet is partially done.You can also use Jesus' diagrams of classes and units as basic reference.

Documentation of eventer and TCP/UDP protocols: http://members.chello.sk/ales/docs

Overview diagrams can be found here: http://members.chello.sk/ales/docs/diagrams/overview.html
Pictures: All classes lNet units lNet units 2

Usage

TCP/UDP

Drop a TLTCPComponent or TLUDPComponent on a form. Assign OnAccept, OnError, OnReceive, OnConnect and OnDisconnect event handlers. Note that this is optional but in most cases required for functionality.

Client connection is initialized with the Connect call. Arguments are IP address/hostname and port respectivly. Non-blocking connect is used, this means that you DON'T know that you're connected until OnConnect event is fired.

Server connection is initialized with the Listen* call. Argument is port.

Note: address is a string representation of IP eg: '127.0.0.1' or a hostname like 'localhost'.

Sending data to the other side is accomplished with the Send/SendMessage method.

Events of TLNetComponent class.

API changes

0.1 to 0.2 There have been some API changes from 0.1 to 0.2. These were required and should improve the usability of packages. I know API changes are always a PITA but I'll try to keep them minimal from now on. Version 0.3 will be the first beta from which API will remain unchanged (only adding new stuff will be possible).

0.2 to 0.3

0.3 to 0.4 Lots of additions. Only "breakage" is that TLSocket.Port got changed into TLSocket.LocalPort and TLSocket.PeerPort for consistency reasons.

0.4 to 0.5 We did some API cleanup which resulted in API breakage.

WARNING: In version 0.4.0, I forgot to move lHTTPSettings unit from lib to the http example. It was NOT supposed to be a part of the library, just the example. DON'T use this, it's not a "library", it's a part of the example (http server will get it's own project later)