Company	Features
net4india.com	Disk Size	1GB	2GB	4GB	10 GB
	Bandwidth Transfer in GB	Unlimited	Unlimited	Unlimited	Unlimited
	No. of domain names that can be hosted	1	1	1	1
	*Allocate username and password to folders on web	Yes	Yes	Yes	Yes
	*Website write permission	Yes	Yes	Yes	Yes
	Windows Free Sub-domain	3	3	3	3
	Windows Microsoft Windows 2003 w/IIS 6.0	Yes	Yes	Yes	Yes
	Windows Microsoft Windows 2008 w/IIS 7.0	Yes	Yes	Yes	Yes
	Linux Linux Redhat	Yes	Yes	Yes	Yes
	Control Panel	Yes	Yes	Yes	Yes
	Raw log files	Yes	Yes	Yes	Yes
	*MS FrontPage Server Extensions	Yes	Yes	Yes	Yes
	24/7 access via FTP	Yes	Yes	Yes	Yes
	Web traffic reporting	Yes	Yes	Yes	Yes
Price	Price/ Year	Rs. 3,649	Rs. 7,298	Rs. 14,596	Rs. 29,499
e2enetworks.com	Plan	VPS-HDD-S	VPS-HDD-1	VPS-HDD-2
	RAM	768MB	1536MB	3072MB
	Diskspace	40GiB	75GiB	150GiB
	IP Addresses	1	1	1
	Monthly Data Transfer	200 GB	400 GB	800 GB
	Control Panel	Virtualmin	Virtualmin	Virtualmin (Unlimited)
Price	Monthly Fee	Rs. 1999	Rs. 3700	Rs. 6850
Price	Monthly Fee(6 month prepay)	Rs. 1899	Rs. 3515	Rs. 6500
Price	Monthly Fee(12 month prepay)	Rs. 1799	Rs. 3330	Rs. 6165
Esds.co.in	Hard Disk	ESDS - Cloud B I	ESDS - Cloud B II	ESDS - DC Cloud SI
	RAM Allocation	0.8Ghz	1.6Ghz	Single Core
	Operating System	20GB	40GB	160GB
	Control Panel	512MB RAM	1GB RAM	1GB RAM
	Bandwidth	Linux	Linux	Linux
	Server Access	cPanel / Plesk (Linux)	cPanel / Plesk (Linux)	cPanel / Plesk (Linux)
	Cloud Server Management	100GB Bndwdth/ Month	200GB Bndwdth/ Month	50GB Bndwdth Month
	Network Uptime	2 IP’s	2 IP’s	2 IP’s
	24×7 Server Monitoring	Fully Managed Cloud Server	Fully Managed Cloud Server	Fully Managed Cloud Server
	24×7 Phone Support	100% Uptime	100% Uptime	100% Uptime
	24×7 Live Chat Support	YES	YES	YES
	24×7 Email Support	YES	YES	YES
		YES	YES	YES
		YES	YES	YES
	Setup Fee	Free	Free	Free
Price	Monthly Pricing	Rs. 2,199	Rs. 3,299	Rs. 3,480
ZNet.com	No. Of Pages	1	15	50
	Web Space	1GB	5GB	25GB
	Email	1	10	50
	MySQL database	0	5	10
Price		Rs. 100/Mnth	Rs.1299/Mnth	Rs.2500/Mnth
	Total Disk Space	50GB	100GB	200GB
	Data transfer/Mo.	Unlimited	Unlimited	Unlimited
	Websites	Unlimited	Unlimited	Unlimited
	POP Email ID	Unlimited	Unlimited	Unlimited
	Sub Domain (sub.domain.com)	Unlimited	Unlimited	Unlimited
	MS SQL 2005/2008 Databases	Unlimited	Unlimited	Unlimited
	MY SQL Databases	Unlimited	Unlimited	Unlimited
Price		Rs. 1399/mo.	Rs. 2399/mo.	Rs. 4199/mo.
Indialinks.com	Web Space	500 Mb	1000 Mb	2500 Mb
	Mailboxes	5 Mail Boxes(2.5Gb)	Do	Do
	Monthly Bandwidth	100 Gb Data Transfer	Do	Do
	MySQL Database(s)	1	Do	Do
