Uploading Temporary Data Clause Samples

Uploading Temporary Data. This operation can be started by the user after logging in at the EAGLE portal. The EAGLE server will send a request to the FMA server using the dedicated service, providing only the user id of the logged in user. With the user id the FMA server identifies the data saved in the user dedicated area and sends it to the EAGLE server. Since the data was saved in the format sent by the EAGLE server, no conversion is needed on either side. After uploading the saved data will be deleted by the FMA server. The data that will be uploaded to the server will be structured as a Blinkster Response item. The title and the comment added by the user will be transmitted, as well as the operation type (see more detail on part 3.4 about this aspect of the History Item) and the whole Xml text that was transmitted by the Eagle Portal during the request. The deletion will be executed only after all the data is received properly by the Eagle Portal. This operation will be triggered by calling another Web Service of the FMA server, but it will happen automatically, after confirmation that the data saved on the server was properly received by the user. Therefore, it will avoid losing data if any problem occurs during the transfer.
Uploading Temporary Data. This operation can be started by the user after logging in at the EAGLE portal. The EAGLE server will send a request to the FMA server using the dedicated service, providing only the user id of the logged in user. With the user id the FMA server identifies the data saved in the user dedicated area and sends it to the EAGLE server. Since the data was saved in the format sent by the EAGLE server, no conversion is needed on either side. After uploading the saved data will be deleted by the FMA server.