BorlandTalk.com

Danijel Tkalcec · Guest

RealThinClient is a set of easy-to-use components for writing
internet-enabled applications using any Delphi version (even the personal
edition) and BCB. No other components are needed. It even comes with a
ready-to-use WebServer implementation comparable to Appache, supporting
PHP5.

RealThinClient Core 1.x components - commercial license with full source
code for Delphi and BCB = 95,- EUR
Check www.realthinclient.com for more info.

With this purchase, you get 1 year first-hand techical support with all
minor updates and bug fixes.
As a licensed RTC user, you can define the way RTC will be evolving in the
future.

RealThinClient Core now contains

* RTC Core Server components:
- TRtcUDPServer
- TRtcTCPServer
- TRtcDataServer
- TRtcDataServerLink
- TRtcDataProvider
- TRtcServerModule

* RTC Core Client components:
- TRtcUDPClient
- TRtcTCPClient
- TRtcDataClient
- TRtcDataClientLink
- TRtcDataRequest
- TRtcClientModule

* RTC Core Remote Function components:
- TRtcFunction
- TRtcFunctionGroup
- TRtcResult

* RTC Core Value objects:
- TRtcValue
- TRtcArray
- TRtcRecord
- TRtcDataSet
- TRtcFunctionInfo

Some information about RTC Core components:
----------------------------------------

* Complete package: You don't need to buy the Enterprise version of Delphi
or BCB, nor upgrade to the latest Delphi/BCB version to use RealThinClient
components. All RTC components compile with standard editions of Delphi and
BCB, starting from Delphi 4.

* True RAD: Everything you do with RTC is component-based, while all the
code you will ever need to write is defined as events, so you can truly
design your server and your client applications, without the need to use
wizzards or code your interfaces.

* Multi-Threading: A very sophisticated Threading mechanism is built into
all RTC Connection components, which allows thousands of active connections
to be running in separate threads, all at the same time. And the only thing
you need to do is change a simple MultiThreaded property to True. Then, any
newly received connection will be handled by a thread pooling mechanism
which saves valuable System resources, while enabling nearly unlimited
number of symultaneous connections at the same time.

* Uses Proxys: Data Clients will never have to be specialy configured to get
through corporate firewalls to reach the server. Simply by setting the
UseProxy property to True, DataClient connection will use a connection
provider which uses the same settings as Internet Explorer for browsing the
Web. This means that Clients can work in any corporate LAN and have full
access to the internet.

* Non-Blocking: Other than most other internet components, RTC connection
components are non-blocking and event-driven. This means that, even when not
using a multithreaded mode, your users will not be blocked ("Application Not
Responding") during communication between your client and the server. For
each state change in the connection, there is an event that will be
triggered.

* Remote Functions: Implementing and using remote functions is as easy as
writing local functions. You just place a RtcFunction component on your Form
or a DataModule, set function name and write your OnExecute event. OnExecute
event receives the Connection object, Function Parameters and a Result
object. You just have to use the parameters passed to the function to
prepare the result. The rest is done "under the hood" by RealThinClient
components.

* Strong Encryption: RTC components offer easy-to-use strong encryption with
Encryption Keys of variable length. And you don't even have to think about
the keys to use, they will be generated and maintained for you. Also, for
remote functions, it makes no difference wether function parameters and
result are transmitted using a secure encrypted connection or just plain
text, it is marely a parameter you define for your Server- and Client-Module
components.

* Use/Write Plug-Ins: All Client and Server code you write using RTC Core is
ready to be used as building blocks or plug-ins in any application that uses
RTC Core. For example, you can combine a WebServer, Messenger server,
Application server, Database server and your own functions in one Data
Server, even when those components weren't specialy designed to share the
same Server space. Because of the easy-to-use plug-in framework on top of
which all RTC Components are built, you can link unlimited number of
functionality and data providing components like DataProvider, ServerModule
and/or DataLink to one DataServer, enhancing that server's functionality
with each new component. And by keeping code in separate units
(DataModules), you can even provide your own plug-ins (and sell those
plug-ins) to anyone who uses the RTC Core Library.

* Small footprint: A complete WebServer implementation, using RTC Core
components, is less than 600 KBytes when compiled with D7. Even though it is
so small, it offers enough functionality with great stability and
scalability.

For more information on RealThinClient components, check:
www.RealThinClient.com
(powered by the RTC DataService)

Best Regards,
Danijel Tkalcec

Ted Nicolson · Guest

Last year, many Delphi developers including myself, paid a hundred bucks,
for your previous project (Remote Tools). Three months later you sold code
rights to another company leaving your own registered clients without
updates or bug fixes.
Instead that, you asked them to promote and advertise this new company just
to have access to new source.

And now you believe that we gonna spent more money for your new "efforts" ?
What a joke !

Ted

Nick Rollas · Guest

I second that.
You left the Remote Tools project with lot of missing features and LOT of
bugs.

I agree Ted, what a joke !

Nick

"Ted Nicolson" <no (AT) email (DOT) pls> wrote

Keith Blows · Guest

Nick Rollas wrote:

I'll third that!

Most disappointing turn of events.

Regards,
Keith Blows

Danijel Tkalcec · Guest

Sorry guys, but that is simply not true.

1.) I still support all licensed Remote Office users (check
www.realthinclient.com forum, it still has a RemoteOffice section) and if
anyone had any questions regarding Remote Office, they contacted me directly
and we solved the problems.

