- **summary**: IMM: DEprecate support for infinitely long class-names --> IMM:
Deprecate support for infinitely long class-names
- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -8,7 +8,7 @@
not just impose a sanity limit on class-name-length.
But the immsv can define a config attribute that is analogous to the attribute
-'longDnsAllowed' (introduced in 4.59) that we may call 'longClassNamesAllowed'
+'longDnsAllowed' (introduced in 4.5) that we may call 'longClassNamesAllowed'
This attribute will by default be 'true'.
The idea is to allow deployments that are sane, i.e. dont currenlty have any
~~~~
---
** [tickets:#1148] IMM: Deprecate support for infinitely long class-names**
**Status:** unassigned
**Milestone:** 4.6.FC
**Created:** Wed Oct 01, 2014 02:11 PM UTC by Anders Bjornerstedt
**Last Updated:** Wed Oct 01, 2014 02:11 PM UTC
**Owner:** nobody
Currently (due to an omission) the immsv has no sanity limit for the length
of class-names.
Thus the immsv currently "supports" infinitely long class-names.
In practice this means the actual limit is resource dependent.
Due to the overriding principle of always being backwards compatible, we can
not just impose a sanity limit on class-name-length.
But the immsv can define a config attribute that is analogous to the attribute
'longDnsAllowed' (introduced in 4.5) that we may call 'longClassNamesAllowed'
This attribute will by default be 'true'.
The idea is to allow deployments that are sane, i.e. dont currenlty have any
applications with any class-name longer than 255 bytes, to prevent any such
application from being added.
Setting the attribute to false will only be allowed if the system
currently has no class with a classname longer than 255 bytes.
The reason for deprecating infinitely long class-names is of course that such
long class-names are just inconvenient for everyone and a sign of some form
of failure in application design.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
