Re: MsgCommunicator v.2.00: Instant Messenger SDK, now with databases support

Just a note on the side ...

using a proprietary protocol built on top of UDP is closing corporate doors
for your product. I think that, if you would offer the same functionality
over the HTTP protocol, your potential customer base would increase
dramaticaly, since you would break the LAN barrier and make the Messenger
Server available from any PC having access to Internet. Remote work is
getting more and more popular, with corporate Networks spreading wide across
the Internet.

Since the number of clients inside a LAN will never be as big as the
potential number of clients over the Internet, the capability of your
current implementation to handle virtualy unlimited number of clients is not
really important. It would be more than enough if your server was able to
handle 32K clients.

In other words, if I would be extending the RTC Messenger with features like
message history, message search and user search (which now make your product
unique), AidAim MsgCommunicator would have to share the market with RTC
Messenger. And in its current implementation, it would have a big
dis-advantage, called "propriatery UDP protocol", which is making it
un-suitable for use over the Internet.

Maybe you should consider a re-design.

--
Danijel Tkalcec
http://www.deltasoft.hr/rtc/author.htm

RealThinClient components
-------------------------------------------
* The Easiest way to build Internet-enabled applications
- Clients, Stand-alone Servers, ISAPI extensions -
> Write and Call Remote Functions
> Download and Upload Files
> Single- and Multi-Threaded mode
> Firewall friendly - all over HTTP
> Stress-tested for highest stability

http://www.deltasoft.hr/rtc
http://www.deltasoft.hr/rtc/forum


.

Relevant Pages

  • Re: New to ISA
    ... Is it safe to have protocol and content ... > The ports that will open are for the external interface of ISA Server ... > ISA Server 2000 can't use packet filters for NATed clients. ... >> All i want to do is NATing to my internal web servers and internet ...
    (microsoft.public.isaserver)
  • Re: New to ISA
    ... You should limit the clients that are allowed to use Any IP traffic. ... >>> Protocol rules are used to allow clients inside your networ to go out ... >> The ports that will open are for the external interface of ISA Server ... >>> All i want to do is NATing to my internal web servers and internet ...
    (microsoft.public.isaserver)
  • Re: New to ISA
    ... > Protocol rules are used to allow clients inside your networ to go out to ... The ports that will open are for the external interface of ISA Server ... ISA Server 2000 can't use packet filters for NATed clients. ... > All i want to do is NATing to my internal web servers and internet access, ...
    (microsoft.public.isaserver)
  • Re: Internal clients able to FTP out
    ... the ISA on-line documentation. ... And the "Small Business Internet Access Protocol Rule" allows all IP traffic ... >> Yet internal clients, using the Firewall client, are able to access ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN PPTP problem
    ... Internet Security and Acceleration Server 2004 Standard ... | Protocol Info ... | Header checksum: 0x7708 ... | Transmission Control Protocol, Src Port: 1619, Dst Port: pptp ...
    (microsoft.public.windows.server.sbs)