[#UBA-7595] Improve handling of client system properties

ULCBase

Improve handling of client system properties

Created: 07/Nov/08 04:57 PM Updated: 07/Jan/09 04:13 PM

Component/s:

core

Affects Version/s:

None

Fix Version/s:

UltraLightClient '08 Update 2

Issue Links:

Reference

This issue relates to:

~~UBA-7639~~ Properties instances are wrong encoded

Description

« Hide

In a ULC application the client system properties are accessible with ClientContext.getSystemProperty(). However, by default only the system properties that can be read in the sandbox are available. A better approach would be to send the reduced set only if running in the sandbox and to send all system properties if running outside of the sandbox.

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Janak Mulani added a comment - 10/Dec/08 07:15 AM

ClientInfo.getDefaultSystemProperties returns all System properties if ULC client is running with full permission else it returns predefined properties

[ Permalink | « Hide ]

Daniel Grob added a comment - 17/Dec/08 09:14 PM

Reopened because most system properties are default properties. And because of ~~UBA-7639~~ all default properties are lost during encoding. So we first have to fix ~~UBA-7639~~.

[ Permalink | « Hide ]

Janak Mulani added a comment - 19/Dec/08 01:53 PM - edited

Created PropertiesCoder.

But even before that there were 35 properties available on server in Signed Applet mode on windows XP, Java 6 and FireFox

Dany reported that on Mac only 2 properties were available suspecting that Properties(properties) ctr was being used and MapCoder was not sending the default properties.