Ha i knew it!
The Web Model
The Web deployment model consists of an application that can be run and
administered just like a Web page. In this scenario, the HTA is launched
simply by browsing to its URL or by accessing it from the Internet Explorer
Favorites list. Before launch, an Internet Explorer dialog box presents the
user with the choice to open or save the application. After launch,
ancillary application components are downloaded from the server as needed
and then cached. Servers must have the MIME type "application:hta"
registered for delivery through the http: protocol to work.
This model boasts some important strengths. It facilitates seamless updates:
The intranet administrator need only post the new code or content for the
client to receive the latest version. It provides ease of use: The user need
never install or uninstall the application. Unused applications are
automatically flushed from the cache. One important consideration when
evaluating this deployment model is that server-based applications cannot be
run offline or when the server goes down. One option is to anticipate this
eventuality by implementing the advanced channel (CDF) features in Internet
Explorer 4.0 and later. For more information, see the Introduction to Active
Channel Technology.
The Package Model
In the package deployment model, the installation process for the HTA is the
same as for traditional applications. Files are copied from disk or over a
network, using any installer or self-extracting executable. The installer
places the application in the Program Files directory or in the directory
selected by the user. A link to the HTA is included in the Start menu. And
the application's dependency on Internet Explorer 5 or greater is
registered. This way the user is warned that uninstalling Internet Explorer
will disable that application. Look to tools vendors for vehicles for
packaging and delivering HTAs to your specifications.
Like the Web model, the package model has points in its favor. The user is
prompted only during the initial installation about trusting the
application; thereafter, the application runs as trusted code just as an
..exe does. Also, the installed HTA is always available to users, whether
they are connected to the server or not.
http://msdn.microsoft.com/library/default.asp?url=/workshop/author/hta/overview/htaoverview.asp