Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


ID: 25628, Update 1 for C++BuilderX 1.5

by Tim DelChiaro Email: Anonymous


C++BuilderX 1.5 Update 1 contains an expanded set of components for using the HTTP functionality included in Symbian's Series 60 2.0 SDK.
Download Details
FTP  download also available
CDN Login Required to Download. (You will be redirected to the login page if you click on the Download Link)
Network License Users

If you are a network license user, click  here  to download this submission.

To download this, you must have registered [one of]:
C++ Mobile Edition
C++BuilderX 1.5 Mobile Edition
C++BuilderX 1.5 Mobile Edition, Upgrade for Nokia Customers
Enterprise Studio for Mobile 1.5

For C++Builder, Version 1.5  to 1.5
Copyright: All rights reserved


Size: 1,342,302 bytes
Updated on Fri, 08 Oct 2010 13:55:25 GMT
Originally uploaded on Wed, 07 May 2008 18:19:53 GMT
SHA1 Hash: AF5C84D8D1941640D2564D0294A3C0B0F4D5A4CA
MD5 Hash: 8BB8B75D7894E94CBF9E59B2683714E4

    Explore the files in this upload

Description

C++BuilderX 1.5 Update 1

Release Notes

This document contains installation instructions for C++BuilderX1.5 Update 1, and describes the updated components for this release.

Table of Contents

Overview
Installation
Configuring the SDK
Using the HTTP Components
Running Examples
Known Issues

Overview

C++BuilderX1.5 Update 1 contains an expanded set of components for using the HTTP functionality included in Symbian's Series 60 2.0 SDK.

Installation

Following are the system requirements for C++BuilderX1.5:

  • Windows 2000 or Windows XP Professional operating system
  • Series 60 SDK
  • Perl 518 and JRE 1.3.1 (installed with the Series 60 SDK)
  • Mobile device or emulator

To install C++BuilderX:

  1. Double-click on install.exe in the C++BuilderX 1.5 Update 1 folder.
  2. Install C++BuilderX1.5 Update 1.

Configuring the SDK

To configure the SDK in the IDE:

  1. Choose Tools Symbian SDK Configuration.
  2. Click Add in the SDK Configuration dialog box.
  3. In the Add SDK Configuration dialog box, specify the SDK Path (e.g., C:\Symbian\7.0s\Series60_v20), select the appropriate template (e.g., Symbian OS 7.0s (Borland version), type a name for the SDK (e.g., Series 60 SDK 2.0 Borland), and click OK.
  4. You should see the SDK you just configured in the SDK Configuration dialog box.
  5. Click Close to close the dialog.

Using the HTTP Components

The following HTTP components are included with this release: These components wrap the RHTTPSession and RHTTPTransaction classes from Symbian, and provide helper functions for setting request headers quickly and easily. For API documentation, see CHttpSession.html and CHttpTransaction.html.
The error event handlers for both components will be called in the event of a code error, such as a function leaving unexpectedly. Errors returned by the remote server, such as a 404:Page Not Found should be handled in the Run methods.
Borland's implementation does not support filters directly, but filters can be created and manipulated by accessing the underlying RHTTPSession and RHTTPTransaction objects.

To create an HTTP Client:
  1. Create a new Symbian Series 60 GUI application using the 2.0 SDK.
  2. Select the Non-Visual Designer.
  3. Click on the CHttpSession component to select it, and drop it on the designer.
  4. Click on the CHttpTransaction component to select it, and drop it on the designer.
  5. In the Object Inspector, select the session you just created from the Session drop down to associate it with the transaction.
  6. Enter a URI in the URI field, or select a URI from the application string table.
  7. Select the HTTP method from the Method drop down (i.e. HTTP::EGET, HTTP::EPOST, HTTP::EHEAD).
  8. Implement event handlers for the CHttpSession and CHttpTransaction components.

Running Examples

  • A sample demonstrating the usage of the HTTP components will be provided with the final release.
  • You can run Series 60 1.2 examples and examples from C++BuilderX1.5 as you normally would.

Known Issues

The following known issues concern the current version of the product:
There are currently no known issues with this update.


Copyright © 2004 Borland Software Corp.
All rights reserved.

   Latest Comments  View All Add New

Move mouse over comment to see the full text

Server Response from: ETNACDC03