Pwhp.web

11/07/2024

https://egbos.com/en/bos-platform/bos-app/bos-general/inventory?code=efbp3

Business operating system - Inventory management and warehouses administration

11/07/2024

https://egbos.com/ar/bos-platform/bos-app/bos-dedicated/medical-sector?code=efbp2

Medical module is an addon module that turns general modules into dedicated business solution, as health care business Bos can manage a simple clinic, lab, or enterprise الوحدة الطبية هي وحدة إضافية تحول الوحدات العامة إلى وحدة أعمال مخصص، ح...

09/07/2024

New Business management solution for your school or educational firm, truly differ from other solutions, manage and control your school with tight & right tool
see more @
https://www.egbos.com/en/bos-platform/bos-app/bos-dedicated/education-sector
https://www.youtube.com/playlist?list=PLIukaC2cwWZ-mnUrM2W6yJFHUCq5z-AN0

01/06/2017

Our mission is to supply a live stream of continuous and accurate data and insight into what people are thinking and doing all over the world, all of the time, so that companies, governments and institutions can better serve the people that sustain them.

14/12/2015

https://www.youtube.com/watch?v=D8c4JZW73cM

Ever wondered where websites come from? Learn what websites are made of, where they are stored, and how they get to your computer at home! Call us to get you...

14/12/2015

https://www.youtube.com/watch?v=i5oe63pOhLI

http://www.datacenterscanada.com - SIMPLE explanation of how the internet really works. Understand networks, inter-networks, data packets, peering and intern...

25/11/2015

How Multiple Servers Hosting Impacts Your Website's Uptime
Hosting of web sites has essentially become a commodity. There is very little distinguishing one hosting company from the next. Core plans and features are the same and price is no longer a true determining feature. In fact, choosing a host based on the cheapest price can be more expensive in the long term with respect to reliability issues and possible loss of sales as a result of website downtime.
Selecting a host from the thousands of providers and resellers can be a very daunting task, which may result in a hit and miss approach. But although hosting may have become a commodity, one distinguishing feature that you must always look out for is reliability.
At the heart of any hosting company's reliability is redundancy. This ensures that if a problem exists at one point, there will be an alternative which ensures continuity as seamlessly and transparently as possible.
Most hosts do employ redundant network connections. These are the high speed pipes that route data from the server to your web browser. But, redundant 'multiple web servers' have been extremely rare and very expensive, requiring costly routing equipment which has previously been used only in mission critical applications of Fortune 500 companies.
However, a very neat but little known Domain Name Server(DNS) feature called 'round robin' allows the selection and provision of a particular IP address from a 'pool' of addresses when a DNS request arrives.
To understand what this has to do with server reliability it's important to remember that the Domain Name Server (DNS) database maps a host name to their IP address. So instead of using a hard to remember series of numbers (IP address) we just type in your web browser www.yourdomain.com, to get to your website.
Now, typically it takes at least 2 to 3 days to propagate or spread the word of your DNS info throughout the internet. That's why when you register or transfer a domain name it isn't immediately available to the person browsing the web.
This delay has stymied the security benefits of hosting your site on multiple servers, as your site would be down for a couple of days if something went awry with one server. You would have to change your DNS to reflect your second server and wait days before the change was picked up in routers on the internet.
However, the round robin DNS strategy solves this predicament, by mapping your domain name to more than one IP address.
Select hosting companies now employ the DNS round robin technique in conjunction with'failover monitoring'.
The DNS round robin failover monitoring process starts by a web hosting company setting up your site on two or more independent web servers (preferably with different IP blocks assigned to them). Your domain name will therefore have 2 or more IP Addresses assigned to it.
Then the failover monitor watches your web server(s) by dispatching data to a URL you specify and looking for particular text in the results. When the system detects that one of your IP addresses is returning an error, and the others aren't, it pulls that IP address out of the list. The DNS then points your domain name to the working IP address/s.
If any of your IP's come back online they are restored to the IP pool. This effectively and safely keeps your site online even if one of your web servers is down.
The average failure detection and recovery time with a system like this can be as low as 15 minutes. This time varies depending on the speed of your site and the nature of the failure and also how long other ISP's cache (save) your DNS information.
The time taken for other ISP's caching your information can be manipulated in the failover monitor by lowering the "time to live" (TTL) cache settings. These are the settings that other ISP's will use to determine how long to cache your DNS information.
Of course you must bear in mind the matter of how frequently data is synchronized between your website's servers. This will be the hosting company's responsibility, and this may become complicated where databases and user sessions are involved.
The very expensive hardware based failover monitoring systems that point a virtual IP address to other ISP's, while behind the scenes juggling a number of unique IP addresses on different servers, is of course the most 'elegant' solution to multi server hosting.
That way, the whole issue of ISP's caching your information does not come into play.
Therefore, for site's that need to have true 99.99995% uptime, without huge outlays of money, the technology is readily available and certain proprietary failure monitoring systems are now relatively cheap to apply.

