Recent changes to Fastupload Home

WikiPage Fastupload Home modified by Link Qian

Link Qian — Sat, 05 Jan 2013 08:28:20 -0000

--- v16
+++ v17
@@ -32,9 +32,7 @@
 

 In the code snippet, after fastUploadParser.parseList() execute,  all data parts split by boundary are parsed an put into a list. {@link MultiPart} provides isFile() method determine a multipart data whether is a uploading file or normal input. For example, in a form HTML code is. ie.
- <input type="text" />, regarding 
- MultiPart object is not a file, to a no-file type
- MultiPart object, Fastupload limits to provides get content of  it as String
+ <input type="text" />, regarding MultiPart object is not a file, to a no-file type MultiPart object, Fastupload limits to provides get content of  it as String
   <input type="file" />, regarding
  MultiPart object is a file, to a file type
  MultiPart object, Fastupload provides toFile(String) method to write content of current multipart stream into a file. And getInputStream() to open a inputream for  current multipart stream. so APIs user can access it directly.
@@ -57,7 +55,7 @@
  }
   

- As you see, most code is like the first way, the code snippet change the parse way. It set a temporary repository for FileFactory object.
+As you see, most code is like the first way, the code snippet change the parse way. It set a temporary repository for FileFactory object.

  
  FileFactory fileFactory = FileFactory.getInstance();


WikiPage Fastupload Home modified by Link Qian
Link Qian — Fri, 04 Jan 2013 12:35:36 -0000

--- v15
+++ v16
@@ -2,7 +2,6 @@
 Fastupload is the fastest form-based file upload java programming component so far. The component is based on RFC1867, written for java and j2ee development zone. It uses high performance byte-search algorithm to parse the multipart/form-data request, afterward save data within boundaries into the file system or save data into buffer in memory. Also, it provides a through resolution to resolve the encoding issue for text file uploading in multipart/form-data request. The component has the ability to filter off data within boundaries by content-type or file extension name specified in the processing of parse multipart/form-data headers.

 ##Features##
-
 * support multiple boundaries
 * support parsing sub-boundary
 * supply resolution for uni-code text through
@@ -12,7 +11,6 @@
 * support struts2

 Refer to RFC1867, High level API for multipart/form-data ServletInputStream parsing. Sometime web site need to receives large size of uploading file, sometime web site need to receives a plenty of small size of uploading file in the high throughput. Fastupload provides two way to parse ServletInputStream and very simple APIs for variant requirements from high performance web site.
-

 ##Basic Usage##

@@ -33,18 +31,15 @@
 }
 

-
- In the code snippet, after fastUploadParser.parseList() execute,  all data parts split by boundary are parsed an put into a list. {@link MultiPart} provides isFile() method determine a multipart data whether is a uploading file or normal input. For example, in a form HTML code is. ie.
+In the code snippet, after fastUploadParser.parseList() execute,  all data parts split by boundary are parsed an put into a list. {@link MultiPart} provides isFile() method determine a multipart data whether is a uploading file or normal input. For example, in a form HTML code is. ie.
  <input type="text" />, regarding 
  MultiPart object is not a file, to a no-file type
  MultiPart object, Fastupload limits to provides get content of  it as String
   <input type="file" />, regarding
  MultiPart object is a file, to a file type
- MultiPart object, Fastupload provides
- toFile(String) method to write content of current multipart
- stream into a file. And getInputStream() to open a inputream for  current multipart stream. so APIs user can access it directly.
+ MultiPart object, Fastupload provides toFile(String) method to write content of current multipart stream into a file. And getInputStream() to open a inputream for  current multipart stream. so APIs user can access it directly.

- The second way is read 8K bytes from ServletInputStream to a  buffer, then parse multipart data within two boundaries, create disk file for  it and write content data in the temporary file when found a multipart data. read 8K bytes next until all byte of ServletInputStream is read and parsed. Finally return a list of {@link MultiPart}. This way only need 8K buffer extra. It's very useful when receive a large size of file. Here are simple code snippet to show this usage way.
+The second way is read 8K bytes from ServletInputStream to a  buffer, then parse multipart data within two boundaries, create disk file for  it and write content data in the temporary file when found a multipart data. read 8K bytes next until all byte of ServletInputStream is read and parsed. Finally return a list of {@link MultiPart}. This way only need 8K buffer extra. It's very useful when receive a large size of file. Here are simple code snippet to show this usage way.

  
  FileFactory fileFactory = FileFactory.getInstance();
@@ -62,8 +57,7 @@
  }
   

- As you see, most code is like the first way, the code snippet change the parse way. It set a temporary repository for FileFactory object
- 
+ As you see, most code is like the first way, the code snippet change the parse way. It set a temporary repository for FileFactory object.

  
  FileFactory fileFactory = FileFactory.getInstance();


WikiPage Fastupload Home modified by Link Qian
Link Qian — Fri, 04 Jan 2013 12:33:19 -0000

--- v14
+++ v15
@@ -34,8 +34,7 @@
 

- In the code snippet, after fastUploadParser.parseList() execute,  all data parts split by boundary are parsed an put into a list. {@link MultiPart} provides isFile() method determine a multipart data whether is a uploading file or normal input. For example, in a form HTML
-code is. ie.
+ In the code snippet, after fastUploadParser.parseList() execute,  all data parts split by boundary are parsed an put into a list. {@link MultiPart} provides isFile() method determine a multipart data whether is a uploading file or normal input. For example, in a form HTML code is. ie.
  <input type="text" />, regarding 
  MultiPart object is not a file, to a no-file type
  MultiPart object, Fastupload limits to provides get content of  it as String
@@ -96,6 +95,9 @@
 listener.progress();
  

+##Charset Encoding##
+Tobe done..
+
 ##Maven Coordinate##
 you can add the dependency to your POM.xml, such that Maven resolve dependency automatically.

WikiPage Fastupload Home modified by Link Qian

Link Qian — Fri, 04 Jan 2013 12:32:08 -0000

--- v13
+++ v14
@@ -11,62 +11,43 @@
 * faster performance, low memory occupy and high stability
 * support struts2

-Refer to RFC1867, High
-level API for multipart/form-data ServletInputStream parsing.
-Sometime web site need to receives large size of uploading file, sometime web
-site need to receives a plenty of small size of uploading file in the high
-throughput. Fastupload provides two way to parse
-ServletInputStream and very simple APIs for variant requirements
-from high performance web site.
+Refer to RFC1867, High level API for multipart/form-data ServletInputStream parsing. Sometime web site need to receives large size of uploading file, sometime web site need to receives a plenty of small size of uploading file in the high throughput. Fastupload provides two way to parse ServletInputStream and very simple APIs for variant requirements from high performance web site.

 ##Basic Usage##

-The first way is read all bytes from ServletInputStream into a
-buffer, then parse multipart data within two boundaries.
-FastUploadParser parse multipart/form-data input stream with the
-way in default. we recommend it. Here are a sample code snippet.
+The first way is read all bytes from ServletInputStream into a buffer, then parse multipart data within two boundaries.
+FastUploadParser parse multipart/form-data input stream with the way in default. We recommend it. Here are a sample code snippet.

-
-  FastUploadParser fastUploadParser = new FastUploadParser(request);
- List<MultiPart> list = fastUploadParser.parseList();
- for (MultiPart e: list){
+
+FastUploadParser fastUploadParser = new FastUploadParser(request);
+List<MultiPart> list = fastUploadParser.parseList();
+for (MultiPart e: list){
    if (e.isFile()){
-       System.out.format("input field name: %s, file name:%s%n", e.getFieldName(), e.getFileName());
+   System.out.format("input field name: %s, file name:%s%n", e.getFieldName(), e.getFileName());
            e.toFile( /file/ ) ;  //write data to a file where you want to place
    }
        else {
            System.out.format("input field name: %s, value:%s%n", e.getFieldName(), e.getString());
        }
-  }
+}
+

-
- In the code snippet, after fastUploadParser.parseList() execute,
- all data parts split by boundary are parsed an put into a list.
- {@link MultiPart} provides isFile() method determine a multipart
- data whether is a uploading file or normal input. For example, in a form HTML
- code is
- <input type="text" />, regarding
+ In the code snippet, after fastUploadParser.parseList() execute,  all data parts split by boundary are parsed an put into a list. {@link MultiPart} provides isFile() method determine a multipart data whether is a uploading file or normal input. For example, in a form HTML
+code is. ie.
+ 
<input type="text" />, regarding 
  MultiPart object is not a file, to a no-file type
- MultiPart object, Fastupload limits to provides get content of
- it as String
+ MultiPart object, Fastupload limits to provides get content of  it as String
   <input type="file" />, regarding
  MultiPart object is a file, to a file type
  MultiPart object, Fastupload provides
  toFile(String) method to write content of current multipart
- stream into a file. And getInputStream() to open a inputream for
- current multipart stream. so APIs user can access it directly.
+ stream into a file. And getInputStream() to open a inputream for  current multipart stream. so APIs user can access it directly.

- The second way is read 8K bytes from ServletInputStream to a
- buffer, then parse multipart data within two boundaries, create disk file for
- it and write content data in the temporary file when found a multipart data.
- read 8K bytes next until all byte of ServletInputStream is read
- and parsed. Finally return a list of {@link MultiPart}. This way only need 8K
- buffer extra. It's very useful when receive a large size of file. Here are
- simple code snippet to show this usage way.
+ The second way is read 8K bytes from ServletInputStream to a  buffer, then parse multipart data within two boundaries, create disk file for  it and write content data in the temporary file when found a multipart data. read 8K bytes next until all byte of ServletInputStream is read and parsed. Finally return a list of {@link MultiPart}. This way only need 8K buffer extra. It's very useful when receive a large size of file. Here are simple code snippet to show this usage way.

- 
+ 
  FileFactory fileFactory = FileFactory.getInstance();
  fileFactory.setRepository(System.getProperty("user.home")+"/fastupload");
  FastUploadParser fastUploadParser = new FastUploadParser(request, fileFactory);
@@ -79,11 +60,10 @@
    else {
        System.out.format("input field name: %s, value:%s%n", e.getFieldName(), e.getString());
    }
-  }
-  
+ }
+  

- As you see, most code is like the first way, the code snippet change the
- parse way. It set a temporary repository for FileFactory object
+ As you see, most code is like the first way, the code snippet change the parse way. It set a temporary repository for FileFactory object

  
@@ -92,17 +72,12 @@
  

- e.toFile( /target/ ) move the temporary file to the target place
- where you want because it isn't as same as first way that store multipart
- data in memory.
+ e.toFile( /target/ ) move the temporary file to the target place where you want because it isn't as same as first way that store multipart data in memory.

 ##Advanced APIs##
  {@link FileFactory} controls parse way, give some advanced features as well.
  FileFactory fileFactory = FileFactory.getInstance("UTF-8");
- create a {@link FileFactory} instance with specific charset name. Content of
- a multipart will convert with the charset name when find the content type is
- text. Another thing is it converts the file name of content header with the
- charset when find it. It is a key feature of Fastupload open-source project.
+ create a {@link FileFactory} instance with specific charset name. Content of a multipart will convert with the charset name when find the content type is text. Another thing is it converts the file name of content header with the charset when find it. It is a key feature of Fastupload open-source project.

   
  FileFactory fileFactory = FileFactory.getInstance("UTF-8");



WikiPage Fastupload Home modified by Link Qian
Link Qian — Fri, 04 Jan 2013 12:27:30 -0000
--- v12
+++ v13
@@ -115,7 +115,11 @@

  fileFactory.setThreshold(200000); limit parse content length of a part excludes headers, does not exceed the threshold. throw a runtime type of {@link ThresholdException} 
  
fileFactory.setMaxContentLength(2000000); limit parse a content length of current multipart request, does not exceed the value. throw a runtime type of {@link ThresholdException}
- 
+
+
Setup a {@link ProgressListener} to know  parsing progress 
+ProgressListener listener = new ProgressListener(fastUploadParser);
+listener.progress();
+ 

 ##Maven Coordinate##
 you can add the dependency to your POM.xml, such that Maven resolve dependency automatically.




WikiPage Fastupload Home modified by Link Qian
Link Qian — Sat, 29 Dec 2012 13:37:32 -0000
--- v11
+++ v12
@@ -11,80 +11,111 @@
 * faster performance, low memory occupy and high stability
 * support struts2

-##Basic API##
-The first usage is parsing data in memory. The usage has high performance. We recommend it.
-
-MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory();
-HttpMemoryUploadParser httpMemoryUploadParser = new HttpMemoryUploadParser(request, mpdf);
-List<MultiPartFile> list = httpMemoryUploadParser.parseList();
-for (MultiPartFile e : list) {
-    if (e.isFile()) {
-        e.toFile(System.getProperty("user.home" + "/" + e.getFileName());
-    } else {
-        if (e.getBytes() > 0)
-            System.out.println(new String(e.getContentBuffer()));
-    }
-}
+Refer to RFC1867, High
+level API for multipart/form-data ServletInputStream parsing.
+Sometime web site need to receives large size of uploading file, sometime web
+site need to receives a plenty of small size of uploading file in the high
+throughput. Fastupload provides two way to parse
+ServletInputStream and very simple APIs for variant requirements
+from high performance web site.

-The second usage is parsing data in buffer and save data into a disk file. The usage is lower performance than the first usage. But it has lower memory cost.
+##Basic Usage##
+ 
+The first way is read all bytes from ServletInputStream into a
+buffer, then parse multipart data within two boundaries.
+FastUploadParser parse multipart/form-data input stream with the
+way in default. we recommend it. Here are a sample code snippet.
+ 

-DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"));
-HttpFileUploadParser parser = new HttpFileUploadParser(req, dff);
-List<MultiPartFile> files = parser.parse();
+  FastUploadParser fastUploadParser = new FastUploadParser(request);
+ List<MultiPart> list = fastUploadParser.parseList();
+ for (MultiPart e: list){
+   if (e.isFile()){
+       System.out.format("input field name: %s, file name:%s%n", e.getFieldName(), e.getFileName());
+           e.toFile( /file/ ) ;  //write data to a file where you want to place
+   }
+       else {
+           System.out.format("input field name: %s, value:%s%n", e.getFieldName(), e.getString());
+       }
+  }

-##Advanced API##
-optional  *DiskFileFactory* and *MultiPartDataFactory* provide a several features. specify a charset,

-DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8");
-or
-MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory("utf-8");
+ In the code snippet, after fastUploadParser.parseList() execute,
+ all data parts split by boundary are parsed an put into a list.
+ {@link MultiPart} provides isFile() method determine a multipart
+ data whether is a uploading file or normal input. For example, in a form HTML
+ code is
+ <input type="text" />, regarding
+ MultiPart object is not a file, to a no-file type
+ MultiPart object, Fastupload limits to provides get content of
+ it as String
+  <input type="file" />, regarding
+ MultiPart object is a file, to a file type
+ MultiPart object, Fastupload provides
+ toFile(String) method to write content of current multipart
+ stream into a file. And getInputStream() to open a inputream for
+ current multipart stream. so APIs user can access it directly.
+ 
+ The second way is read 8K bytes from ServletInputStream to a
+ buffer, then parse multipart data within two boundaries, create disk file for
+ it and write content data in the temporary file when found a multipart data.
+ read 8K bytes next until all byte of ServletInputStream is read
+ and parsed. Finally return a list of {@link MultiPart}. This way only need 8K
+ buffer extra. It's very useful when receive a large size of file. Here are
+ simple code snippet to show this usage way.
+ 
+ 
+ FileFactory fileFactory = FileFactory.getInstance();
+ fileFactory.setRepository(System.getProperty("user.home")+"/fastupload");
+ FastUploadParser fastUploadParser = new FastUploadParser(request, fileFactory);
+ List<MultiPart> list = fastUploadParser.parseList();
+ for (MultiPart e: list){
+   if (e.isFile()){
+       System.out.format("input field name: %s, file name:%s%n", e.getFieldName(), e.getFileName());
+       e.toFile( /target/ ) ;  //move temporary file to where you want to place
+   }
+   else {
+       System.out.format("input field name: %s, value:%s%n", e.getFieldName(), e.getString());
+   }
+  }
+  

+ As you see, most code is like the first way, the code snippet change the
+ parse way. It set a temporary repository for FileFactory object

-*HttpFileUploadParser* converts file name with utf-8 charset, also
-convert the content with utf-8 charset if found the form-based uploading file
-is text format. In memory appropriate, *MultiPartFile* object export all bytes to user. so it doesn't convert data CharSet. 

-
-DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8", 0x20000);
-or 
-
-MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory("utf-8", 0x20000);
-
-the code indicates the max size is 0x20000 per file.
-
-dff.setParseThreshold(0x100000);
-
-The code indicates the max content-length of whole requesting data.
-
-Fastupload provides an advanced mechanism that filters uploading files. It
-does not like others form-based uploading component or framework filter
-feature. It filters off a boundary if found the boundary's content header
-doesn't match the rules.
-
-dff.setAllowedExtensions(".jpg, .png");
-
-
-comma splitting. the code indicates *HttpFileUploadParser* accept two
-types file. JPG and PNG.
+ 
+ FileFactory fileFactory = FileFactory.getInstance();
+ fileFactory.setRepository(System.getProperty("user.home")+"/fastupload");
+ 

-dff.setAllowedTypes("image/jpg");
-
-
-the code indicates *HttpFileUploadParser* accept the image/jpg
-content type.
-when *HttpFileUploadParser* filters off some boundaries, it put headers into a exceptional collection as digest information. user can get it with the API.
-
-Set<ContentHeaderMap> exceptionals = dff.getExceptionals()
-
-
-At the point, you may know *MemoryMultiPartDataFactory* has the same methods. indeed, it has.
-mpdf.setParseThreshold(0x100000);
-mpdf.setAllowedExtensions(".jpg, .png");
-mpdf.setAllowedTypes("image/jpg");
-Set<ContentHeaderMap> exceptionals = mpdf.getExceptionals()
-
+ 
+ e.toFile( /target/ ) move the temporary file to the target place
+ where you want because it isn't as same as first way that store multipart
+ data in memory.
+ 
+##Advanced APIs##
+ {@link FileFactory} controls parse way, give some advanced features as well.
+ FileFactory fileFactory = FileFactory.getInstance("UTF-8");
+ create a {@link FileFactory} instance with specific charset name. Content of
+ a multipart will convert with the charset name when find the content type is
+ text. Another thing is it converts the file name of content header with the
+ charset when find it. It is a key feature of Fastupload open-source project.
+ 
+  
+ FileFactory fileFactory = FileFactory.getInstance("UTF-8");
+ fileFactory.setAllowedTypes("image/jpeg");
+ fileFactory.setAllowedExtensions(".jpg, .png");
+ 
 FastUploadParser provides content type and file
+ name filter function. Parser ignore a multipart content when found its
+ content header does not match AllowedTypes or extension name of
+ filename entity does not match AllowedExtensions.
+  
+ fileFactory.setThreshold(200000); limit parse content length of a part excludes headers, does not exceed the threshold. throw a runtime type of {@link ThresholdException} 
+ 
fileFactory.setMaxContentLength(2000000); limit parse a content length of current multipart request, does not exceed the value. throw a runtime type of {@link ThresholdException}
+ 

 ##Maven Coordinate##
 you can add the dependency to your POM.xml, such that Maven resolve dependency automatically.
@@ -92,5 +123,5 @@
 <dependency>
     <groupId>net.sf.fastupload</groupId>
     <artifactId>fastupload-core</artifactId>
-    <version>0.4.7</version>
+    <version>0.5.3</version>
 </dependency>




WikiPage Fastupload Home modified by Link Qian
Link Qian — Fri, 30 Nov 2012 13:45:04 -0000
--- v10
+++ v11
@@ -13,7 +13,7 @@
 
 ##Basic API##
 The first usage is parsing data in memory. The usage has high performance. We recommend it.
-+
 MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory();
 HttpMemoryUploadParser httpMemoryUploadParser = new HttpMemoryUploadParser(request, mpdf);
 List<MultiPartFile> list = httpMemoryUploadParser.parseList();
@@ -25,37 +25,37 @@
             System.out.println(new String(e.getContentBuffer()));
     }
 }