Price		Rs.8000/Year	Rs.9500/Year	Rs.16000/Year
ewebguru.com	Budget Reseller	Advance Reseller	Power Reseller	Ultimate Reseller
	Web Space	10 GB	20 GB	30 GB	40 GB
	Monthly Bandwidth	100 GB	200 GB	300 GB	400 GB
	Domain Limit	Unlimited	Unlimited	Unlimited	Unlimited
	cPanel/WHM
	Subdomains	Unlimited	Unlimited	Unlimited	Unlimited
	FTP Accounts	Unlimited	Unlimited	Unlimited	Unlimited
	MySQL Databases	Unlimited	Unlimited	Unlimited	Unlimited
	POP3 Mail accounts	Unlimited	Unlimited	Unlimited	Unlimited
Price	Monthly Price	Rs.995/-	Rs.1995/-	Rs.2995/-	Rs.3995/-
	Half Yearly Price	Rs.5595/-	Rs.11195/-	Rs.16995/-	Rs.22395/-
	Yearly Price	Rs.9950/-	Rs.19950/-	Rs.29950/-	Rs.39950/-
Brainpulse.com	Disk Space	1 GB	5 GB	15 GB	Unlimited
	Bandwidth/mo	Unlimited	Unlimited	Unlimited	Unlimited
	Domain Hosting	1	2	5	10
	Sub Domains	Unlimited	Unlimited	Unlimited	Unlimited
	MySQl Databases	2	Unlimited	Unlimited	Unlimited
	FTP Accounts	Unlimited	Unlimited	Unlimited	Unlimited
	Email Accounts	50	100	200	Unlimited
	Price / Year
Price		Rs. 899	Rs. 1999	Rs. 3999	Rs. 8500
hostrightnow.com	Dedicated RAM	384 MB	1 GB	2GB
	Disk Space	10 GB	30 GB	60 GB
	Monthly Traffic	100 GB	300 GB	600 GB
	Usable IP addresses	1	1	2
	24×7 live chat and phone support	Yes	Yes	Yes
	24×7 server monitoring	Yes	Yes	Yes
	24×7 port monitoring	Yes	Yes	Yes
	Easy Upgrade Options	Yes	Yes	Yes
	Setup Fees	Rs. 500.00	Rs. 900.00	Rs. 900.00
Price	Monthly cost	Rs. 1450.00	Rs. 2800.00	Rs. 3900.00

There exists a wide range of mobile device user agents (browsers), each rendering markup in different ways. The choice to use WML, XHTML Mobile Profile, XHTML Basic, or cHTML can be an overwhelming decision, to say the least.

All mobile web development strategy must begin with an understanding of the target audience and what they want from a site or app, and what the contextual relevance of such a site or app is, what is relevant to the users and the tasks, the problems, and the needs, the users may encounter while being mobile?

WAP 2.0: An XHTML Environment

WAP 2.0, XHTML Mobile Profile (XHTML-MP) is generally the preferred mark-up language, with mandated backward compatibility for WML.

Nearly, all devices today are WAP 2.0 devices with XHTML Mobile Profile, which will be familiar to anyone who has worked with XHTML Transitional or Strict is the official mark-up language for such devices.

Finally, because XHTML-MP is a subset of XHTML, initial testing and validation are done within most desktop browsers. Thorough, final testing will certainly need to be conducted using actual devices, but one may test on the desktop initially to see if the mark-up renders correctly and semantically.

Design Strategy

Opt for web standards and a flexible layout and then with the reference design and adaptation rules in place, the final strategy builds flexibility into the mark-up through the use of generic, standards based XHTML and CSS. In practice, this means creating mark-up that uses the tags and structures inherent in HTML (i.e. headers, paragraphs, lists and divs) to define the structure of the page. The immediate benefit—any browser that can read HTML will be able to display your content and will assign it with (albeit rudimentary) visual style. Given the vast number of mobile devices, this benefit cannot be underestimated as it ensures your content will be accessible to a large number of users without too much higgery-jiggery on the part of developers. One will then be in a great position to progressively enhance the design for different device groupings through the use of browser and/or device-specific CSS, graphics and scripting.

