File: mime_part.xml

package info (click to toggle)
virtuoso-opensource 7.2.5.1%2Bdfsg1-0.3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 285,240 kB
  • sloc: ansic: 641,220; sql: 490,413; xml: 269,570; java: 83,893; javascript: 79,900; cpp: 36,927; sh: 31,653; cs: 25,702; php: 12,690; yacc: 10,227; lex: 7,601; makefile: 7,129; jsp: 4,523; awk: 1,697; perl: 1,013; ruby: 1,003; python: 326
file content (120 lines) | stat: -rw-r--r-- 4,785 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
 -  
 -  This file is part of the OpenLink Software Virtuoso Open-Source (VOS)
 -  project.
 -  
 -  Copyright (C) 1998-2018 OpenLink Software
 -  
 -  This project is free software; you can redistribute it and/or modify it
 -  under the terms of the GNU General Public License as published by the
 -  Free Software Foundation; only version 2 of the License, dated June 1991.
 -  
 -  This program is distributed in the hope that it will be useful, but
 -  WITHOUT ANY WARRANTY; without even the implied warranty of
 -  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
 -  General Public License for more details.
 -  
 -  You should have received a copy of the GNU General Public License along
 -  with this program; if not, write to the Free Software Foundation, Inc.,
 -  51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
 -  
 -  
-->
<refentry id="fn_mime_part">
  <refmeta>
    <refentrytitle>mime_part</refentrytitle>
    <refmiscinfo>mail</refmiscinfo>
  </refmeta>
  <refnamediv>
    <refname>mime_part</refname>
    <refpurpose>used to compose a MIME message body part.</refpurpose>
  </refnamediv>
  <refsynopsisdiv>
    <funcsynopsis id="fsyn_mime_part">
      <funcprototype id="fproto_mime_part">
        <funcdef>any <function>mime_part</function></funcdef>
        <paramdef>in <parameter>content_type</parameter> varchar</paramdef>
        <paramdef>in <parameter>content_disposition</parameter> varchar</paramdef>
        <paramdef>in <parameter>transfer_encoding</parameter> varchar</paramdef>
        <paramdef>in <parameter>data</parameter> varchar</paramdef>
      </funcprototype>
    </funcsynopsis>
  </refsynopsisdiv>
  <refsect1 id="desc_mime_part">
    <title>Description</title>
    <para>This function is used to make a MIME part that can be used with the 
<function>mime_body()</function> function.</para>
  </refsect1>
  <refsect1 id="params_mime_part"><title>Parameters</title>
    <refsect2><title>content_type</title>
      <para>This parameter is used to specify the media type and subtype of data 
      in the body of a message and to fully specify the native representation of 
      such data.  This header embodies much of the power of MIME.  The IETF can 
      add new official content types. Additionally, private content-type values can 
      be defined by anyone. Such private content types have values of 
      "x-something" or "X-something", where "something" can take on 
      any value.</para></refsect2>
    <refsect2><title>content_disposition</title>
      <para>This parameter provides information about how to present a 
      body part.  When a body part is to be treated as an attached file, the 
      Content-Disposition header should include a file name parameter.</para></refsect2>
    <refsect2><title>transfer_encoding</title>
      <para>The encoding method to use, such as base64.</para></refsect2>
    <refsect2><title>data</title>
      <para>The content of the message.</para></refsect2>
  </refsect1>
  <refsect1 id="ret_mime_part"><title>Return Types</title>
    <para>The function returns a MIME part for use with the <function>mime_body()</function> function.</para>
  </refsect1>
<!--
  <refsect1 id="errors_mime_part">
    <title>Errors</title>
    <para>This function can generate the following errors:</para>
    <errorcode></errorcode>
  </refsect1>
-->
  <refsect1 id="examples_mime_part">
    <title>Examples</title>
    <example id="ex_mime_part"><title>Creating a MIME message body</title>
      <para>This example will show the output in ISQL of producing a two part MIME message
      using the mime_body() and mime_part() functions.</para>
      <screen>
SQL&gt; select MIME_BODY (vector (MIME_PART (null,null,null,&#39;this is a first&#39;),
MIME_PART (null,null,&#39;base64&#39;,&#39;this is a second&#39;)));
callret
VARCHAR
_______________________________________________________________________________

Date: Tue, 25 Jun 2002 11:13:05 GMT
Content-Type: multipart/mixed; boundary=&quot;----43c7f8b88e14a87dc3f2d840db93c731&quot;
Mime-Version: 1.0
X-Mailer: Virtuoso

This is a multi-part message in MIME format.

------43c7f8b88e14a87dc3f2d840db93c731
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

this is a first
------43c7f8b88e14a87dc3f2d840db93c731
Content-Type: text/plain
Content-Transfer-Encoding: base64

dGhpcyBpcyBhIHNlY29uZA==
------43c7f8b88e14a87dc3f2d840db93c731--


1 Rows. -- 21 msec.

</screen>
    </example>
  </refsect1>
  <refsect1 id="seealso_mime_part">
    <title>See Also</title>
      <para><link linkend="fn_mime_part"><function>mime_part()</function></link></para>
      <para><link linkend="fn_mime_body"><function>mime_body()</function></link></para>
  </refsect1>
</refentry>