🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: borland.public.cppbuilder.internet.web
6 messages
6 total messages Started by David Ray Mon, 09 May 2005 18:53
Web-based System
#1115
Author: David Ray
Date: Mon, 09 May 2005 18:53
16 lines
1542 bytes
I'm thinking of a project that would be web-enabled such that users can
enter data through EITHER a client program that runs on their PC or through
a web-browser.

This is a simple application that hopefully would not take long to write;
the tables are simple and the relationships are, as well.  But I've never
written any kind of "web-enabled" application, so I really don't know where
to start.  Most recently, I've been developing with BCB6 but could use
something else if I needed to.

Would someone here be able to point me to a resource that might help me get
off the ground quickly with this?

TIA

David
Re: Web-based System
#1117
Author: Hans Galema
Date: Mon, 09 May 2005 19:48
32 lines
2201 bytes
David Ray wrote:
> I'm thinking of a project that would be web-enabled such that users can
> enter data through EITHER a client program that runs on their PC or through
> a web-browser.

Then you have to write at least three programs. A server, a gui-client and
a cgi-client. The cgi-client is started by a webserver upon requests
of a webbrowser.

> This is a simple application that hopefully would not take long to write;

Simple ? And three instead of one application ?

> the tables are simple and the relationships are, as well.  But I've never
> written any kind of "web-enabled" application, so I really don't know where
> to start. 

I do not know what ideas you have for a program to be 'web-enabled'.
But if your server and the gui-client communicate using sockets
and your own protocol, then the sever could be web-enabled already. Just
write a cgi-client that uses the same protocol.

So you did not write "web-enabled" applications.
Did you write web-applications ?
Did you write cgi programs ?
Do you know html and how to generate it ?
Can you manage communication using sockets ? For instance
using TServerSocket and TCientSocket ?

On which point do you need help ?

Hans.
Re: Web-based System
#1118
Author: Chad Z. Hower aka Kudzu
Date: Mon, 09 May 2005 20:39
17 lines
1499 bytes
"David Ray" <david@timecalc.com> wrote in news:427fb17a$1
@newsgroups.borland.com:
> Would someone here be able to point me to a resource that might help me get
> off the ground quickly with this?

http://www.atozed.com/IntraWeb

Works fine with CB6, and you can deploy it on a users machine, or run it via 
web.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
      "Programming is an art form that fights back"

  Web Development causing you headaches?
  Find relief at http://www.atozed.com/IntraWeb/
Re: Web-based System
#1119
Author: Remy Lebeau (TeamB)
Date: Mon, 09 May 2005 20:50
19 lines
1677 bytes
"Hans Galema" <notused@notused.nl> wrote in message
news:427fbf31$1@newsgroups.borland.com...

> Then you have to write at least three programs.

Not necessarily.  CGI is not a requirement.  The webserver can do the
requested work directly.  And incidently, even if you want to use CGI, you
don't need to write a program for it.  Just install the Perl engine from
http://www.perl.com and then shell out to it when needed.

> I do not know what ideas you have for a program to be 'web-enabled'.
> But if your server and the gui-client communicate using sockets and your
> own protocol, then the sever could be web-enabled already.

Only if HTTP were being used for that protocol to begin with.


Gambit
Re: Web-based System
#1120
Author: Hans Galema
Date: Mon, 09 May 2005 21:16
33 lines
2146 bytes
Remy Lebeau (TeamB) wrote:

>>Then you have to write at least three programs.
> 
> Not necessarily.  CGI is not a requirement.  The webserver can do the
> requested work directly. 

Ok. Three layers then.

> And incidently, even if you want to use CGI, you
> don't need to write a program for it.  Just install the Perl engine from
> http://www.perl.com and then shell out to it when needed.

That would be three programs then.

>>I do not know what ideas you have for a program to be 'web-enabled'.
>>But if your server and the gui-client communicate using sockets and your
>>own protocol, then the sever could be web-enabled already.
> 
> Only if HTTP were being used for that protocol to begin with.

Not needed.
HTTP for browser<->webserver.
CGI for webserver<->cgiapplication.
Own protocol for cgiapplication<->server. (The same as server<->guiclient).

What I meant was "web-enabling the server" by writing a cgiclient for it.

But the intention of my reply was to make it clear to David that
a lot of aspects had to be considered and to invite him to
express his needs more to the point.

Hans.
Re: Web-based System
#1121
Author: Chad Z. Hower aka Kudzu
Date: Tue, 10 May 2005 08:28
24 lines
1970 bytes
Hans Galema <notused@notused.nl> wrote in
news:427fbf31$1@newsgroups.borland.com: 
>> I'm thinking of a project that would be web-enabled such that users can
>> enter data through EITHER a client program that runs on their PC or
>> through a web-browser.
> 
> Then you have to write at least three programs. A server, a gui-client
> and a cgi-client. The cgi-client is started by a webserver upon requests
> of a webbrowser.

With IntraWeb he can make just one. It can run on the server and be accessed 
remotely by a web browser, or it can run localy (Standalone deployment) on 
the users machine and be accesed by a local browser. Witih umPartial and 
other you can get quite close to a real windows forms experience.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
      "Programming is an art form that fights back"

  Build Web Applications just like normal Delphi applications
  with IntraWeb for Delphi 5, 6, 7, Kylix, C++ Builder 5, 6 and Java

    http://www.atozed.com/IntraWeb/
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads