PicLan-IP is now available for four native Pick platforms Modular Software is pleased to announce the immediate availability of PicLan-IP for four different native Pick systems:
With hosted MultiValue implementations, PicLan-IP brings a new level of performance, versatility, and simplicity to internet applications that make use of MultiValue DBMS environments. With native Pick environments, PicLan-IP does even more by providing not only the high-level internet application functions, but also the high-performance, low-level TCP/IP protocol stacks required for internet network communications. Instead of relying on tenuous links to non MultiValue internet services, PicLan-IP for native Pick hosts implements these same internet standard protocols and functions completely within the Pick environment. The result is a standards-based solution that is efficient, cost-effective, and elegant.
|Contents: ...||The PicLan-IP Native TCP/IP Stacks
The PicLan-IP TELNET Server
The PicLan-IP Coyote Web Server
The PicLan-IP Web Client
The PicLan-IP Mail Server
The PicLan-IP TCP/IP Sockets API
PicLan-Ip for native Pick Implementation Details
PicLan-IP includes a full featured TCP/IP protocol implementation for ethernet and fast ethernet connections that runs concurrently with the IPX protocol support that is a part of the PicLan IPX product. The PicLan-IP TCP/IP protocol stacks are implemented in the same high-performance 'C' code state-machine that is used to implemnet PicLan IPX support. The result is a very fast, reliable TCP/IP support layer on native Pick platforms.
|TCP/IP Standard||The PicLan-IP stacks implement all of the required TCP/IP elements including IP, ICMP, UPD, TCP, ARP, static route tables, and Ping.|
|Virtual Hosting||The PicLan-IP TCP/IP stacks support up to 50 local IP addresses on a single network adapter.|
|You can use PicLan-IP with the same set of ISA and PCI bus Ethernet and Fast Ethernet adapters that run with IPX PicLan.|
|PicLan-IP TCP/IP operations do not interfere with PicLan IPX connections. You can freely use TCP/IP and IPX services on the same host with the same network adapter.|
|The PicLan-IP TCP/IP stacks are user configurable to support as many as 4000 concurrent TCP/IP connections (on servers with sufficient RAM). This allows native Pick host to support even large web server applications with ease.|
The PicLan-IP inbound TELNET functions are very fast and low latency using experience gained in deploying PicLan IPX services on over 5000 Pick host systems. This allows users access to TCP/IP TELNET services with native Pick hosts for both intranet and internet use plus the added option of using industry standard TELNET terminal servers as an additional serial connectivity option.
One added benefit of PicLan-IP inbound TELNET services is the level of configurability that PicLan-IP provides. Unlike most Unix and NT TELNET servers, PicLan-IP allows you to configure not only what TCP/IP addresses and ports are used, but also what client IP addresses are allowed. This allows you to manage your TELNET connections in a single centralized configuration file allowing access to users that you choose, and restricting access to others. All without requiring a firewall.
And finally, PicLan-IP inbound TELNET services support full connecting logging operation as well as connection definitions that are designed to make terminal server operation seamless and reliable
There are a number of reasons why running the Web Server as a MultiValue application makes sense:
|Web Server||Built-In||Requires External Server|
|Performance||Very fast - all processing takes place in a single centralized location within a single process model.||Slow - numerous processes have to exchange information using slow interfaces like CGI and pipes.|
|Setup||Easy - all configuration items are controlled within the MultiValue environment.||Difficult - Multiple products must be installed and configured in several run-time environments.|
|Control||Excellent - All web functions are controlled within the MV environment.||Poor - Web Server functions are beyond the reach of MV applications.|
|Logging||Excellent - MV applications control all web logging function in MV format. You control what informaton is logged and in what format.||Poor - Web Server logging functions are controlled by the external web server and are difficult to manipulate with MV applications|
|Excellent - Active Server Pages with embedded mv/BASIC source code. All processing occurs in MV code with MV format data structures.||Poor - Application must map MV data to ODBC or use cumbersome subroutine based APIs.|
|Development Environment||Excellent - Use any HTML editor. Application error messages can be configured to go to the browser, monitor console, or log files. Use of mv/BASIC debugger is supported.||Proprietary or none - MV interface uses obscure subroutine calls or non-MV data structures.|
|Error Reporting||Excellent - Application errors are logged and user-controlled error displays are generated in plain english to the end-user.||Poor - Application errors usually result in generic "no response" messages with little indication of the source of errors.|
|Live Development||Excellent - Applications can be updated real-time with live users on-line.||Poor - server components may need to be restarted with many type of application changes.|
|Application Persistence||Excellent - mv/WEB environment handles persistence transparently with added support for timed item-locks.||Some good, some poor - Hidden input fields and cookies may require manual decoding of HTTP headers and input fields. Unknown support for item-locks.|
|Reliability||Excellent - All server functions are fully watch-dogged. True 24x7 operation is designed in.||Poor - Many server functions reside in environments that require manual intervention upon failure. Poor implementation for 24x7 applications.|
|Cost||Low - The PicLan-Ip licensing cost is all that is required. You do not need to license external servers. PicLan-IP also runs on MultiValue phantom processes, so no MultiValue user licenses are consumed.||Low to High - Depending on the configuration, you may need to license external web server software or even purchase additional host computers. Some solutions also consume MultiValue user licenses depending on their implementation.|
|HTTP/1.0 Standard||PicLan-IP implements the entire HTTP/1.0 standard. Web users have no way of knowing they are conversing with a MultiValue host (unless you tell them).|
|Virtual Hosting||PicLan-IP supports up to 50 independent sets of web content. One MultiValue host can appear to the world as many independent web sites and applications.|
|The PicLan-IP web server supports user-definable web content including HTML, TXT, GIF, JPEG, EXE, ZIP, WAV, and other types that you can easily define.|
|The PicLan-IP web server implementation is fully multi-threaded taking full advantage of multi-CPU hardware platforms and overlapped I/O and CPU processing.|
|Server-side Caching||The PicLan-IP web server makes extensive use of server-side caching to reduce server overhead when a page is accessed more than once. Nearly every concievable web element, from HTTP headers to active server page merge logic, is "compiled" the first time a page is accessed. This logic allows the web server to use intelligent "machine code generation" techniques to produce web interfaces that are actually faster than could be hand coded.|
|Standard||Any web page can include mv/BASIC source code to generate dynamic web responses.|
|Default||You can setup web directories, or entire IP addresses to call a single default active server page for any URL. This allows you to easily implement global security and access control, sense browser configurations, etc. all from a single block of mv/BASIC source code.|
|Error||If web processing results in an HTML error condition (such as page not found), you can specify an error page that can then present this error to the user with additional information beyond the simple error code. These error pages are specified independently for each IP address that the server is servicing.|
Some applications for the PicLan-IP Web Client might include:
Having a mail server in the MultiValue environment has the advantages of:
PicLan-IP server functions are implemented as event-driven Pick/BASIC applications that execute on Pick phantom processes. PicLan-IP does not consume any Pick user licenses (except for inbound TELNET connections), regardless of the number of TCP/IP connections utilizing PicLan-IP services. PicLan-IP server process "threads" are user configurable to take advantage of overlapped CPU and disk operations and scale well with system configuration.
All network traffic is extensively buffered and event-driven in a state-machine driver engine that sits directly on top of system interrupts in the 32-bit flat-model kernel environment. This offloads most network control functions from the Pick/BASIC environment allowing a very small number of PicLan-IP server processes to service literally thousands of concurrent TCP/IP connections.
One additional note, because PicLan-IP on native Pick hosts has its own TCP/IP protocol stacks, system security is actually better than on a hosted system. This is because PicLan-IP does not have any back doors or complicated code paths that can allow intruders access. PicLan-IP truly does keep it simple.