[dba-VB] Access data across the internet

Hi Stuart and John

Except that the main location could be placed in "the cloud":

http://www.jungledisk.com/desktop/how.aspx 

This service - which among other things mimics a drive letter - uses Amazon as the storage. 

The Amazon storage can, of course, be accessed directly, for example via the S3 service:

http://aws.amazon.com/s3/ 

Also: 
<quote>
LitS3 is a library written in C# that provides comprehensive and straightforward access to Amazon S3 for .NET developers. 
</quote>

http://code.google.com/p/lits3/ 

Fascinating tiny amount of code. Unfortunately I haven't had the time to play with even though we do have an Amazon account up and running.

/gustav


>>> "Stuart McLachlan" <stuart at lexacorp.com.pg> 31-08-2009 08:53 >>>
No,

As I read it, John's original scenario was several client locations processing files locally with  
a shared directory structure in the main location. He was looking at ways to share the 
directory structure and move files to and from it over the internet. 

No web at all.

-- 
Stuart


On 30 Aug 2009 at 21:25, Eric Barro wrote:

> Didn't the original spec indicate that the CSV file would be dropped into a
> web location where the client machines could pick them up?
> 
> -----Original Message-----
> From: dba-vb-bounces at databaseadvisors.com 
> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
> Sent: Sunday, August 30, 2009 4:30 PM
> To: Discussion concerning Visual Basic and related programming issues.
> Subject: Re: [dba-VB] SPAM-LOW: Re: Access data across the internet
> 
> The only reason it "goes away" is because web services use the standard HTTP port 80 
> which is open by default on most routers.   That means there is no configuration needed on 
> the client machines.  
> 
> But you will still need "IT" to configure the router and set up port
> forwarding to point to the server hosting the web service.  Of course, this
> is not an issue where you set up a web service on a public web server, but
> that is not what you are trying to do - you want something hosted internally
> which can access your internal file systems and databases and interface in a
> controlled manner with other machines.
> 
> There's nothing to stop you from using the same port 80 for your own TCP/IP
> Listener application. 
> 
> You can also any of the other "standard" ports which are likely to be open
> on a router such as FTP (21), SMTP(25),  POP3(110) etc
> 
> I have a couple of such Listener applications which do the sort of things
> you are after, but they are written in PB/Win - if you want to look at them
> to get a better idea of oterh way you can do this, I will send the source to
> you off line.
> 
> 
> --
> Stuart
> 
> 
> 
> On 30 Aug 2009 at 18:18, jwcolby wrote:
> 
> > Thanks Stuart.
> > 
> > I believe one of the implications of the service route was that the whole TCP/IP address / port 
> > thing goes away, IOW it can get through a firewall without having to get the intervention of IT.
> > 
> > I am listening to all points of view.  Luckily I am in no hurry here, it will be six months or more 
> > before I need to solve this problem, or even have the requisite knowledge.
> > 
> > John W. Colby
> > www.ColbyConsulting.com