Many thanks for that very useful help.
I'm slightly confused, being used to HTTP as user-interface type of
thing. I would like the desktop app user to be blissfully unaware of
the details of the login. Although they'll know about it in principle.
Can I "go" to a (say) html/php page, fill it in with values, submit it
and read the resulting HTML all invisible to the user, using code rather
than user input?
If so, do you have a pointer to an example or two?
Thanks
Richard
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:457f324b$1@newsgroups.borland.com...
>
> "Richard Teller" <r.teller@e-tabs.com> wrote in message
> news:457ef9e7$1@newsgroups.borland.com...
>
>> An existing client app on the users desktop is being enhanced to
>> include a log-in by the user. The server app (not yet written) will
>> sit on a web-site somewhere.
>
> Unless you have direct control over the web server, then it is very
> difficult to put your own applications on the server. Network admins
> don't
> usually allow that.
>
>> After log-in the client app will contact the server app and will pass
>> the log-in and a few other details to the server which will verify them
>> and inform the client whether that log-in has been successful. If
>> so the client will carry on and if not will bomb out.
>
> If your website supports ASP, PHP, or Perl, then you don't need a server
> app
> for that. Just put a database on the website and let the client app use
> normal HTTP to access a verification page that then queries the database
> and
> returns the result.
>
>
> Gambit