08/11/2015

Which Web Server - Linux or NT?
If you've been lurking in the various forums and newsgroups devoted to webmastering, you could hardly fail to notice the heated debate going on at this time. No, it's not which is the best browser. This debate is about web servers. More precisely, which one is better: Apache or Internet Information Server (IIS).
To tell you the truth, I've used them both (and a few others as well) and the simple plain truth of the matter is these two web server platforms are really functionally equivalent.
Ease Of Use
IIS is much easier for the novice as operators can maintain it from easy-to-use screens and forms. Windows 2000, on the other hand, costs a lot more than other operating systems such as Linux, FreeBSD and Unix.
Straight Apache requires a huge learning curve to learn how to operate and administer. Everything is configured in extremely obscure text files, and these configurations are done by hand (although you can purchase add-on utilities to enable entry of much of this information from screens and forms.)
Security
The security model of IIS is one of the best ever designed, based as it is upon NTFS (the security model of Windows NT and Windows 2000). This model is far superior to the anything provided with Apache for non-Windows systems. Of course, on Windows, Apache can use NTFS as well.
Of course, IIS has been plagued with a number of vulnerabilities lately, and these are a concern. It's common to patch IIS at least monthly, and to install a new service release (a collection of patches) twice a year. Most of the bugs were worked out of Apache (prior to version 2) long ago. Of course, with the release of version two of Apache you can expect a number of security and other flaws to surface - these are a normal part of a product's life cycle.
Customization
IIS does NOT have the equivalent of HTACCESS. The HTACCESS file in Apache is used to individually configure virtual sites (web sites) without restarting the web server. However, on IIS you have a very flexible method of configuration with ISAPI filters and other similar methods. Both methods (HTACCESS and ISAPI filters) are very obscure and for advanced webmasters.
Efficiency
According to several reports that I've come across lately IIS is more efficient than Apache. My own testing has led me to conclude the performance of the two is roughly the same for static pages. PHP (the server side scripting platform common on Apache) tends to be more efficient than ASP (the server side scripting system for IIS) according to many sources, although I have tested neither for speed.
Hardware Requirements
I have run both web server platforms on large and small boxes of many different configurations, and I've found they require much the same hardware. This is not surprising, since the two platforms basically do the same thing.
When you configure Windows and IIS, it's a good idea to strip the operating system of unneeded functions. This reduces the size box you need (as well as increasing security).
I've run both platforms on 64mb of memory with a single 5600 RPM IDE drive and 200mhtrz processors with reasonable response time (all things considered). I've also run them on dual 2gigahertz systems with 15k RPM SCSI raid 10 drives with incredible performance. The two platforms are equivalent in hardware needs.
Large Server Farms
Microsoft has worked hard on load balancing, so there are more options available for IIS and Windows 2000 for this than other operating systems. In fact, Windows 2000 clustering (the ability to run several servers using the same disks) is very advanced and makes disaster recovery a breeze.
Disaster Recovery
IIS backup solutions (those which are provided with Windows 2000) are surprisingly weak. There is no way to back up the metabase (all of the IIS configuration parameters) from one machine and restore it to another (which makes disaster recovery difficult). On the other hand, with Apache it's just a matter of saving all of the configuration text files.
Language and other support
IIS and Apache both support CGI, SSI and PERL (ActivePerl on IIS is excellent). IIS natively supports ASP and I'm sure you could find PHP if you looked (I have not). Apache tends towards PHP, although you can install something like Chilisoft ASP if you want.
CGI, SSI and PERL are performance hogs and security nightmares in both web platforms.
Stability
Both web platforms are rock solid stable. I have run apache servers which have stayed up for longer than a year without a reboot, and my IIS servers have run for years with the only rebooting required is the occasional service pack and security patch. Neither web platform (or OS for that matter) has even once crashed due to a bug.
Operating System Integration
IIS and Windows 2000 is a more "integrated" environment than Apache, since IIS is targeted specifically for the operating system. This has the advantage that the GUI and controls of IIS look and feel the same as every other tool on Windows.
On the other hand, you can find Apache for just about any platform, including Lunix, Unix, BSD, and even such things as OpenVMS. If you need to be able to move between platforms, then Apache is a great choice.
Email
SMTP on IIS is primitive but functional. This is because it is only provided to allow scripts and such to send email from the server. If you need additional email support, you are expected to use Exchange or some other email system.
Apache does not support SMTP (sendmail), although a version is usually provided on the target system. The provided email solution is full featured - but you must be very sure to check the configuration to be sure your system is not an open relay.
The IIS SMTP module is configured through the standard Windows 2000 entry system, while Sendmail requires configuration file editing. IIS SMTP is absolutely trivial to maintain; Sendmail can be a challenge.
DNS
DNS on Windows 2000 is far, far superior to anything available on Unix or Linux. Bind (he DNS for Unix and similar systems) has traditionally suffered from a huge number of security vulnerabilities) and is very involved to maintain.
My own experience with DNS servers indicates the best solution is a dedicated DNS application box. These are inexpensive (for a business), easy-to-configure and much more secure than either the Windows 2000 version or the Unix version.
Search Engines
There is NO difference as far as search engines are concerned between Apache and IIS (or any other web server, for that matter).
Conclusions
I'm sure I could write for hours and hours about this subject (and perhaps I will in an article on my own web site). Basically, IIS and Apache do the same thing. They have a vastly different design philosophy, however, and the underlying operating systems have even wider differences.
My experience is that Linux and Unix people prefer apache, and windows people prefer IIS.
To me, the choice of webserver really comes down to "what are you and your group comfortable with?" If your experience is with apache, linux or unix, then you probably want to stick with Apache. If your experience is with Windows, then you will probably be uncomfortable with Apache.
I've used both (and several others) and quite frankly, to me, it does not matter. Drop me on a server running apache or IIS, and I will feel at home.

05/11/2015

Do you need Dedicated IP when hosting your website ?
Many of us who is still beginner in web hosting industry didn't really know what is Dedicated IP/Static IP and does it really important to have dedicated IP for your site ?. And is there any difference between having dedicated IP and shared IP. In this article, I will try to explain and elaborate as much as possible so you can have better understanding and decide whether you really need them.
As the IP Address is getting harder and harder to get, most web hosting company doesn't offer dedicated IP to their hosting account. So basically when you host your site with them, you are sharing your IP Address with other web site and one IPaddress is normally shared by hundreds or even milion sites.
Then, the question is , how does it work, how did it knows how to load my site and is there any performance issue when your site IPAddress is shared between other web site?
The answer is that all the web request is handled by Web Server,and the webserver will load the your site based on the host header or virtual host name that your site is configured.
For example if the web server has 5 website and all sharing one IP, then the Network Admin has to configure host header or virtual host that is unique to your site such as www.yourdomain.com to your site.
And there is no performance benefit on using dedicated IP over shared IP. It all depends on your hosting provider bandwidth.
So what is the reason why people want dedicated IP?. The main reason is if you planning to use SSL on your site, then you need dedicated IP.If not then either static IP or shared IP doesn't make any difference.

04/11/2015

How does Traffic Affect My Hosting?
The topic of hosting involves many different aspects; reliability, customer support, pricing, add-on features, programming, and allowable installation of PHP and other popular marketing scripts.
Today, I'm going to focus on ONE topic, traffic, and the effects it has on your web site's hosting. The simple one word answer here is 'Bandwidth'.
By definition, Bandwidth is the measurement of data, and the speed at which it flows through the phone lines, cable or DSL lines to transfer information to and from a web site via your computer.
In relation to your web site hosting, Bandwidth measures this flow of data transfer, otherwise termed 'Traffic'. In plain English, it's the number of hits you receive to your site; pure volume multiplied by the file sizes included on your pages.
So, if you have an all text based web site, you would be able to receive more traffic, at lower bandwidth numbers, than you would if you have a 'graphics' intensive page, which would naturally have higher file sizes that are being transferred from your site to your visitor's browser.
That's great Ginger, but how does this effect my hosting?
Well, that depends on your host, and the package you sign up for. For example, most hosting services set an limit on the amount of bandwidth they include with your fee per month. Depending on the nature of your site, (graphics intensive vs. lower file sized pages), you should be able to predict how much bandwidth you will need.
Case in point; my design site is definitely what most would consider a *graphics intensive* web site! I can tell you that most of my pages there are over the recommended file size of 24kbs. From my stats logs, I can see that I receive upwards of 150,000 hits to my site before I reach a total bandwidth of 2GBs, which is usually the maximum limit you'll find on lower scaled hosting packages.
If you know, or predict that you'll see more hits than that in any given month, you may want to consider shopping for a hosting package that offers a higher maximum of bandwidth allowed per month.
Hosting companies that limit your bandwidth, charge an additional fee whey you exceed your limits. The average additional cost I've found through my research is approximately $3USD per GB...
FYI= 1 GB = 1,000 MB 1 MB = 1,000 KB
So, if you have a bandwidth, (aka 'data transfer'), limit of 2GB, that would equal approximately the same amount of data you can store on 3 CD's. *whew*
For a more detailed explanation of byte measurements,
visit: http://www.learnthat.com/courses/computer/windows/filesize1.shtml
If you're building your first web site, and have no idea how much traffic you will generate out of the gate, I would recommend starting with a basic web hosting package. As your site grows in popularity, and your traffic increases, you can always talk to your host about upgrading to a package with higher bandwidth limits.
From my own experience, brand new websites usually take about 3-6 months of solid promotion before bandwidth becomes an issue. Remember to use a host that provides in-depth statistics reports, and monitor your web site activity regularly. Watch for trends, and base your judgments on your results.

