 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Richard Speiss Guest
|
Posted: Thu Dec 04, 2003 11:09 pm Post subject: How can I do this? |
|
|
I want my app to be a Dynamic DNS client so that they don't have to run a
separate app. From the documentation for the client all I need to do is
goto a specific website and pass all the information on the command line.
e.g. If I use IE and enter
http://dynupdate-no-ip.com:PORT/ducupdate.php?username=EMAIL&pass=PASSWORD&h[]=HOST1
it actually updates the entry for my host.
I figure that I should be able to use some simple internet component like
TcpClient but I continually get a Socket Error 10049. What component should
I use to send this information? Since it is such a simple requirement it
doesn't seem like I should need the Indy Direct components. I figure I
should be able to use one the built-in components for D6.
Am I on the wrong track? Can anybody suggest how I should be doing this?
Many thanks
Richard
|
|
| Back to top |
|
 |
Remy Lebeau (TeamB) Guest
|
Posted: Thu Dec 04, 2003 11:26 pm Post subject: Re: How can I do this? |
|
|
"Richard Speiss" <rspeiss (AT) mtxinc (DOT) com> wrote
| Quote: | I figure that I should be able to use some simple
internet component like TcpClient
|
I would suggest you use an actual HTTP component instead, such as the one
available in Indy (http://www.indyproject.org) or ICS
([url]http://www.overbyte.be)[/url].
| Quote: | but I continually get a Socket Error 10049.
|
WSAEADDRNOTAVAIL
(10049)
Cannot assign requested address.
The requested address is not valid in its context. Normally results from
an attempt to bind to an address that is not valid for the local machine, or
connect/sendto an address or port that is not valid for a remote machine
(e.g. port 0).
| Quote: | Since it is such a simple requirement
|
It is not as simple as you think. The request has to use the HTTP protocol
just to communicate with the server. HTTP is not a very trivial protocol to
implement manually. Oh sure, you could send a few strings over the socket
manually, but using a true implementation of the actual HTTP protocol is
best.
| Quote: | it doesn't seem like I should need the Indy Direct components.
|
You could, though. I wrote my own client for DynDNS.org, and Indy's TIdHTTP
component works quite well for it.
Gambit
|
|
| Back to top |
|
 |
Richard Speiss Guest
|
Posted: Tue Dec 09, 2003 4:24 pm Post subject: Re: How can I do this? |
|
|
I went to the Indy site to check out the licence thing and find it a little
confusing as I do not plan to change the source code, I just want to use the
component. My boss says that he doesn't want to have to list the
attribution so I am looking at the Mozilla Public Licence.
Can you tell me in simple terms, if I am just planning to use the component
with no changes and do not want to distribute source code, what do I need to
do? In '3.6 Distribution of Executable Versions' it looks like I still need
to include a notice stating that the source code is available so there is
still the attribution thing.
Thanks
Richard
"Remy Lebeau (TeamB)" <gambit47.no.spam (AT) no (DOT) spam.yahoo.com> wrote
| Quote: |
"Richard Speiss" <rspeiss (AT) mtxinc (DOT) com> wrote in message
news:3fcfbe9b$1 (AT) newsgroups (DOT) borland.com...
I figure that I should be able to use some simple
internet component like TcpClient
I would suggest you use an actual HTTP component instead, such as the one
available in Indy (http://www.indyproject.org) or ICS
([url]http://www.overbyte.be)[/url].
but I continually get a Socket Error 10049.
WSAEADDRNOTAVAIL
(10049)
Cannot assign requested address.
The requested address is not valid in its context. Normally results
from
an attempt to bind to an address that is not valid for the local machine,
or
connect/sendto an address or port that is not valid for a remote machine
(e.g. port 0).
Since it is such a simple requirement
It is not as simple as you think. The request has to use the HTTP
protocol
just to communicate with the server. HTTP is not a very trivial protocol
to
implement manually. Oh sure, you could send a few strings over the socket
manually, but using a true implementation of the actual HTTP protocol is
best.
it doesn't seem like I should need the Indy Direct components.
You could, though. I wrote my own client for DynDNS.org, and Indy's
TIdHTTP
component works quite well for it.
Gambit
|
|
|
| Back to top |
|
 |
Remy Lebeau (TeamB) Guest
|
Posted: Tue Dec 09, 2003 10:50 pm Post subject: Re: How can I do this? |
|
|
"Richard Speiss" <rspeiss (AT) mtxinc (DOT) com> wrote
| Quote: | I went to the Indy site to check out the licence thing and find it
a little confusing
|
What is confusing about it exactly?
| Quote: | as I do not plan to change the source code, I just want to use the
component.
|
Then just do so.
| Quote: | Can you tell me in simple terms, if I am just planning to use the
component with no changes and do not want to distribute source
code, what do I need to do?
|
Simply write the program, put the component into the program, compile, and
run.
| Quote: | it looks like I still need to include a notice stating that the source
code is available so there is still the attribution thing.
|
I know nothing about how the licensing works. You will have to ask the Indy
people directly. They have their own newsgroups at news.atozedsoftware.com.
Gambit
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|