Chilkat Examples

ChilkatHOME.NET Core C#Android™AutoItCC#C++Chilkat2-PythonCkPythonClassic ASPDataFlexDelphi ActiveXDelphi DLLGoJavaLianjaMono C#Node.jsObjective-CPHP ActiveXPHP ExtensionPerlPowerBuilderPowerShellPureBasicRubySQL ServerSwift 2Swift 3,4,5...TclUnicode CUnicode C++VB.NETVBScriptVisual Basic 6.0Visual FoxProXojo Plugin

PowerBuilder Examples

Web API Categories

ASN.1
AWS KMS
AWS Misc
Amazon EC2
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Key Vault
Azure Service Bus
Azure Table Service
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Code Signing
Compression
DKIM / DomainKey
DNS
DSA
Diffie-Hellman
Digital Signatures
Dropbox
Dynamics CRM
EBICS
ECC
Ed25519
Email Object
Encryption
FTP
FileAccess
Firebase
GMail REST API
GMail SMTP/IMAP/POP
Geolocation
Google APIs
Google Calendar
Google Cloud SQL
Google Cloud Storage
Google Drive
Google Photos
Google Sheets
Google Tasks
Gzip
HTML-to-XML/Text
HTTP

HTTP Misc
IMAP
JSON
JSON Web Encryption (JWE)
JSON Web Signatures (JWS)
JSON Web Token (JWT)
Java KeyStore (JKS)
MHT / HTML Email
MIME
MS Storage Providers
Microsoft Graph
Misc
NTLM
OAuth1
OAuth2
OIDC
Office365
OneDrive
OpenSSL
Outlook
Outlook Calendar
Outlook Contact
PDF Signatures
PEM
PFX/P12
PKCS11
POP3
PRNG
REST
REST Misc
RSA
SCP
SCard
SFTP
SMTP
SSH
SSH Key
SSH Tunnel
ScMinidriver
SharePoint
SharePoint Online
Signing in the Cloud
Socket/SSL/TLS
Spider
Stream
Tar Archive
ULID/UUID
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl

 

 

 

(PowerBuilder) MIME Body vs. Sub-Parts

Explains the difference between sub-parts and body.

MIME documents (i.e. messages) can have a nested structure. The simplest MIME message contains a header followed by content (possibly encoded). The header is delimited from the content by two consecutive CRLF's.

A MIME message may be multipart. If so, then the Content-Type header field indicates "multipart" and the content the follows the header is itself a MIME message, which may also be multipart, etc. You can see how MIME messages effectively have a tree structure. The non-leaf nodes have Content-Types that are "multipart/" and the leaf nodes have non-multipart Content-Types.

The Chilkat MIME component/library uses two terms that need to be understood in order to effectively use the API. These are "body" and "sub-part". A multipart node has 1 or more sub-parts, but its body is empty. A leaf node (i.e. non-multipart node) has no sub-parts, but the body is (usually) non-empty.

This example creates a multipart MIME message and shows the results of getting the sub-parts and body of each node.

Chilkat ActiveX Downloads

ActiveX for 32-bit and 64-bit Windows

integer li_rc
oleobject loo_Mime
oleobject loo_Part1
integer li_Success
oleobject loo_Part2
integer n
oleobject loo_Part

// This example assumes the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.

loo_Mime = create oleobject
li_rc = loo_Mime.ConnectToNewObject("Chilkat_9_5_0.Mime")
if li_rc < 0 then
    destroy loo_Mime
    MessageBox("Error","Connecting to COM object failed")
    return
end if

// Create a multipart/mixed MIME message with two sub-parts.
// We'll use the Base64 encoding for the 2nd sub-part.
loo_Part1 = create oleobject
li_rc = loo_Part1.ConnectToNewObject("Chilkat_9_5_0.Mime")

li_Success = loo_Part1.SetBodyFromPlainText("This is part 1")

loo_Part2 = create oleobject
li_rc = loo_Part2.ConnectToNewObject("Chilkat_9_5_0.Mime")

li_Success = loo_Part2.SetBodyFromPlainText("This is part 2")
loo_Part2.Encoding = "base64"

li_Success = loo_Mime.NewMultipartMixed()
loo_Mime.UseMmDescription = 0
li_Success = loo_Mime.AppendPart(loo_Part1)
li_Success = loo_Mime.AppendPart(loo_Part2)

// Show the MIME message:
Write-Debug loo_Mime.GetMime()

// Here's the MIME:
// Content-Type: multipart/mixed;
// 	boundary="------------040605030407000302060008"
// 
// --------------040605030407000302060008
// Content-Type: text/plain;
// 	 charset="us-ascii"
// Content-Transfer-Encoding: 7bit
// 
// This is part 1
// --------------040605030407000302060008
// Content-Type: text/plain;
// 	 charset="us-ascii"
// Content-Transfer-Encoding: base64
// 
// VGhpcyBpcyBwYXJ0IDI=
// 
// --------------040605030407000302060008--

// If we examine the root node of the MIME message, 
// we see that it has 2 sub-parts and the body is empty (as expected)
n = loo_Mime.NumParts
Write-Debug "Num Parts = " + string(n)
Write-Debug "Body = " + loo_Mime.GetBodyDecoded()

// The GetEntireBody retrieves the entire content after
// the header.  (Perhaps GetEntireBody should've been named
// GetEntireContent to make it less confusing...)
Write-Debug "---- EntireBody:"
Write-Debug loo_Mime.GetEntireBody()
Write-Debug "********"

// Now examine the 2nd sub-part.  It has a body encoded
// using base64.  Get the contents of the body in both
// decoded and encoded forms:

// index 0 is the 1st part, index 1 is the 2nd part.
loo_Part = loo_Mime.GetPart(1)
Write-Debug "Decoded Body:"
Write-Debug loo_Part.GetBodyDecoded()
Write-Debug "Encoded Body:"
Write-Debug loo_Part.GetBodyEncoded()

destroy loo_Part


destroy loo_Mime
destroy loo_Part1
destroy loo_Part2

 

© 2000-2024 Chilkat Software, Inc. All Rights Reserved.