03/11/2015

How to estimate your website hosting needs
Write this article especially for people who are new to web hosting. This is why I will only talk about the basic needs (in a shared hosting environment): space, bandwidth. Most of the people looking for advanced features (scripting, databases) already know what they want/need anyway.
So let's start with the space. Web space (disk space) is the amount of data you can store on the hard disk of the web server. Each web hosting account comes with a certain amount of space, usually over 50 MB and less than 1000 MB.
Obviously, the amount of needed space depends on the size of the website. Most websites are composed of html (text) pages with a few images (gifs or jpegs) or even a little bit of Flash animation. Text is very economical; it occupies very little space. Images and flash are more expensive; they require a lot of space. If you're new to the web you might think it's great to have a lot of colorful images to make your website really beautiful. Don't make this common mistake!
Your aim should be to say as much as you can on a page while maintaining it's size under 50-60 KB including images.
The reason? There are still lots of people using slow dial-up connections of under 56 Kbps. For them a 150 KB will take more that 21 seconds to load. A 60 KB page will take more than 8 seconds to load. That's still a lot of time! A good page size is under 30 KB. A maximum page size is 50-60 KB. Considering an average page size of 30 KB, you can put approximately 33 pages on 1Mb of space. If you have 10 MB of space available, you could host 330 pages. I only wish I had so many pages to put online. Don't worry, I'm working on it!
The idea is this: unless you run a busy forum your needs for space are likely to be rather modest. Just keep in mind to achieve an average of 30KB/page and you should be more than fine even with 10 MB of web space.
Bandwidth is the amount of data that you're allowed to transfer per month. It includes all uploads and downloads regardless of the protocol used (HTTP, FTP, POP etc.). Bandwidth depends very much on the average page size, but it also depends on the number of visitors your website will have and the average number of pages they visit. For an average page size of 30 KB, 20,000 visitors per month and 3 pages per visitor your website will need about 1800 MB (1.8 GB) of bandwidth per month. Most low cost hosting packages include that amount of bandwidth. Not to mention that 20,000 visitors per month is only a dream for most websites. Most don't even have 2,000 visitors per month.
I took you through all those numbers just to give you an idea how to estimate your needs. If you're just launching your website you will not need neither a huge amount of space, neither a huge amount of bandwidth. For 99% of people a hosting account with 10MB of space and 1Gb is more than enough. Conclusion: Unless you have reasons to believe that your website will definitely have lots of visitors and unless you'll offer movies or music for download (legally of course), I see little reason for you to worry about space and bandwidth.
Just make your own calculations and also try to make sure that the host you choose allows account upgrades. That is to make sure you will be able to get more space and/or bandwidth if/when you need it without going through all the trouble of changing hosts.

02/11/2015

Bandwidth Or Data Transfer - Which is Which?
Too often web hosts talk about bandwidth and data transfer in the same breath but truth be known they are different although very closely related. Bandwidth is how much data can be transferred at a time and data transfer is how much data is being transferred.
Think of it this way. If bandwidth were a bridge, then the bigger the bridge is the more vehicles can pass through it. While data transfer is the number of vehicles allowed on the bridge in say a month. In essence, data transfer is the consumption of bandwidth.
How It Affects Your Site
The less bandwidth you have, the slower your site takes to load regardless of the visitor's connection type. If you have more visitors, some of them will have to wait their turn. The least data transfer you have, the more often you'll find your site unavailable because you're reached the maximum allowed until a new month rolls by or you upgrade your account.
Determining Your Requirements
Usually when a host talks about bandwidth, they are referring to your transfer. So you need to figure out what is sufficient for your site to function. You'll need to gather some information; fairly easy if you already have a site. Most of this information is available from your traffic history. If you don't have an existing site, provide an optimistic estimate if you intend to heavily promote the site. Then get ready for some math.
Find out the daily averages of:
1- Number of visitors / expected number of visitors
2-Page size including the graphics of the page
3-Page views / expected pages viewed by each visitor
Then, multiply them as follows:
Visitors x Page size x Page views x 30 days = Monthly Website Transfer
You should also throw in a small margin or error there to take into account email traffic and your own uploads to the server. If you offer downloads, then you should add the following:
Average/Expected downloads x File Size x 30 days = Monthly Download Transfer
Unlimited Plans
Bandwidth is very expensive. All hosts are limited by their own allocations. Thinking back to the bridge. What happens is each visitor to your site will be given a smaller lane to transfer the data, creating many tiny lanes therefore "unlimited". The more visitors you have the smaller each lane will be, which makes each visitor wait for the page to load.
More often than not there is little choice over your bandwidth as your host controls this. Some hosts may limit the number of simultaneous connections so in affect slowing down your site and refusing some visitors. This is called throttling.
If you're concerned about this, you should ask the host how they control bandwidth usage or purchase a package with more data transfer. If you use HostVoice.net (http://hostvoice.net), this information is easily obtainable with one request.
Reducing Transfers
On the other hand, you can reduce your transfer amount by building simpler, more efficient websites and optimizing your graphics. Refrain from fancy flash presentations or streaming audio. Use CSS, call JavaScript externally instead of embedding in every page.
Remove unwanted tags, white space and comments. Limit your META tags to those absolutely necessary. Having too many keywords is not search engine friendly. Besides many search engines will only review the first few and ignore the rest.
Another good idea is to cache your website but you might want to set an expiry date in the HTTP headers so the browser will refresh the content after a certain time. Use mod-gzip. It could save you as much as 40% of your bandwidth. Out of control robots can also suck down your bandwidth like a black hole. So use robots.txt to keep spiders in check.
Src: http://www.cyberindian.com/web-hosting/