[fpc-pascal] 3-tier database applications with FPC

Graeme Geldenhuys graemeg.lists at gmail.com
Wed Oct 19 13:25:05 CEST 2011

On 2011-10-19 11:36, michael.vancanneyt at wisa.be wrote:
> Out of the box: no.

OK, thanks. Do you know if TClientDataset has improved at all?

> Midas is written in C++, so that's not going to happen.

I didn't know that.

> OTOH the web-development part has resulted in a ready-to-use packet transport 
> layer. It's inefficient though, since it uses JSON or XML, but that can
> easily be adapted to support a 'binary' packet.

I just finished watching a CodeRage 5 Datasnap demo. The guy said that
XML packet transport is extremely slow (because XML is generally hard to
parse). Simply changing to CSV packet format gave a 20x speed
improvement, but obviously CSV is not self-describing.

Is parsing JSON any faster than XML?  Sorry if this is a stupid
question, but I know near zero about JSON.

OK, so it seems worth my while to port the tiOPF Remote Persistence
Layer to FPC+Synapse (or maybe lNet) then. Based on an old message from
Peter Hinrichsen, tiOPF can take care of everything for me, without 3rd
party components or libraries, including some state information. He also
mentioned that [at the time of his message] it was well unit tested and
already used for 4 years in a production environment. The current tiOPF
Remote Persistence Layer uses Indy's HTTP client & server components and
has two data packet formats it supports (one being more compressed).
I'll dive into that code then and see what I can manage with FPC.

  - Graeme -

fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal

More information about the fpc-pascal mailing list