Recent

Poll

Which is best in your opinion?

LNet
0 (0%)
Synaspe
4 (100%)

Total Members Voted: 4

Voting closed: July 03, 2010, 12:25:28 pm

Author Topic: Networking Component  (Read 11366 times)

Jishaxe

  • Full Member
  • ***
  • Posts: 103
  • Hobbist Programmer
Networking Component
« on: June 28, 2010, 12:25:28 pm »
What do you think is better?
Linux Mint 12
Windows 7 Home Premium
______________________
Definition of programmer: An organism that converts caffeine into software.

theo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1927
Re: Networking Component
« Reply #1 on: June 28, 2010, 03:19:03 pm »
I think you can't answer this by a simple poll.
lNet is well integrated with Lazarus and should work on most platforms afaik.
Afaik it's also "event driven" (I know only little about it).

Synapse is very well tested (many years for Delphi and Kylix) and works on Windows and Unices without problems. There are some issues with OSX and WinCE afaik.
Synapse is more for the programmer who whants to know what's really happening.
It has some "convenience" functions but beyond that, it's leaving decisions about when to use threads etc. up to you.

I for one would use lNet or Indy for "quick and dirty" programming.
I would always choose Synapse for writing a performant/scalable server.

Jishaxe

  • Full Member
  • ***
  • Posts: 103
  • Hobbist Programmer
Re: Networking Component
« Reply #2 on: June 28, 2010, 09:43:44 pm »
Thanks for your explanation.
Linux Mint 12
Windows 7 Home Premium
______________________
Definition of programmer: An organism that converts caffeine into software.

OpenLieroXor

  • New Member
  • *
  • Posts: 38
Re: Networking Component
« Reply #3 on: June 28, 2010, 11:40:08 pm »
lNet is much easier to use because of event handlers, built-in threading, and LCL components implementing lots of operations on sockets. However, it has very basic functionality and, for me, it's usable only for very simple communication. Synapse is the most powerful network library, which allows you to take much better control over your sockets, but it's harder to use - you need to know a bit how the network sockets work, and you need to code in your own a lot of things done automatically by lNet, like threading, etc. When I began network programming with Delphi, I used TServerSocket and TClientSocket components, so when I moved to Lazarus I began to use lNet, because it was very similar to my old components. But later such 'all-in-one' network components weren't functional enough for me, so I learned Synapse. Now I use Synapse in every project.

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 11567
  • FPC developer.
Re: Networking Component
« Reply #4 on: July 05, 2010, 12:14:32 pm »
Well, Indy10 obviously.

Leledumbo

  • Hero Member
  • *****
  • Posts: 8761
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: Networking Component
« Reply #5 on: July 05, 2010, 01:34:14 pm »
LNet for me. I don't want to know what a library does to do what I want. In fact, this is why a library is created so you can focus on your application only.

JD

  • Hero Member
  • *****
  • Posts: 1848
Re: Networking Component
« Reply #6 on: July 05, 2010, 03:30:37 pm »
Indy 10 even though there are reports that it has some problems in Linux & MacOS. It has all the protocols one could possible want.

The proof for me is the fact that it is bundled with Delphi 2010.
Windows - Lazarus 2.1/FPC 3.2 (built using fpcupdeluxe),
Linux Mint - Lazarus 2.1/FPC 3.2 (built using fpcupdeluxe)

mORMot; Zeos 8; SQLite, PostgreSQL & MariaDB; VirtualTreeView

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 11567
  • FPC developer.
Re: Networking Component
« Reply #7 on: July 05, 2010, 09:54:31 pm »
Indy 10 even though there are reports that it has some problems in Linux & MacOS.

I tested some versions on Linux and OS X (PPC even) and it worked for me. (mostly ftp client, pop/smtp and httpclient).

The reports were not awfully detailed, and I have no time to hunt this down myself.

That said, I know the 64-bit side of things didn't receive that much testing, and the recent Tiburon branch broke the designtime packages.

Jishaxe

  • Full Member
  • ***
  • Posts: 103
  • Hobbist Programmer
Re: Networking Component
« Reply #8 on: July 07, 2010, 11:55:56 am »
Indy? I thought that was only for Delphi...
Linux Mint 12
Windows 7 Home Premium
______________________
Definition of programmer: An organism that converts caffeine into software.

ahmetnurideniz

  • Full Member
  • ***
  • Posts: 110
  • As you sow, you shall reap.
    • Big Student Web Site
Re: Networking Component
« Reply #9 on: August 16, 2010, 05:40:17 am »
is indy free for lazarus?

typo

  • Hero Member
  • *****
  • Posts: 3051
Re: Networking Component
« Reply #10 on: August 16, 2010, 06:41:21 am »

 

TinyPortal © 2005-2018