Communications (communications layer):

The communications layer provides the Transports in the system with means by which they can communicate to other platforms. The communications layer recycles endpoints for speed (reduces endpoint setup time).

Available communications methods:

• TCP/IP:
  1. Through the use of the NIE, able to communicate over PPP/SLIP/MacIP/Ethernet;
  2. Caches resolved domain names for speed (NIE is slow).
• Serial/Modem:
  1. Allows for services to be accessed through modem;
  2. Login/Logout scripts for accessing e.g. Unix accounts.

Transports (transport layer):

Transports are responsible for communicating with a remote source/server. They arrange for the transport of data between the Newton and the remote source.

All transports use Newton's Owner/Worksite card mechanism to store user and site dependent configuration data, and have the ability to activate at a certain time (scheduling). Every transport makes use of status dialogs through which the user is informed.

Since all transports are based on one very powerful framework, they all share the same functionality. A plug-in API allows for other transports to make use of this framework. Through the merge feature, two items in the outbox can be merged into one. This is useful for attaching some data to an email written in the Notepad.

Available transports:

• InetSMTP (outgoing only)
• InetPOP3 (incoming only):
  1. Browse mode. Downloads headers first and stores messages as 'remote', after which downloading of messages will run in background. User can tap messages to download first;
  2. Ability to keep 'remote' messages in inbox after disconnect and perform operations such as retrieve and delete;
  3. Delete, reply, forward or redirect any message;
  4. Can leave mail on server;
  5. Ignore large messages (configurable). Downloads headers only;
  6. Add message sender to names application.
• InetHTTP (incoming only):
  1. HTTP 1.0 (GET and POST);
  2. Talks to proxy servers;
  3. Supports serverside persistent Cookies;
  4. Authentication is supported for the simple and basic methods;
  5. Thorough cache management.
• InetFTP (incoming/outgoing):
  1. Standard FTP protocol;
  2. Uses either PASV or PORT for active or passive operations (firewalls);
  3. Knows about directories.

Conversions (conversion layer):

The conversion framework is responsible for converting data from an outside source, to Newton savvy data, vice versa. This is what implements the MIME (Multipurpose Internet Mail Extensions) compatibility. It will ensure that data, not especially formatted for Newton, will get converted, so it is usable on your Newton. This applies to all types of data such as: images, packages, sounds, and text. By chaining the various converters, a very powerful system is created. The support for MIME types can be easily extended by third-party developers through the extensive API.

Converted data can be viewed in two ways. It can either be viewed in a context that adds routing and history, or it can be put away into a destination application (such as notes can be put away into Notes, etc) and be viewed there, with whatever facilities that application provides.

Note that it does not matter through which transport data arrives. All incoming data will be converted by the conversion framework. So, e.g. is does not matter whether an HTML page is received through the HTTP, FTP or POP3 transport, the result will be exactly the same. Same goes for outgoing data.

Available conversions:

• UUEncode
• Base64
• Quoted-Printable

• HTML (one way)
• JPEG (one way)
• GIF (animating, one way)
• Sun Audio (.au) (one way)
• Versit Objects (vCard):
  The vCard standard is supported by Apple, Microsoft, Netscape, Siemens, and AT&T to name a few companies. LunaSuite's Versit Object implementation will allow users to exchange cards and calendar events with vCard users and servers independent of platform.
• Newton native data (e.g. packages, namecards, etc.):
  1. Enables a Newton device to send data to other Newton device.
• Multiparts:
  1. Supports mixed, digest and alternative;
  2. Used for e.g. attachments to mail.

Stationery (display layer):

Most data on the Newton is viewed using Stationery, a very powerful mechanism which in some respects resembles OpenDoc/OLE types of implementation. LunaSuite provides a number of stationery viewers to view data.

Available stationery:

• HTML:
  1. All basic style elements;
  2. True alignment (inline);
  3. Forms;
  4. Frames;
  5. Tables;
• BitMap (GIF (animating), JPEG)
• Sound
• Multipart
• Text (email):
  1. Fast scrolling through the use of new protoTXView;
  2. Looks like the text editor in Newton Works.
• Headers (email):
  1. Nicely formats headers with styles.

Go-To:

The Go-To application can retrieve a given URL and will display it. It provides a view with shortcut-buttons with which the user can compose a URL.

Bookmarks:

The Bookmarks application allows the user to create a list of bookmarks. Bookmarks are stored in folders. Every bookmark can contain several URLs. Selecting a bookmark will retrieve the document associated with it.

LunaSuite Roamer:

The LunaSuite Roamer is the frontend to the HTTP and FTP transports. Through this application users have access to their Bookmarks and all system wide preferences. Access to the Go-To application is also provided.

The Roamer can hide the standard Newton button bar in order to make more screen space available for viewing documents.

LunaSuite Setup:

The whole LunaSuite can be configured by a first-time user by using the LunaSuite Setup application. This application will walk the user through each component of the LunaSuite, and will guide the user in the configuration (such as email address, connection method, etc). This application is mostly used for the email transports since the FTP and HTTP transports do not require any configuration before they can operate.