Blackberry PROFESSIONAL SOFTWARE FOR IBM LOTUS DOMINO - - RELEASE NOTES Guide de l'utilisateur Page 26

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 210
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 25
IBM Lotus Notes, Domino, Domino Designer 8 Release Notes
z
Policies - IBM Lotus Productivity Tools settings document
z
Policies - Window Naviigation settings in desktop policy settings document
z
Policies - Policy managment of Inbox cleanup on desktop policy settings document
z
Server command - Tell adminp process restart
z
Option to synchronize unread marks when creating replicas
1
z Allow diagnostic data to be sent to IBM
Java
z
Java console enhancements, for example, auto-connecting multiple, recently connected servers at
startup
z
Support Same Java Runtime
Replication
z
Streaming cluster replication
Security
z
AES cipher support for SSL. Domino 8 introduces the ability to configure the Domino server to use
the TLS
_
RSA
_
WITH
_
AES
_
128
_
CBC
_
SHA and TLS
_
RSA
_
WITH
_
AES
_
256
_
CBC
_
SHA ciphers for
SSL, as defined in RFC 3268.
z
Use of xACLS to protect Internet password fields in the Domino directory
Web Server
z
User-defined attributes can now be added to the
<HTML>
tag generated by the web engine. If the
field $$HTMLFrontMatter is present on a form, its contents will be placed in the generated HTML,
ahead
of the <html> tag, and the web server will not generate anything there automatically. The
expected use of this feature is to supply a custom <!DOCTYPE> declaration for the generated HTML.
Note that as with other of these special fields, it is the application designer's responsibility to insure
that the field is not visible on the form and that it does not allow POSTing of that field.
The content of the field is not used by the web server in any other way - it has no other effect on the
generated HTML other than as described above. For example, suppling a doctype of HTML 4.01
STRICT will not cause the web engine to generate strict HTML. The content of the field is not
validated in any way.
Limitation of thecurrent implementation: the special field is not recognized in custom response forms..
z
Users can now specify a custom
<!DOCTYPE>
declaration on a per form basis. If the field
$$HTMLTagAttributes is present on a form, its contents is placed in the attribute list of the <HTML>
tag. Note that as with other of these special fields, it is the application designer's responsibility to
insure that the field is not visible on the form and that it does not allow POSTing of that field.
The content of the field is not used by the web server in any other way - it has no other effect on the
generated HTML other than as described above. The content of the field is not validated in any way.
Limitation of current implementation: the special field is not recognized in custom response forms.
Footnotes
These features are not available for the System i platform in the current beta release.
15
1
Vue de la page 25
1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 209 210

Commentaires sur ces manuels

Pas de commentaire