🚀 go-pugleaf

Hi,
not sure if this is the most appropriate group, but...

I am trying to figure out the best way to establish and hangup a unattended
auto-dial internet-connection for timer-controlled automatic ftp acess.

Problem :
there may be multiple independent processes which connect and disconnect
to/from
the internet in the same way. So its necessary to prevent the internet
connection from being closed by one program as long as others still need it.

As I understand InternetAutoDialHangup would close the connection without
waiting for other Processes so this doesn't seem to be the right way.

Example :
1. Process A calls InternetAutodial, the connection is established
2. Process B calls InternetAutodial, the connection is already established,
so
B can use the connection.
3. Process A has done its online-work ans calls InernetAutodialHangup, the
Sonnection is closed
4. Process B produces Errors because it still needs the connection

Possible Solution (?):
InternetDial seems to have autodial options and it returns a connection
Number
by which the specific Connection can be closed with InternetHangup. Is that
what i'm looking for ? Will several processes that are using InternetDial
with
the same physical connection to dial in be able to "close" their
"connection"
by number without closing each others ?

But if so - what about the Name of the connection ? InternetAutoDial uses
the
Default connection. How can I retrieve the name of this connection for use
with
InternetDial ?

thanks,
Nick