-
+
 
 The second usage is parsing data in buffer and save data into a disk file. The usage is lower performance than the first usage. But it has lower memory cost.
-+
 DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"));
 HttpFileUploadParser parser = new HttpFileUploadParser(req, dff);
 List<MultiPartFile> files = parser.parse();
-
+
 
 ##Advanced API##
 optional  *DiskFileFactory* and *MultiPartDataFactory* provide a several features. specify a charset,
--DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8");
or+
+DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8");
+or
 MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory("utf-8");
-
+
  
 *HttpFileUploadParser* converts file name with utf-8 charset, also
 convert the content with utf-8 charset if found the form-based uploading file
 is text format. In memory appropriate, *MultiPartFile* object export all bytes to user. so it doesn't convert data CharSet. 
  
--DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8", 0x20000);
+
+DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8", 0x20000);
 or 
-+
 MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory("utf-8", 0x20000);
-
+
 the code indicates the max size is 0x20000 per file.
 
- dff.setParseThreshold(0x100000);
-
+
 The code indicates the max content-length of whole requesting data.
 
 Fastupload provides an advanced mechanism that filters uploading files. It
@@ -63,37 +63,34 @@
 feature. It filters off a boundary if found the boundary's content header
 doesn't match the rules.
 
- dff.setAllowedExtensions(".jpg, .png");
-
+
 
 comma splitting. the code indicates *HttpFileUploadParser* accept two
 types file. JPG and PNG.
  
