Board index » delphi » RTC and C4D

RTC and C4D


2007-11-21 07:22:16 PM
delphi46
Hello,
this bad thing with ThinDac and RO brought at least
a very positive thing:
The new partnership RTC + C4D.
Two componetns companies there i can really trust,
and they have an excellent support.
Delphi + RTC + C4D + Firebird SQL + IBO will be an unbeatable
combination for big, stable and fast Webapplicationservers.
I am glad for this new possibilities.
br
Gerhard
 
 

Re:RTC and C4D

Tiger writes:
Quote
I would replace IBO with UIB, then everything becomes perfect.
I would replace three vendors RTC + C4D + IBO with only one: RO.
Perfectness is subjective. :)
--
Erick Sasse
 

Re:RTC and C4D

I would replace IBO with UIB, then everything becomes perfect.
William
"prom" <XXXX@XXXXX.COM>writes
Quote
Hello,

this bad thing with ThinDac and RO brought at least
a very positive thing:

The new partnership RTC + C4D.

Two componetns companies there i can really trust,
and they have an excellent support.

Delphi + RTC + C4D + Firebird SQL + IBO will be an unbeatable
combination for big, stable and fast Webapplicationservers.

I am glad for this new possibilities.


br
Gerhard
 

Re:RTC and C4D

Uffe Kousgaard writes:
Quote
With C4D you can also choose RTC, Indy, Synapse etc. And instead of
IBO there are also IBX, Zeos, SQLdirect, FIB, IB5, UIB etc.
With RO you can also use all these technologies except, of course, RTC.
--
Erick Sasse
 

Re:RTC and C4D

"Erick Sasse" <XXXX@XXXXX.COM>writes
Quote

I would replace three vendors RTC + C4D + IBO with only one: RO.
Perfectness is subjective. :)
Known as the "put all your eggs in one basket" strategy :-)
With C4D you can also choose RTC, Indy, Synapse etc. And instead of IBO
there are also IBX, Zeos, SQLdirect, FIB, IB5, UIB etc.
 

Re:RTC and C4D

Kim Madsen writes:
Quote
just to mention a couple of things.
I didn't say it wasn't a great product.
--
Erick Sasse
 

Re:RTC and C4D

Basically you only need C4D and CG.
However you can choose to use RTC+C4D when the required binders are
released.
That will make the life easier for ex-thinDAC users, and will thus provide
the technical functionality of RTC SDK underneath, which some people prefer
over for example Indy or other communication libraries.
But lets not forget that the database API layer and the transport are only
some pieces of kbmMW.
You will for example also find (depending on edition):
- Application server technology
- Advanced loadbalancing technology
- Advanced failover technology
- Advanced publish/subscribe messaging technology with unsurpassed features
- Advanced multi database transaction handling
- Support for resolving complex queries including multi table and multi db
joins.
- Native integration with PHP
- Native integration with C
- Native integration with Java
- Native integration with .Net incl. Compact Framework.
- Native integration with Office
- Advanced scriptable management console and configuration repositories
not to mention the 30+ database APIs that kbmMW currently supports.
just to mention a couple of things.
--
best regards
Kim Madsen
XXXX@XXXXX.COM
www.components4developers.com
www.myc4d.com - Your access to cool code
blogs.myc4d.com - Your access to code tidbits and comments
The best components for the best developers
Application server enabling technology for developers
"Erick Sasse" <XXXX@XXXXX.COM>skrev i en meddelelse
Quote
Tiger writes:

>I would replace IBO with UIB, then everything becomes perfect.

I would replace three vendors RTC + C4D + IBO with only one: RO.
Perfectness is subjective. :)

--
Erick Sasse

 

Re:RTC and C4D

Uffe Kousgaard schrieb:
Quote
"Erick Sasse" <XXXX@XXXXX.COM>writes
news:47447245$XXXX@XXXXX.COM...
>I would replace three vendors RTC + C4D + IBO with only one: RO.
>Perfectness is subjective. :)

Known as the "put all your eggs in one basket" strategy :-)

With C4D you can also choose RTC, Indy, Synapse etc. And instead of IBO
there are also IBX, Zeos, SQLdirect, FIB, IB5, UIB etc.


Thank you Uffe, i never heared from IBX, Zeos, SQLDirect, FIB, IB5, UIB etc.
lol
There are many good softwarecomponents on market, and as an application
developer i decided to use this or that. I have also bought a lot of them.
Thank you all, component developers!
You are an important part of the success of Borland Delphi,
And i wish CodeGear the best to have success in future.
(And i also hope CodeGear goes back to a usable IDE like Delphi7, lol)
They have not to do clones from M$ IDEs, i work also with
Microsoft C# 2005, and .... i am so happy, if i can start
Delphi 7 again, there i am at home.
Perhaps, there comes Delphi 2008 with a IDE thats Delphi 7 near and that works
also for Linux, let me dream on ... LOL
Since Vista is on market, i hear form many customers (in Europe, not in
the USA), they give Linux now a try (OpenOffice some of them uses now as
primary office solution on Windows, and soon on Linux workstations).
Therefore i integrated now OpenOffice in my import and export solutions
with Delphi.
now ..
1) RTC
I like the conecpt of RTC and the really stable working, i have some
1000lines of code now written with RTC and i am
fully satisfied, have no reason to change.
RTCWebApplicationservers running for months as service without issues.
I also like and use the RtcPHPProvider, is easy to handle.
E.G. i let run collecting data form 5 different databases in a business
logic class i have written, and, with a weblcient i can realize online
reports that produce with rtcremotefunctions php pages as output with
flash animated charts, based on this perpared data.
You will say now: others have also this, of course, there a many
good components and i hope they grow and exists for a long time ...
2)IBO and Firebird
For do this job, i could also realize a db-pool with IBO and 5 different
firebird database servers behind. All in multithreading and service mode
and stable.
Here comes the point, what other component can handle this? Perhaps
there are more as i think, but I have not the time to test others.
Some years ago i have to change from BDE to another
thing, as i had more as 256 fields in one table, BDE crashed.
At first i used IBX, but was not really happy with it.
Therefore i changed to IBO that was the best solution with Interbase
at this time for me. And i am happy with IBO and Firebird till now. Why
shall i change it? Who pays the manmonths to change to another tool?
3)ThinDac
I have written 100.000 lines of code of classic client/server software.
Since Delphi 1.0 i am woking with Delphi.
(before: Fortran77, DecForms, DecPascal, C++, and some others like ADA)
To change such an old fat classic client/server application to a
webclient with ThinDac i could do following:
1) drop a RTCHttpClient on the form
2) drop a RtcClientModule on the form
3) drop a TdClient on the form and set all parameters
4) open delphi-form as Text with a texteditor:
- search and replace: TIBOQuery with TDQuery
5) open xxxx.pas with texteditor: search and replace TIBOQuery with TDQuery
6) save all, open project and compile
READY, now the classic client/server client is a webclient.
Of course not optimizid, the conecpt for a webclient is another one
as a fat classic client/server application.
But it works as a first step much more better using on 2 mbit networks.
I could write here long stories, also my experience with Indy,
(I have to realized a FTPS Client with Indy, what a nightmare, have to
change Indy code, and loosed nearly my last hair)
But i think nobody will read such stories. LOL
br
gerhard
 

Re:RTC and C4D

"prom" <XXXX@XXXXX.COM>writes
Quote
Thank you all, component developers!
You are welcome, I am one of them :-)