2.) There are quite a few Remote Office users who are more than happy with
Remote Office and use it on a daily basis to support their customers. The
only "problem" is that only the trouble-makers stand up and scream out loud,
while happy customers mind their own bussiness. Some of those happy
customers added features to their Remote Office version and created
comemrcial products based on Remote Office, which you can also find in this
newsgroup.

3.) RealThinClient code has nothing to do with RemoteOffice. RealThinClient
has a completely new code base, which I have been working on the past 6
months. RTC is fully component-based, has detailed help (also available as
Web Help), demo applications that show you how to use each component (which
includes a fully functional WebServer) and a Quick-Start guide, which I will
be enhancing with visual presentation guides.

Anyway ... if you have questions about RemoteOffice, you can still contact
me directly (or post questions to the RTC Forum at [url]www.realthinclient.com)[/url].
I will be more than happy to help you.

Best Regards,
Danijel Tkalcec

prom · Guest

Hi,

i use Remote Office, and are very happy with it.
With Remote Office i could realize a nice and good working
support software for my customers, and it works perfect!

And if i need help, i can write to the developer and get
quickly answers.

As i bought Remote Office i got the sourcecode and a well working
example. Thats all what i expect from good vcl-components.
AND i couldn't find bugs.

It' not a new thing, that VCL-components change owners and companies.
This happens often.

best regards
Gerhard Knapp

prom · Guest

Hi,

i use Remote Office, and are very happy with it.
With Remote Office i could realize a nice and good working
support software for my customers, and it works perfect!

And if i need help, i can write to the developer and get
quickly answers.

As i bought Remote Office i got the sourcecode and a well working
example. Thats all what i expect from good vcl-components.
AND i couldn't find bugs.

It' not a new thing, that VCL-components change owners and companies.
This happens often.

best regards
Gerhard Knapp

Jonathan Neve · Guest

Hi Ted,

I was also (and still am) a user of RemoteOffice, and I don't agree with
your statements.

I do realise of course, that Danijel made a bit of a commercial mistake
with RemoteOffice, and I can understand that you would be disappointed
with the way things turned out. However, I don't see why that should
make you so bitter against him, nor why you should try to defame his new
product because of it.

I really think you're exagerating, because:

a) You paid a very moderate price, and what you got was well worth the
price, considering that you have the full source code. You are therefore
completely free to do what you like with it. Obviously, this isn't as
good as having Danijel continue working on improving it, but surely it's
better than being left stranded without even the source code.

b) The product you now have works fine. If it's missing some features,
you can always add them, but even as it is, it's quite adequate for a
lot of people. For example, all I changed in my version is the user
interface.

c) As Danijel stated, there is still support for RemoteOffice. The only
"problem" is that Danijel is no longer adding features.

d) If you really needed new features, why didn't you accept the
Acclimate partner agreement. I know, it was a bit complex, and over all,
a surprising way of doing things. But at the end of the day, it wasn't
that bad. If you can get the full source code and updates for merely
partnering with Acclimate to some extent, that's even cheaper than
RemoteOffice ever was. Of course, if you wanted to produce a commercial
application based on the source code, that wouldn't have been possible.
But in that case, staying with RemoteOffice was still possible.

e) I find it perfectly understandable that someone may sell his product
to a third-party, and that that third-party may not choose to
commercialise it in the same way as before. Danijel didn't break the
licence agreement you had agreed to in any way, because if you didn't
like the new terms, you were allowed to stay with the old agreement.

f) RealThinClient has nothing to do with RemoteTools.

g) Danijel's a nice guy, he just made a commercial mistake. Please stop
trying to give him a bad name for all his future developments.

Regards,
Jonathan Neve.

Ted Nicolson · Guest

Tim Shields · Guest

I was also quite disappointed about the turn of events.

