Web Synchronization

Hello guys!
I went through the bunch of documentation pages about configuring the one for providing web subscriptions.
The most usefull for me were:

Security Architecture for Web Synchronization
How to: Configure an IIS Server for Web Synchronization (SQL Management Studio)
How to: Configure a Subscription to Use Web Synchronization
Topologies for Web Synchronization
Securing the Publisher
Subscribing to Publications
Mssubscription_properties (Transact-SQL)
How to: Configure a Subscription to Use Web Synchronization (Replication Transact-SQL)
sp_addmergepullsubscription (Transact-SQL)
Web Synchronization for Merge Replication
 But I still have questions about it. If you could help me with small notes about subscribing to web based merge publication I would really appreciate that!

I believe, I just need a bit of clarification. The target setting is simple as it is: a client should connect to the our hosting server via HTTPS and update his pull subscription on demand by running .NET application.
 Avoiding the server part, are the following steps correct and enough to accomplish what I need?
1. To create subscription, should I use the script:-- This script uses sqlcmd scripting variables. They are in the form-- $(MyVariable). For information about how to use scripting variables  -- on the command line and in SQL Server Management Studio, see the -- "Executing Replication Scripts" section in the topic-- "Programming Replication Using System Stored Procedures". -- Publication must support anonymous Subscribers.-- Execute this batch at the Subscriber.DECLARE @publication AS sysname;DECLARE @publisher AS sysname;DECLARE @publicationDB AS sysname;DECLARE @websyncurl AS sysname;DECLARE @security_mode AS int;DECLARE @login AS sysname;DECLARE @password AS nvarchar(512);SET @publication = N'AdvWorksSalesOrdersMergeWebSync';SET @publisher = $(PubServer);SET @publicationDB = N'AdventureWorks';SET @websyncurl = 'https://' + $(WebServer) + '/WebSync';SET @security_mode = 0; -- Basic Authentication for IISSET @login = $(Login);SET @password = $(Password); -- At the subscription database, create a pull subscription -- to a merge publication.USE [AdventureWorksReplica]EXEC sp_addmergepullsubscription         @publisher = @publisher,         @publication = @publication,         @publisher_db = @publicationDB,        @subscriber_type = N'anonymous'; -- Add an agent job to synchronize the pull subscription. EXEC sp_addmergepullsubscription_agent         @publisher = @publisher,         @publisher_db = @publicationDB,         @publication = @publication,         @distributor = @publisher,         @job_login = @login,         @job_password = @password,        @use_web_sync = 1,        @internet_security_mode = @security_mode,        @internet_url = @websyncurl,        @internet_login = @login,        @internet_password = @password;GO
 
What is  @job_login parameter here? As I understand, I will not run SQL Agent job as our client uses MS SQL Server  2005 Express. And I do not want to run it as we will provide a client with .NET application for performing synchrinization on demand
Parameter @publisher means full SQL Server instance name? For example, MYMACHINEMSSQLSERVER?
What user will be used to connect to the distributor and to the Publisher? Will it be @internet_login?
Do I need running sp_addmergepullsubscription_agent if I€™m going to use the following .NET application code to synchronize over the Internet?
 
2. To perform synchronization with our hosting servers, should a client use the following code?
            // Define the server, publication, and database names.
            string subscriberName = instanceName;
            string publisherName = instanceName;
            string publicationName = "AdvWorksSalesOrdersMerge";
            string subscriptionDbName = "AdventureWorksReplica";
            string publicationDbName = "AdventureWorks";
            string hostname = "adventure-works\garrett1";
            string webSyncUrl = "https://" + instanceName + "/SalesOrders/replisapi.dll";
 
            // Create a connection to the Subscriber.
            ServerConnection conn = new ServerConnection(subscriberName);
 
            MergePullSubscription subscription;
            MergeSynchronizationAgent agent;
 
            try
            {
                // Connect to the Subscriber.
                conn.Connect();
 
                // Define the pull subscription.
                subscription = new MergePullSubscription();
                subscription.ConnectionContext = conn;
                subscription.DatabaseName = subscriptionDbName;
                subscription.PublisherName = publisherName;
                subscription.PublicationDBName = publicationDbName;
                subscription.PublicationName = publicationName;
 
                // If the pull subscription exists, then start the synchronization.
                if (subscription.LoadProperties())
                {
                    // Get the agent for the subscription.
                    agent = subscription.SynchronizationAgent;
 
                    // Check that we have enough metadata to start the agent.
                    if (agent.PublisherSecurityMode == null)
                    {
                        // Set the required properties that could not be returned
                        // from the MSsubscription_properties table.
                        agent.PublisherSecurityMode = SecurityMode.Integrated;
                        agent.DistributorSecurityMode = SecurityMode.Integrated;
                        agent.HostName = hostname;
 
                        // Set optional Web synchronization properties.
                        agent.UseWebSynchronization = true;
                        agent.InternetUrl = webSyncUrl;
                        agent.InternetSecurityMode = SecurityMode.Standard;
                        agent.InternetLogin = winLogin;
                        agent.InternetPassword = winPassword;
                    }
                    // Enable agent output to the console.
                    agent.OutputVerboseLevel = 1;
                    agent.Output = "";
 
                    // Synchronously start the Merge Agent for the subscription.
                    agent.Synchronize();
                }
                else
                {
                    // Do something here if the pull subscription does not exist.
                    throw new ApplicationException(String.Format(
                        "A subscription to '{0}' does not exist on {1}",
                        publicationName, subscriberName));
                }
            }
            catch (Exception ex)
            {
                // Implement appropriate error handling here.
                throw new ApplicationException("The subscription could not be " +
                    "synchronized. Verify that the subscription has " +
                    "been defined correctly.", ex);
            }
            finally
            {
                conn.Disconnect();
            }
 
What does HostName parameter use for? What is that host? Subscriber€™s machine name instance name? Or Publisher€™s? Or Distributor€™s?
Why parameters PublisherSecurityMode and DistributorSecurityMode have value SecurityMode.Integrated? How it is used in the replication model for web synchronization? As I understood from the documentation, client (Merge Agent) should connect to the Subscriber, get the changes, connect to hosting server via HTTPS and perform transactions through the SQL Server Replication Listener, thus the internet login to the IIS should be used to perform all the operations on hosting server side? The same internet login will be used to get snapshot from UNC share?
If I€™ve chosen to use FTP to provide with snapshots, should I then provide ftp parameters to sp_addmergepullsubscription_agent stored procedure or they will be used automatically by ISAPI filters on hosting server?
Thank you.