MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Especificaciones descargar pdf (Pagina 136)

Chapter 458

Because shared object and stream names are strings, and both follow the same rules of URI-

encoded data, you can define access based on the name. The

client.readAccess and

client.writeAccess commands take string values. These values can contain multiple string

tokens, or unique identifiers for the object names you want to control, separated by semicolons

(

;). Here are two example strings:

client.readAccess = "appStream;/appSO/"

client.writeAccess = "appStreams/public/;appSO/public/"

Using these calls and the string token convention, you can create shared objects and streams that

follow well-defined patterns. For example, suppose all shared objects created by the application

start with the prefix

appSO; shared objects available for all users begin with the prefix appSO/

public

; and shared objects you want to protect have the prefix appSO/private.

If you set the read access as follows:

client.readAccess = "appSO/"

the server will allow all connected clients to subscribe to shared objects whose name begins with

appSO.

Similarly, you can make the call:

client.writeAccess= "appSO/public/"

and the client can create only shared objects with names beginning with appSO/public, such as

appSO/public/foo, but would be denied access to appSO/private, and so on.

By using the above feature, and designing a naming scheme for streams and shared objects, you

can implement ACL. For more information, see the

Client.readAccess and

Client.writeAccess entries in the Server-Side Communication ActionScript Dictionary.

Debugging your application

This section includes recommendations to help you debug your Flash Communication Server

applications, including tips on using debugging tools and writing onStatus functions.

Using debugging tools

Flash Communication Server provides three powerful tools to help you debug your

applications—the Administration Console, the Communication App inspector, and the

NetConnection Debugger. You should have one or more of these open while you are debugging

your application, in order to see exactly what log messages are being generated, how object values

are being set and updated, etc. For more information on the Administration Console, see

Managing Flash Communication Server. For more information on the App inspector and the

debugger, see the Appendix, “Flash Communication Server Management Tools,” on page 97.

Using onStatus event handlers

The client-side Camera, Microphone, NetConnection, NetStream, and SharedObject objects, as

well as the server-side Application, NetConnection, Stream, and SharedObject objects, provide an

onStatus event handler that uses an information object for providing information, status, or

error messages. To respond to this event handler, you must create a function to process the

information object, and you must know the format and contents of the information object

returned.

1 2 ... 131 132 133 134 135 136 137 138 139 140 141 ... 368 369

Comentarios a estos manuales

Sin comentarios

MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Especificaciones Pagina 136

Comentarios a estos manuales

Relacionado con productos y manuales para Servidores MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY