Hi, I am a Paradox developer from way back (1985 in fact) and have never really touched on the Web Server OCX much.
I am wondering if anyone is using this program to any great effect and what if any problems you see with it. Pardon my ignorance here but does the activex server cope with XML, CSS and XForms?
I am particularly concerned about security of using the server -i.e. can it be locked down tightly enough for real-world apps?
Perhaps this was answered elsewhere in our message boards but I wanted to add a quick note on my thoughts. The Web Server OCX is a lot of fun to code with and it's fun to turn Paradox into a webserver. It's definately not suitable for a large scale commercial venture, but for some applications within an organization that has an existing Paradox system, it's an option. Although, in general, I usually talk my clients out of using it because there are much better solutions available.
I am using the Web Server OCX usully for serval (8 or a lots) years. It is workinf fine and works as a small server. It is only a HTTP request/response OCX. It can manage only HEAD/QUERY/GET/POST request (no PUT).
You need to work to add environement to manage requests et responses. But you can manage dynamics and static ressources (.html/.css etc) and localisation of the ressource (drive/folder_path/ressource_name)
I am using the OCX in C++, VB and ObjectPal environements.
As a exemple, the OCX is workng as a "JSF framework" and is using to make real-time event management. It manages around 25 0000 requests per day, for 2 week without any issue.
It is a easy to use OCX that can help you to add a Embbeded Web Serverin your applications, as long as you can use OCX.
>>It manages around 25 0000 requests per day, for 2 week without any issue.
I assume that's 25,000, right? That's about 1 request every 3 or 4 seconds which is pretty light so yes, that's perfect for Paradox. We have several clients that use the OCX control in that exact fashion. It's still not the best tool even for that situation, but it sure is fun to push Paradox.
I'm curious, the above statement implies a crash every two weeks or so, is that what is happening? We've tried deploying Paradox as a webserver a few times in a production environment (i.e. hosting) and it was never stable enough to release commercially. We do still use it on occassion for a dedicated server approach.
The WebSvr.ocx can be unreliable and unstable depending on your use. I have found it to be reliable and not fail providing you do the following two things, although I don't have figures on how many hits it received:
- Set the OCX control's Visible property on the form to false
- Minimise the form
- Uncheck Allow Keep Alive Connections in the OCX Control properties
- Uncheck Enable Client Name Lookup in the OCX Control properties
Regards
Jonathan
Best regards, Jonathan
Computers are useless. They can only give you answers. - Pablo Picasso (1881 - 1973)
Paradox
Print This