The BBC web site is an ideal example as it shows how simple it can be to combine clean mark-up with well conceived styles and strategic editorial decisions to achieve a great experience on a wide range of devices. Ultimately, the design, adaptation and editorial choices will be based on many factors including the budget, target audience and the functionality of the mobile web site. In the end, it’s all about striking a balance between the creation of a well optimized, fast-loading site and the delivery of great, targeted content to the users.

Development Strategy

A mobile-optimized site addresses first how content is accessed and second what it looks like. In other words, it means context before aesthetics, function before form. Pages are leaner, which means users are spared excessive bandwidth costs and generally enjoy a faster browsing experience.

The development follows the W3C’s Mobile Web Best Practices 1.0 document.

ASP.NET version of HAWHAW can be used in creating such mobile website.

Testing Strategy

There are almost 30+ different mobile browsers and many more. With these kinds of numbers, it is highly impossible to test the Web site across all devices? What can be done is test the site on at least one device from all popular manufacturers, and on as many of the mobile browsers as possible. This will give a good idea of how the site works on different devices and will also help in resolving issues. The catch is in making sure that there is access to all of the necessary devices and mobile browsers. Testing is usually possible in one or two physical devices – not enough to adequately test on but emulators can be used instead to simulate testing on the real device or browser. The benefits of this approach are many-fold:

· No data browsing charges are incurred, as all browsing is performed via your standard Web connection

· Quicker access to devices – starting an emulator is faster than switching sim cards and rebooting devices

· Provides access to a potentially large number of devices/browsers – the number of devices is only limited by hard disk space and the number of emulators that can be found

· Inexpensive – many emulators are available for free

Fortunately, Mozilla Firefox supports some great extensions that can make testing of mobile sites a piece of cake. Firefox is probably the best browser out there for mobile Web site testing. To make Firefox imitate a mobile device, the following are required:

· The Firefox Web browser (obviously)

· The Modify Headers add-on

· The User Agent Switcher add-on

· At least one mobile device user agent

· A UA Profile HTTP Header

After the add-ons have been installed, Firefox is ready for mobile site testing.

Mobile websites can be developed for the following devices:

Apple (iPhone)
Blackberry	BlackBerry® World Edition™ BlackBerry® Tour™ BlackBerry® Storm™ BlackBerry® Pearl™ BlackBerry® Curve™ BlackBerry® Bold™ BlackBerry® 88(00,20,30)
Palm	Palm Pixi Palm Pixi Plus Palm Pre Palm Pre Plus
Android	Nexus One Passion / Bravo GW880 Xperia X10a Eve / GW620 Eris / Desire One Streak Calgary / Motus Liquid / A1 Moment Behold II DROID / Milestone Archos Phone CLIQ / DEXT O1 Spica / Galaxy Lite / i5700 Pulse Mini 3i Sprint Hero Tattoo Hero Galaxy / i7500 Magic / myTouch 3G Dream / G1
Samsung	Android Phones Windows Phones(z105)
Nokia	All N Series
LG	Android Phones
Motorola	V3i
Sony Ericsson	K750i

Mobile websites will have to be compatible across the following mobile browsers:

·Blazer ·Bolt browser ·Deepfish ·Firefox for mobile ·IbisBrowser ·Internet Explorer Mobile ·Iris Browser ·JOCA ·Konqueror Embedded ·MicroB ·Minimo ·NetFront ·Obigo Browser ·Opera Mobile ·Pixo ·S60 web browser ·Safari ·Skyfire ·Steel ·Teashark ·ThunderHawk ·UCWEB ·uZard Web ·WinWAP

For those of you who’ve been frustrated by the XMLHTTPRequest object’s inability to make cross domain requests, there is a way out. This method does away with the XMLHTTPRequest object and uses a technique called dynamic javascript. Here’s how it works.

You would normally define a script tag something like this:

What if you replaced it with this piece of code?

But that can’t possibly work right? The browser will know right away that something’s off, right? Actually your browser won’t find out if your backend script (yourscript.php here) returns what it expects - Javascript code. There are two things you need to do with your backend script to achieve this. First you put in a header that tells the browser that the data returned is of type javascript.

