Re: Data source options


Bill H wrote:

> Dawn:
>
> This is pretty much how FlashConnect was designed to operate. The
> FlashConnect executable, referenced in the URL, resides on the web server
> while the D3 component, an account on the dbms server, creates a socket
> connection to the web server. The D3 server can be anywhere, and usually
> is.
>
> The URL references the FC executable and also identifies the D3 program to
> run (and on which account). The D3 program usually reads in the form data,
> does some processing, builds a return web page, using templates or whatever,
> then returns it back to the FC executable, which sends it back to the
> browser.
>
> U2s RedBack product does pretty much the same thing. It has some additional
> IDE components and the you're charged for the U2 account (the server)
> component. This makes the U2 solution significantly more expensive and not
> likely to be used for expanding an mvDbms developers market, but then not
> too many people are using D3 and FlashConnect either.
>
> This explains why it's difficult for mvDbms developers to get out into new
> markets and develop new solutions; because the mvDbms suppliers are killing
> us with high costs.
>
> Bill
>

Galling to think that when I started using FlashCONNECT it was free.
There was/is also a UniVerse version which was never released. But for
those two masterstokes, and a couple of others (like merging with Omnis
and letting a lot of their best people go), RD could be riding the
crest of a wave now instead of struggling to keep their heads above
water. So sad. Still - FlashCONNECT remains a sound product imo, and JJ
and Jack are still there - as they have been from FC's beginnings
afaik.

Mike.

.