Chapter 5. Communicating with the Server

Chapter 5. Communicating with the Server
Prev		Next

Table of Contents

Remote Communication in yFiles FLEX

Remote API

Class RoundtripHandler

Customizing Graph Serialization
Customizing Graph Deserialization and Update
Support for folded graphs
Transfer of additional data
Handling IDs with the RoundtripHandler
Custom Error Handling
Encoding GraphML Data
Subclassing RoundtripHandler
Using RoundtripHandler

Class DownloadHandler

Configuring DownloadHandler
Subclassing DownloadHandler

Class UploadHandler

Configuring UploadHandler

Class ImageExportHandler

This chapter describes how a yFiles FLEX client communicates with a server component through HTTP service requests. In order to benefit from automatic graph layout algorithms, yFiles FLEX needs a server component running yFiles for Java or yFiles.NET. Since the yFiles FLEX client conducts server communication using the GraphML XML standard, it is also possible to create a yFiles FLEX application without yFiles Java or yFiles.NET using any server technology.

Remote Communication in yFiles FLEX

The yFiles FLEX client library provides an API for communicating with remote services using HTTP requests. In particular, the API makes it easy to exchange graph structure, layout, and style information with a servlet container running yFiles Java or yFiles.NET.

Although the Adobe Flex framework provides support for various means of server communication in addition to request-based HTTP round-tripping, the yFiles FLEX API currently uses only HTTP requests. Nevertheless, it is of course possible to use SOAP, remote objects, or Flex Data Services with the GraphML I/O API of yFiles FLEX.