This effectively fools the browser into thinking it’s reading a .js file. From then on print all the javascript statements you want wrapped within php strings. You will do something like -

That’s it! Try it out. Put the script tag in an HTML page, and the php file on the server, and on opening the page in the browser you should be able to see the dialog box. Of course this simple example does not convey the true power of this technique - that you can make database calls in the script and modify the javascript accordingly.

Suppose you have three clickable images on the screen. Each time one of them is clicked, you have to go back to the database, pick up a message associated with that image and display it. How would you do it? One solution would be to prepopulate hidden divs or javascript variables in the page using a server side scripting language. This idea immediately fails if you do not have control over the web page’s preprocessing. Perhaps you are only supplying a piece of javascript that ‘decorates’ the existing page with the required message, without assuming anything about the content. Then you have to make database calls on your server through the only entry point available to you: the javascript code.

A sample code would look something like this:

This function creates a script tag on clicking the image and that script tag calls a php file that returns the content. First it checks that a dynamically created script tag designed to do precisely this does not already exist. A large number of clicks would create a large number of script tags and that would not do site performance any good. What will the backend php code look like?

There you go, simple and powerful. A combination of dynamic script creation and .js file imitation using a server side script can, to a certain extent, simulate the AJAX effect of updating parts of a page without a complete refresh.

Browsing the web it seems to be quite a challenge installing and working with Ruby On Rails on HostMonster.

We felt the same, once we figured out the tricks, we have really started appreciating deploying on this.

Here are a tips for deploying RoR apps:

Creating an RoR App in Host Monster

1) Create an app in Ruby on Rails console in cPanel and PATH pointing to the my_rails_app rails app root directory (under which u would have public, config, etc..)

2) Create a subdomain (if required) using cpanel, give it your app name myapp (HOME/public_html/myapp)

3) Build your app OR extract your app in the my_rails_app dir

4) Go to the MySql Databases in cPanel, create the Database you want to use and the user name, associate the DB with the user.

5) Go to my_rails_app/config/database.yml and make the necessary changes

adapter: mysql

database: myid_dbname

username: myid_username

password: mypassword

hostname: localhost

ENV['GEM_PATH'] = ‘/my/home/dir/ruby/gems:/usr/lib/ruby/gems/1.8′

6) rm ~/public_html/myapp

ln -s my_rails_app_dir myapp

7) Check if you have dispatch.cgi; dispatch.fcgi; dispatch.rb if not copy from any of your RoR apps

8 ) make sure your .htaccess is fine, better still copy this..

<IfModule mod_fastcgi.c>

AddHandler fastcgi-script .fcgi

</IfModule>

<IfModule mod_fcgid.c>

AddHandler fcgid-script .fcgi

</IfModule>

<IfModule mod_cgi.c>

AddHandler cgi-script .cgi

</IfModule>

Options +FollowSymLinks +ExecCGI

# If you don’t want Rails to look in certain directories,

# use the following rewrite rules so that Apache won’t rewrite certain requests

#

# Example:

#   RewriteCond %{REQUEST_URI} ^/notrails.*

#   RewriteRule .* - [L]

# Redirect all requests not available on the filesystem to Rails

# By default the cgi dispatcher is used which is very slow

#

# For better performance replace the dispatcher with the fastcgi one

#

# Example:

#   RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]

RewriteEngine On

# If your Rails application is accessed via an Alias directive,

# then you MUST also set the RewriteBase in this htaccess file.

#

# Example:

#   Alias /myrailsapp /path/to/myrailsapp/public

#   RewriteBase /myrailsapp

RewriteRule ^$ index.html [QSA]

RewriteRule ^([^.]+)$ $1.html [QSA]

RewriteCond %{REQUEST_FILENAME} !-f

<IfModule mod_fastcgi.c>

RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]

</IfModule>

<IfModule mod_fcgid.c>

RewriteRule ^(.*)$ dispatch.cgi [QSA,L]

</IfModule>

# In case Rails experiences terminal errors

# Instead of displaying this message you can supply a file here which will be rendered instead

#

# Example:

#   ErrorDocument 500 /500.html

ErrorDocument 500 “<h2>Application error</h2>Rails application failed to start properly”