Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : LAST MILE TECHNOLOGIES - Let's Discuss Them Here -- Ignore unavailable to you. Want to Upgrade?

To: John Stichnoth who wrote (3234)	3/28/1999 9:03:00 AM
From: Kevin Collins	Respond to of 12823

JS, I hope I'm reading your question correctly, but the short answer is yes you can have your own web server connected through an ISP. It should not be affected by the type connection you have. Of course whether a particular type of connection will meet your business needs ie. provides enough bandwidth and availability is a different matter. I'm also not taking into consideration whether or not the service provider will place obstacles in your way such as not allowing you to utilize several domain names for the different web servers. It is not uncommon for some in-home businesses to host their own web sites using an ISDN connection. Is there a reason I'm unaware of that would make DSL any different in this regard? Going a step further, today, if I desired it, I could make my development environment's HTML and ASP pages available to be viewed by you or anyone else, even though I'm sitting here using my laptop (Win98) and a 56K dial up connection. All I would have to do is startup Personal Web Server (PWS) and give out my domain name. It would be "my-email-name.service-provider.com." Finally, if it's a static or dynamic IP address it makes no difference since the domain name is translated to the proper IP address by the ISP. Dynamic IP allocation is just a resource conservation method. It makes sense when you have many "transient" users as is the situation with dial up users. A small number of IP addresses can serve a large subscriber population. Once everyone has continuous connections then dynamic IP address allocation provides the service provider fewer benefits if any at all. Kevin

To: John Stichnoth who wrote (3234)	3/28/1999 7:24:00 PM
From: Frank A. Coluccio	Read Replies (2) \| Respond to of 12823

John, I'd like to preface my reply by stating that there are no universal rules governing what an ISP or CLEC, or an ILEC, for that matter, can do in the way of making provisions for its subscribers. These are largely business decisions that they must make, and not dictated by established norms. At least not as much as they once were. If a service provider wants to satisfy a given class of customers by offering off-the-beat beat services, even, they will tweak whatever it is that needs tweaking in order to make that service good. They will even create gateways if they have to.... for a price. ------ Having stated that, I'm not certain that I understand the entire scope of what you would like to do. >>Does anyone have thoughts on the server side? Can a person host in their own server, using a dsl line (probably partial or shared line) out to an domain service provider? << Yes, but is that all you want? How about fire walling? Mail servers? The DNS servers themselves? Upstream access to the Internet's core? You would leave these all to the ISP or DNS provider to maintain? >But is it technically reasonable/feasible? < Yes, it's technically feasible, but I doubt that it would be economically feasible if you run up against what you've predicted in the following, unless you had sufficient symmetric bandwidth: >>I've got half a dozen sites out on cheap hosting services. At $10 per month it starts to add up. And one client is talking about an application that will run into the hundreds of megabytes if it takes off. All these applications have different domain names. The seven (about) domains I've got up are on I think three different DNS servers.<< At some point you cross over to where the line costs are equal to, and then can become far higher than, the colocation costs, if you are highly successful on the hit count and content provision side of the business. A single DSL line wont cut it, in that case. And keep in mind that you must make allowances for incoming and outgoing traffic flows, and that means that a simple ADSL line (which is asymmetric) wont do. In other words, your limited upstream capacity on an ADSL line must satisfy your customer's insatiable downstream requirements, and vice versa. You'll need a more expensive symmetric line, like an HDSL or HDSL2 running at ample speeds, or maybe a T1 at some point. These line capacities would then need to be matched by the ISP on the core side of their routers, anyway. And the ISP, of course, already has this kind of capacity to begin with. But as far as your window (router port capacity towards the core) to the 'net, you could be effectively wind up paying for the same capacity twice, if you were to backhaul everything to 'your place.' No, you're not out of your mind, incidentally. Unless the economics are proved to be egregiously out of line in favor of the local provider (and the ISP or DNS provider). The economics have to make sense. >>It's easy enough to get a domain name. How do you get your DNS address set with a dsl hookup? Can you do it with a static address, or a proxy?<< Let me suggest that you go to the Boardwatch site where you can obtain a wealth of information concerning these issues, including a good history of the then and now of the Internet's architecture and rules. This article won't talk to the DSL issues, specifically (that I recall, at least), but you can gain a sense of the parameters involved in setting up a site, regardless of what medium you choose. The title of the article and its url follows: "The Internet - What is it?" boardwatch.internet.com It's a long, multi-part article in the "Internet Architect" section, written by Jack Rickard. Frank_C.