![]() But if you intend to communicate across the internet, then both machines must have public IP addresses. If you are using TCP/IP solely on an intranet, then you can use private addressing. You may not notice that dynamic popups are not instantly available on a typical view when the Client and Server are on an Ethernet network, but when the Client is on a 56K modem, there will be a noticeable delay if the popup contains much data or is restricted by a complex query.ĭoes Helix TCP/IP work with both public and private IP Addressing? ![]() If you use dynamic popups on entry views, you would have to wait until all of the popup data was delivered to the Client before you could begin to work on the view. Without asynchronous communication you would not be able to open another view while waiting for a list to draw. To do this, the Server must be able to initiate contact with a Client when the data they have accessed is changed. Remember that the Helix Client/Server architecture features live updating of information on the Client's screen. Although you may typically think of Helix Client/Server as being driven by the Client, there are a great many things that are initiated by the Server as well. What does "asynchronous communication" mean?Īsynchronous communication is at the core of Helix Client/Server interaction. Therefore the IP Addressing scheme used on both ends must be such that the Helix application at either end can initiate contact when necessary. Not only can the Client initiate communication (similar to a web browser requesting a page) but the Server must also be able to initiate communication as well. In most cases, the root of the architectural difficulty is attributed to the asynchronous communication that happens between Helix Client and Server. Why doesn't Helix TCP/IP work with my internet setup? No, Helix Server can only support one communications protocol at a time. ![]() A description of Helix's current TCP/IP implementation is found on the Helix Client/Server and TCP/IP page.Ĭan I have some Client visit via TCP/IP and others via AppleTalk? Significant enhancements have been made and are available in Helix 5.3 and later releases. The TCP/IP implementation in Helix 5.0 through 5.2.1 is a rudimentary implementation. If you are using Helix 5.3 or later this link will take you to the correct page. This note discusses the TCP/IP implementation in Helix 5.0 through 5.2.1. Overview Services techdb Helix 8 Technotes Helix 7 Technotes Tips Issues Scripts Chat Repair Feature Requests Bug Reports FTP FAQs Technical Educational Professional 3rd Party Contact Us ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |