readme

g-page 是一款客户端/服务器应用程序

################################################################################
################################################################################
###                                                                          ###
###                                                                          ###
###  g-page version 2.03                                                     ###
###  Author: Hiro Protagonist                                                ###
###  Initial release date: 05/15/00                                          ###
###  License: GPL                              			             ###
###  Send bugs to [e-mail]                        ###
###                                                                          ###
################################################################################
################################################################################
##                                                                           ###
##      This software falls under the GNU Public License. Please read        ###
##                   the LICENSE file for more information                   ###
##                                                                           ###
##     THIS SOFTWARE COMES WITH NO GUARANTEE  USE AT YOUR OWN RISK !!        ###


If you find a bug in g-page, regardless of how small or trivial it might
be, please let me know at [e-mail]. 

                                OVERVIEW

G-page is a client/server application designed to send alphanumeric
messages from a computer running Linux/*nix to a wireless receiver. All 
messages are created from the client and sent to the server for processing. 
The server requires an Internet connection and can be running on the same 
computer or anywhere with a tcp/ip address.


                                PLATFORMS

G-page is supported and known to compile and run on AIX, HP-UX, Solaris, 
Linux and FreeBSD. It should be trivial to get it to compile on any other 
*nix and I would be happy to assist you if you have any trouble doing so.

                                BUILDING

You will need to have GTK+ installed on your computer, including the development 
libraries, in order to build g-page. I am currently using version 1.2.10 of GTK+ 
however g-page should compile with no problems with older versions. Both the gpage 
client and server require pthreads. The server requires two additional libraries, 
expat and ghtml, both can be downloaded from my project website. The database
server doesn't require any additional libraries.

	After you gunzip and untar the source files ( use 'tar zxvf' to unzip and 
untar the files in one command if you're using the Gnu version of tar) you should 
now have three new directories: /Client and /Server and /db_server.

The commands to build the client and server and database server are identical 
with the exception of building the client on FreeBSD. Change into each of the
three directories and perform the following.


FreeBSD:
To build the client:
make -f MakefileBSD
to build the server and database server:
make bsd

To build gpage on AIX:
make aix

To build gpage on HPUX: (11.0 or newer)
make hpux

To build gpage on Solaris:
make solaris

To build gpage on Linux:(any distro)
make
 

This should compile the program. If all goes well you should end up with a binary 
named gpage for the client, gserver for the server and db_server for the 
database server.. If all doesn't go well you might have to tweak the makefile a 
little. 

To install the binares into the /usr/local/bin directory do a:
make install


Note - you may need to be root to do make install as you need permission to write
a file into the /usr/local/bin directory.

                                  BINARIES

	If you downloaded the non statically linked binaries you will need to have 
glibc and Gtk+. The Linux binaries were compiled on RedHat 8.0 with Gtk+ v1.2.10 with gcc
3.2 but they should work with older libraries. If they don't work for you then you will 
need to compile the source code. (Don't worry, it's very easy to do)

                             RUNNING THE CLIENT

The gpage binary can be placed in any directory in your path. The first time 
g-page is run the software will create a new directory called .gpage in your home 
directory. It will then create blank database files for that directory. If you 
wish to store your database files in a different directory you will need to click 
on the "Pref" button on the toolbar and click the "change" button, then select 
the directory you wish to keep your g-page database files in. You will need to 
create the directory manually if it doesn't already exist. The only file that 
must reside in ~/.gpage is the CONFIG.dat file. This is the file that holds all 
your configuration settings, including the location of the current database 
files. You cannot move this file or gpage will not work.

You will need to setup the client before you can send any pages. Start
gpage and  click on the "Config" button on the toolbar. You will need to fill
in all the fields:

Server IP address: This is the IP address where the paging server resides. If you 
are running the server on your computer then the default "localhost" is correct.

Server Port: This is the port number that the server is listening on. You can use 
any port as long as the server is setup to listen on that port, and of course it
cannot conflict with any well known ports in use. The default 1299 was picked
for no good reason. 

ISP Domain: This is the domain of the isp you are using. If your email address
is [e-mail] you will type foobar.com in for your isp domain.

Email Domain: This is the domain you log into to send email. This is the same 
domain you use for your email client. For instance if your isp email server is
mail.foobar.com you would enter that.

Timeout: This is the maximum number of seconds for the client to stay connected 
to the server. When the client sends the pages to the server it stays connected 
and reports back status as it's sending the pages. The client will timeout if it
does not get any information in x seconds. This will stop gpage from hanging
if something evil happens to the server. A value of 120 should be fine for most
people. You might want to sent it higher if you are using a horribly slow
Internet connection. If the client does timeout it will not stop the server
from sending any messages, it simply means that you will not get any status
report back for logging purposes.

Email address: If you are going to send pages via email you will need to enter 
your email address. Most paging companies will put this in the actual message 
that is send to the pager for identification if you are sending a page via email. 
You can put a dummy address in like [e-mail] as long as it is in the standard 
format of a regular email address. You can also put in a pager email address
and any 2 way pager replying to a message will send their message to your pager.

If you are only going to send pages via snpp you can leave the default values for 
all the email settings.


	                  SETTING UP A SERVICE

	You will need to enter a wireless service before you can enter a 
pager or PCS phone. Click on the Service button on the toolbar. The list service 
dialog box should pop up, click on the add button. Fill in the appropriate fields 
for your paging service. For example if you use Pagenet for your service you will 
fill in Pagenet for service Name. Fill in the Max msg length field next. This is 
the maximum number of characters that this paging provider allows per text
page. If you don't know what the maximum number is you can contact the paging
provider and get the number from them. If you are unable to contact them you
can use 80 and it should be okay. If you put a number that is larger than what
the service provider allows the message will be truncated by the paging company
or in some cases they will reject the page. It's best to use the correct value.

Protocols Supported: Now you need to select the protocols supported by this
paging company.

If you are using a service that supports the WCTP protocol you will need to 
enter the address of their server in the field named WCTP Setup. It's important
to note that http:// MUST prepend every address or you will get an error when 
you try to send a page. If your not sure if your paging service supports
WCTP you will need to contact them. I will provide the server addresses for
the major paging companies when it's available.

If your paging service requires a password to use their snpp server then 
select the "yes" button when asked this question and be certain to fill in
the password in the proper field below. Otherwise leave the "no" button selected.

SNPP Setup: If this paging provider supports snpp you will need to fill in
the information for their snpp server. A list of some of the main ones are 
listed at the bottom of this file. The password field is usually not used by
any of the major paging companies, you are probably safe to leave the field blank 
in most cases. If you leave the field blank the software will automatically fill 
in "none" for you.

That's it, click Save and you are done!! Now you need to setup the pager or PCS
phone.

	                  SETTING UP A RECEIVER

	Click on the Receiver button on the toolbar. The list receiver dialog
box should pop up. Click on the add button to get the add receiver dialog box.
Enter the name of the person using this receiver and the receiver number. If 
you are going to send messages via snpp to this receiver you will need to 
enter the full 10 digit number of the pager/phone. If you do not enter the 
full number the page will fail. I believe that WCTP also requires a 10 digit 
pager number. If you are uncertain if your pager/phone needs a 10 digit or
7 digit number you can try experimenting on your own or contact your service
provider.

Select Protocols: Next you will need to select the protocols used by this
receiver. If you select SMTP you will have to enter the email address of 
the receiver in the next field, otherwise you can leave it blank. The 
protocols you select will now be enforced by the software, if you select 
all three protocols g-page will try to send the message via WCTP, if that fails
it will try it via SNPP, if that fails it will try to send it via Email. It
is important to only select protocols for a receiver that are supported
by the messaging service you are using. Otherwise you will generate many
failed pages. Also note that you don't have to enter all the protocols supported
by a specific receiver if you don't wish to use them. for example, if your 
pager supports email paging but you don't want to send a page via email then 
you would leave that SMTP box unchecked. You can also change the order in 
which g-page will try to send a page by setting the protocol precedence
under the pref->protocols->Set protocol precedence from the main toolbar.

Receiver Email Address: If this pager/phone has an email address you will
enter it here. Most wireless service providers attach an email address to 
their pagers and phones. This is not the most efficient way to send a message
but will work if you have no other option. If you are going to use the "cc to 
email" option then you should put the email address of the person using that pager 
in this field, not the pager email address. This is a little confusing and will
be cleaned up in version 2. When you choose to send a cc of every page to an email 
address the person carrying that pager gets a record of every page sent to them 
copied to their email.

SNPP Options: g-page supports sending 1.5 and 2 way messages via 
the snpp protocol. Selecting the 1.5 protocol will activate the
page-read acknowledgment for any message sent to that pager. Selecting 
2 way allows you to send specific responses for the pager to select for
a response. You must be certain that the pager is capable of these
functions and setup properly with the paging service to send a 1.5 
or 2 way message.

WCTP Options: g-page supports three different sending methods for the WCTP
protocol, one way paging, 1.5 way paging and 2 way.. One way means the message is 
sent to the pager and there is no further action. 1.5 way paging means that
if you are sending to a pager (typically a two way pager) with 1.5 way 
messaging enabled, the pager will send a confirming email to your default