Академический Документы
Профессиональный Документы
Культура Документы
Function
Address
Operator
Redirection
Client
General purpose
General Purpose
Member Enquiries
U-MAS advices
Offers from Members
Google Calendar
No-email members
Mail to President
Mail to Secretary
Mail to Treasurer
Mail to Documentation
Indigo.u3a@icloud.com
Indigo.u3a@gmail.com
Courses.indigo.u3a@gmail.com
System.indigo.u3a@gmail.com
Volunteer.indigo.u3a@gmail.com
U3aprogram@gmail.com
Common.indigo.u3a@gmail.com
President.indigo.u3a@gmail.com
Secretary.indigo.u3a@gmail.com
Treasurer.indigo.u3a@gmail.com
Documentation.indigo.u3a@gmail.com
Secretary
Secretary
Course Coordinator
Administrator
Secretary
Program Coordinator
Secretary
President
Secretary
Treasurer
Webmaster
Indigo.u3a@gmail.com
none
none
none
none
unknown
none
President private email
none
none
none
webmail
HGB PC
HGB PC
HGB PC
HGB PC
unknown
HGB PC
various
HGB PC
HGB PC
HGB PC
There are several ways Operators can access the email on a per function basis:-
Hardware
Class
Protoc Notes
ol
Any
browser
Browser
Mail App
TCP/IP
Client
software
Server based
email
Server based
email
Client based email
Client based email
Softwar
e
TCP/IP
IMAP/SM
TP
POP/SMT
P
IMAP/SM
TP
Cloud note: There is always going to be some Indigo U3A Inc. data that should be considered unsuitable to be stored en
masse in Cloud Storage. The Membership Register is a case in point not withstanding that its primary repository is the wed
based U-MAS service.
When one considers other activities that will evolve, of necessity, out of the move to U-MAS a Windows PC (or a MAC???) is an
imperative.
The probability is that some common storage facility accessible from several PCs concurrently will be required will be
required
How much concurrent access to any given record in any system will be required is not yet understood. Having said that
concurrent access for READ should never be a problem but concurrent access for UPDATE will be a problem and protocols to
avoid conflict must be maintained.
(NON SEQUITUR
I wonder what happens to the U-MAS database Member Number determination if several NEW Members apply
concurrently and some cancel the operation mid-stream. Hopefully the numbers are allocated and updated
during a one lane queued commit phase??)
ASK