- dff.setAllowedTypes("image/jpg");
-
+
 
 the code indicates *HttpFileUploadParser* accept the image/jpg
 content type.
 when *HttpFileUploadParser* filters off some boundaries, it put headers into a exceptional collection as digest information. user can get it with the API.
-+
 Set<ContentHeaderMap> exceptionals = dff.getExceptionals()
-
+
 
 At the point, you may know *MemoryMultiPartDataFactory* has the same methods. indeed, it has.
-mpdf.setParseThreshold(0x100000);
+mpdf.setParseThreshold(0x100000);
 mpdf.setAllowedExtensions(".jpg, .png");
 mpdf.setAllowedTypes("image/jpg");
 Set<ContentHeaderMap> exceptionals = mpdf.getExceptionals()
-
+
 
 ##Maven Coordinate##
 you can add the dependency to your POM.xml, such that Maven resolve dependency automatically.
-+
 <dependency>
     <groupId>net.sf.fastupload</groupId>
     <artifactId>fastupload-core</artifactId>
     <version>0.4.7</version>
 </dependency>
-



WikiPage Fastupload Home modified by Link Qian
Link Qian — Thu, 29 Nov 2012 02:13:29 -0000
--- v9
+++ v10
@@ -11,7 +11,7 @@
 * faster performance, low memory occupy and high stability
 * support struts2
 
-##basic API##
+##Basic API##
 The first usage is parsing data in memory. The usage has high performance. We recommend it.
  MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory();
@@ -87,3 +87,13 @@
 mpdf.setAllowedTypes("image/jpg");
 Set<ContentHeaderMap> exceptionals = mpdf.getExceptionals()
 
+
+##Maven Coordinate##
+you can add the dependency to your POM.xml, such that Maven resolve dependency automatically.
++<dependency>
+    <groupId>net.sf.fastupload</groupId>
+    <artifactId>fastupload-core</artifactId>
+    <version>0.4.7</version>
+</dependency>
+



WikiPage Fastupload Home modified by Link Qian
Link Qian — Tue, 13 Nov 2012 08:56:33 -0000
--- v8
+++ v9
@@ -11,7 +11,7 @@
 * faster performance, low memory occupy and high stability
 * support struts2
 
-##API basic usage##
+##basic API##
 The first usage is parsing data in memory. The usage has high performance. We recommend it.
  MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory();



WikiPage Fastupload Home modified by Link Qian
Link Qian — Tue, 13 Nov 2012 08:50:10 -0000
--- v7
+++ v8
@@ -37,7 +37,7 @@
 ##Advanced API##
 optional  *DiskFileFactory* and *MultiPartDataFactory* provide a several features. specify a charset,
 -DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8");
 or +DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8");
or MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory("utf-8");
 
  
@@ -46,7 +46,9 @@
 is text format. In memory appropriate, *MultiPartFile* object export all bytes to user. so it doesn't convert data CharSet. 
  
 -DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8", 0x20000);
 or +DiskFileFactory dff = new DiskFileFactory(System.getProperty("user.home"), "utf-8", 0x20000);
+or 
+ MultiPartDataFactory mpdf = new MemoryMultiPartDataFactory("utf-8", 0x20000);
 
 the code indicates the max size is 0x20000 per file.