|
Home > Archive > SQL Anywhere Mobile > June 2005 > What does ML use to sync over HTTP/HTTPS?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
What does ML use to sync over HTTP/HTTPS?
|
|
| Michael Luggen 2005-06-09, 3:24 am |
| Hi,
I guess MobiLink opens a TCP/IP connection to the
MobiServer. So also users behind routers and firewalls can
sync. Or trys the server to connect back to the client?
Which port's does ML use in case of standart?
thx a lot
greets ml
| |
| Reg Domaratzki \(iAnywhere Solutions\) 2005-06-09, 9:24 am |
| By default, MobiLink listens on port 80 when using HTTP and port 443 when
using HTTPS. I'm not sure if I answered your question or not though.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
<Michael Luggen> wrote in message
news:42a7e035.254a.1681692777@sybase.com...
> Hi,
>
> I guess MobiLink opens a TCP/IP connection to the
> MobiServer. So also users behind routers and firewalls can
> sync. Or trys the server to connect back to the client?
>
> Which port's does ML use in case of standart?
>
> thx a lot
>
> greets ml
| |
| Greg Fenton 2005-06-09, 9:24 am |
| Michael Luggen wrote:
>
> I guess MobiLink opens a TCP/IP connection to the
> MobiServer. So also users behind routers and firewalls can
> sync. Or trys the server to connect back to the client?
>
I'm not sure what your definition of "MobiLink" and "MobiServer" is.
There is the MobiLink Server (usually referred to as just "MobiLink" or
"ML") and there are the MobiLink clients (dbmlsync for ASA remotes, and
UltraLite itself is a ML client).
The ML server opens whichever ports you indicate in your startup
parameters. By default it will start a TCPIP listener on port 2439.
However you can start ML with "-x http" (defaults to port 80) or "-x
https" (defaults to port 443), or you can specify any unused port (e.g.
"-x tcpip(port=5555)") or even multiple ports ("-x tcpip(port=5555) -x
http(port=8080)").
If you are opening a port in your firewall so that clients can directly
connect to ML, then it typically makes more sense (and gives better
performance) to use TCPIP rather than HTTP. You typically use HTTP when
either the requests will be proxies/redirected through an existing
webserver or if clients will be coming from behind a firewall/proxy that
only allows HTTP traffic.
Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
| Michael Luggen 2005-06-15, 11:25 am |
| Thanks a lot...
exactly the syntax i searched: tcpip(port=5555)
greets
> Michael Luggen wrote:
>
> I'm not sure what your definition of "MobiLink" and
> "MobiServer" is. There is the MobiLink Server (usually
> referred to as just "MobiLink" or "ML") and there are the
> MobiLink clients (dbmlsync for ASA remotes, and UltraLite
> itself is a ML client).
>
> The ML server opens whichever ports you indicate in your
> startup parameters. By default it will start a TCPIP
> listener on port 2439. However you can start ML with "-x
> http" (defaults to port 80) or "-x https" (defaults to
> port 443), or you can specify any unused port (e.g. "-x
> tcpip(port=5555)") or even multiple ports ("-x
> tcpip(port=5555) -x http(port=8080)").
>
> If you are opening a port in your firewall so that clients
> can directly connect to ML, then it typically makes more
> sense (and gives better performance) to use TCPIP rather
> than HTTP. You typically use HTTP when either the
> requests will be proxies/redirected through an existing
> webserver or if clients will be coming from behind a
> firewall/proxy that only allows HTTP traffic.
>
> Hope this helps,
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/
|
|
|
|
|