However, as we use the software everyday and I can honestly say that
our company could not function with out his software I got over it
pretty quickly!

Oliver Feins · Guest

Hi Danijel,

Danijel Tkalcec · Guest

You can't say that I have left Remote Office users on the street. There were
several possibilities for every licensed Remote Office user after the
copyright transfer. If you were one of them, you would have known that.

1.) You could have partnered with Acclimate and get access to their
Support-Bridge (new Remote Office) with all future upgrades at no cost
(totaly free). This agreement might have been confusing, but the only thing
they asked for is that you don't go and create a competing product (meaning:
sell Support-Bridge as your product), which is understandable, since they
are doing all the upgrades and the coding.

2.) You could continue using the source code as it was, or make some minor
interface changes (different language, reorder buttons, add your remote
functions), which is pretty easy, considering the fact that you had the full
source code, all components were on a standard Delphi form and everything
was working just fine as it was. And if you should get stuck, there was
always the possibility to contact me for support.

3.) There were no known bugs (as you would like to present here) in
RemoteOffice source code, it worked fine (still does). After RemoteOffice
became Support-Bridge, there was not a bug-fixing needed in the RemoteOffice
core library. The only thing that was done is a new interface (polish the
thing a bit), encrypted communication and a gateway option.

In any case, I was offering full support to all RemoteOffice licensed users,
wether they chose to continue using the original code or partner with
Acclimate. I still am doing this, as good as I can, but you have to say if
you have a problem, I can't baby-sit you. I didn't hide, nor dissapear.
Whenever someone contacted me or posted a query on the forum, I helped them
out (but there were not a lot of such queries, since everything worked fine
as it was). And my E-Mail address is still the same as before (check the
copyright notice at [url]www.realthinclient.com)[/url]. So, I can't understand why
you're crying out loud that I left you on the street. If you have a problem
with RemoteOffice, what is stopping you from contacting me directly or using
the Support Forum? RemoteOffice forum was open and I was there all the time.

And last but not least, would you please state your real name? "Ted
Nicolson" did not license a copy of Remote Office (never did), nor had
anyone named "Ted" or "Nicolson" ever try to contact me anytime in the past
2 years (guess what, I also keep track of all my E-Mails). For all I know
(especially since you are using a fake E-Mail address), you are just someone
who doesn't want RealThinClient to take off. And your statements like "get a
real job!" may only prove that I'm right. Well, I wish you all the luck in
your actions, I'm not taking part in this sharede anymore.

Best Regards,
Danijel Tkalcec

"Ted Nicolson" <no (AT) email (DOT) pls> wrote

Danijel Tkalcec · Guest

Hi Oliver,

Danijel Tkalcec · Guest

One more thing :)

Judging by the reactions of some people here, someone might think that I am
selling waporvare (software that isn't finished or needs a lot of testing
and polishing to work). This isn't so. I have been working on RTC Core since
October 2004 (that's 7 months) and it has been my full-time job since. But,
I didn't feel like publishing it or offering it here befoere I had a
complete Core component set for the client and for the server, which can be
used to write fully-functional applications client/server applications.

I do not want RealThinClient to have the same faith as RemoteOffice, where
some people are still attacking me just because I've sold the copyrights to
a company which didn't want to offer the same licensing terms for their
product I did while it was mine. I also do not want to make any promisses
regarding future upgrades and RTC updates. When I say that I plan to do
something, it is only ideas which I would like to realize.

RTC Core 1.1 is best suited for writing Web Servers, SOAP/XML Services, or
Client/Server applications. For WebServers and Services, you will be writing
server-side code only, using RtcDataProvider components to implement the
functionality. And for Client/Server applications, you will most likely be
using server-side remote functions, called by your clients. Since the
framework of RTC Core is built with a goal to work as a general server,
being capable of supporting data from different sources, all RTC components
can be used together in one application.

I will be enhancing RTC Core continualy, but ... please, do not go and buy a
copy if you are doing this only because I might add some feature in the
future. If you like RTC Core but miss some functionality, please contact me
directly (www.realthinclient.com) and I will tell you if that functionality
is implemented or will be inplemented in short, so you know if it is worth
waiting or you should take some other component set, already available. Each
time I add something interesting to the RTC Components library, I will post
it here as an announcement [ANN]. If you like what you see and feel like you
can use it, then RTC may be worth taking a look.

Again: Don't buy something you can't start using today. But, if you have
ideas for RTC and want to help me realize those, I would be more than happy
to grant you a free RTC license in return for your help.

Best Regards,
Danijel Tkalcec

Ted Nicolson · Guest

"Danijel Tkalcec" <dtkalcec (AT) hotmail (DOT) com> wrote