Noemax
Home
Products
Buy Now
Downloads
Support
Your Account
Contact Us Bookmark and Share
Products
WCF-Xtensions
FastInfoset.NET
Features
Size Comparisons
Performance Benchmarks
Pricing and Licensing
Try It
FAQ
DotNetCompression
Subscriptions
Free Utilities
Questions?
  Contact us for help on...
Features and capabilities
Pricing and licensing
Placing your order

Home » Products » FastInfoset.NET » FAQ

FastInfoset.NET FAQ

Download v4.1.0

Download

What is FastInfoset.NET?

FastInfoset.NET is a class library that provides an implementation of the Fast Infoset standard.

What is Fast Infoset?

Fast Infoset is a binary encoding of the XML Infoset that improves the efficiency of the text encoding by producing a more compact representation at a higher transaction rate.

Is Fast Infoset a standard?

Yes, it has been published as an ITU-T Recommendation (ITU-T Recommendation X.891 (2005)) and ISO/IEC International Standard (ISO/IEC 24824-1:2007).

Is FastInfoset.NET interoperable?

Yes, it has been tested for interoperability with the Java implementation by Sun Microsystems and with several other implementations available for a wide range of platforms.

Why should I prefer Fast Infoset as my XML encoding?

Compared to the text, .NET Binary and MTOM encodings, Fast Infoset has been shown to return the smallest document size and the best processing performance.

What are the practical benefits of using Fast Infoset?

Faster network communications, lower bandwidth consumption, higher XML performance, and lower storage requirements.

Better all around performance, faster network communications,

Higher performance, faster communications, reduced bandwidth consumption and storage requirements.

Improves application performance, speeds up communications, reduces bandwidth consumption and storage requirements.

Improves the performance of XML-related operations, reduces storage requirements and bandwidth consumption, speeds up network communications.

(check all short titles on the right).

Is it easy to use FastInfoset.NET?

Yes, it is. The API of FastInfoset.NET conforms to the XML API of .NET, so you can use the Fast Infoset encoding similarly to the way you use the text XML encoding.

Does FastInfoset.NET integrate into .NET?

Yes, FastInfoset.NET acts as an integral part of .NET by implementing the abstract XmlReader and XmlWriter of .NET. You can use Fast Infoset as if it was a system-provided XML encoding.

FULLY MANAGED

How do I switch from the text to the Fast Infoset encoding?

The XmlFastInfosetReader and XmlFastInfosetWriter of FastInfoset.NET are used similarly to the XmlTextReader and XmlTextWriter of .NET, so in most cases all you have to do is:

  • Add a reference to the Noemax.FastInfoset (or Noemax.FastInfoset.CF) assembly.
  • Add the Noemax.FastInfoset namespace.
  • Replace XmlTextReader with XmlFastInfosetReader.
  • Replace XmlTextWriter with XmlFastInfosetWriter.

How much smaller are Fast Infoset documents?

Take a look at the size comparisons that were made using a large number of documents collected from several publicly available sources on the Web.

Fast Infoset proved to be by far the most compact encoding, reducing the average document size to about 1/4th of the text encoding and showing that it can even reduce it down to 1/10th.

Are Fast Infoset documents always smaller than text?

Generally, yes. Except of some special cases such as <a></a> which is 7 bytes as text and 9 bytes as Fast Infoset, your documents will always be smaller when using Fast Infoset.

How much will Fast Infoset reduce the size of my documents?

You can use the freely available Fast Infoset Converter to find out. It will convert your text-encoded documents to Fast Infoset-encoded documents and report the conversion ratios.

If you also wish to convert your text-encoded documents to .NET Binary-encoded documents so that you can compare the conversion ratios of .NET Binary to those of Fast Infoset, use the MSBXML Converter.

Is Fast Infoset also efficient with binary data?

Yes, very much so. While the text encoding transforms binary data to Base64 or BinHex, Fast Infoset serializes binary data as it is. By avoiding these costly transformations, the speed of reading and writing binary data is increased and the amount of space taken up by it reduced.

Is Fast Infoset better than MTOM?

Yes, for three reasons:

  • Fast Infoset reduces the size of text messages irrespective of whether they contain binary data or not. MTOM does not reduce the size of text messages that do not contain binary data.
  • Fast Infoset reduces the size of text messages irrespective of the amount of binary data that they contain. MTOM actually increases the size of text messages containing less 2,350 bytes of binary data and gradually approaches the efficiency of Fast Infoset only above this threshold. You can read more here.
  • Fast Infoset returns considerably higher transactions per second that MTOM.

Is Fast Infoset better than .NET Binary?

Yes, because it is more efficient than .NET Binary both on document size and on processing performance, it conforms to an open international standard, and it provides interoperability with Java and other platforms.

Can I use Fast Infoset with my WCF-based Web services?

A ready-to-use, cross-platform interoperable Fast Infoset message encoding for WCF is available in WCF-Xtensions.

How can I view the contents of Fast Infoset documents?

Fast Infoset Viewer displays the contents of Fast Infoset-encoded files formatted as text XML.

How does Fast Infoset compare to compression?

In most cases compression reduces document size more than Fast Infoset but also consumes a lot of additional processing power. Compressing the encoded data introduces a substantial overhead irrespective of the encoding used, which can result in a noticeable degradation of performance, specially on the server side when it is under load.

Contrary to compression, Fast Infoset reduces document size and increases processing speed at the same time. You don't lose anything by using Fast Infoset, you only have gains.

Can I use both Fast Infoset and compression?

Yes, you can optionally use compression to further decrease the size of Fast Infoset-encoded documents. When you need the smallest possible document size, you can reduce the processing cost of compression by combining the Fast Infoset encoding with compression. Since Fast Infoset produces smaller documents than any of the system-provided encodings, the amount of processing required to compress Fast Infoset documents is the least possible.

If you wish to compress Fast Infoset, use DotNetCompression which offers compression classes that are more efficient than the corresponding system-provided classes of .NET.

Why is compressing Fast Infoset better than compressing text?

Compression is heavily processor intensive. The performance penalty it introduces is generally proportional to document size, so compressing the smaller Fast Infoset-encoded documents can be significantly faster than compressing the larger text-encoded documents.

Does Fast Infoset require a schema?

No, it does not require a schema.

How does Fast Infoset handle internationalization?

Fast Infoset encodes everything as UTF-8, so it has no internationalization issues.

Will FastInfoset.NET affect my application in any way?

No, it will not. FastInfoset.NET is an unobtrusive class library that operates transparently without affecting the operation of your application in any unexpected manner. It does not display anything, it does not access the registry or the file system, and it does not perform any communications, other than its own ,

Does FastInfoset.NET require activation?

Can FastInfoset.NET be easily deployed?

No it does not. FastInfoset.NET does not require activation or registration, nor does it employ any copy protection mechanism.

No, it will not. FastInfoset.NET consists only of fully managed .NET assemblies that operate unobtrusively without displaying anything, without accessing the registry or the file system, and without performing any communications.

It even doesn't use any copy protection mechanism so as to ensure that it doesn't affect the operation of your application in any way.

If it not time limited, it does not need any activation or registration.

, without blocking

To ensure the most unobtrusive operation, FastInfoset.NET does not display anything, does not access the file system or the registry, does not perform any communications, does not use a copy protection mechanism and does not inhibit any of its functionality for any reason. is not time limited

no intercation with the user, no special installation requirements other than including the assemblies with your software, fully managed, source code available for you to examine, code embedding for deployment flexibility

without retrieving or storing any data, without receiving or sending any data, without displaying or accepting any data.

Its operation is not inhibited for any reason

no special permissions are required for its operation, it does not require a key to be installed in order to run

it does not use any copy protection mechanism

displaying accessing the user interface or file system, introducing any unwanted functionality.

mechanism that affects the user interface, file system or communications of your software.

It has no user interface, it does not display any dialogs, it does not communicate with any other party, it does not use the registry, it does not access the file system, it does not perform any validation,

offers you additional functionality - minimal impact

You can either deploy its assemblies with your application. Minimal impact to existing code, non-intrusive

Only the trial edition is time limited and expires after a specific date.

This trial will expire on a random date, usually at least 30 days after downloading it.

Can FastInfoset.NET be used on the Compact Framework?

Yes, FastInfoset.NET includes assemblies for .NET Framework and .NET Compact Framework that provide the same functionality and the same API on both platforms.

On which versions of .NET can FastInfoset.NET be used?

FastInfoset.NET includes the following:

  • FastInfoset.NET 4.1.0 assemblies for .NET Framework 4.0, 4.0 Client Profile, 3.5, 3.5 Client Profile, 3.0, 2.0
  • FastInfoset.NET 4.1.0 assemblies for .NET Compact Framework 3.5, 2.0
  • FastInfoset.NET 4.1.0 assemblies for Silverlight 4, 3
  • DotNetCompression 2.1.0 assemblies for .NET Framework 4.0, 4.0 Client Profile, 3.5, 3.5 Client Profile, 3.0, 2.0
  • DotNetCompression 2.1.0 assemblies for .NET Compact Framework 3.5, 2.0
  • DotNetCompression 2.1.0 assemblies for Silverlight 4, 3

Can I try FastInfoset.NET?

Yes, you can download a trial from here.

Is the source code of FastInfoset.NET available?

Yes, its full source code is included in FastInfoset.NET Enterprise.

The Questions
What is FastInfoset.NET?
What is Fast Infoset?
Is Fast Infoset a standard?
Why should I prefer Fast Infoset as my XML encoding?
What are the practical benefits of using Fast Infoset?
Is FastInfoset.NET interoperable?
Does FastInfoset.NET integrate into .NET?
How do I switch from the text to the Fast Infoset encoding?
How much smaller are Fast Infoset documents?
Are Fast Infoset documents always smaller than text?
How much will Fast Infoset reduce the size of my documents?
Is Fast Infoset also efficient with binary data?
Is Fast Infoset better than MTOM?
Is Fast Infoset better than .NET Binary?
Can I use Fast Infoset with my WCF-based Web services?
How can I view the contents of Fast Infoset documents?
How does Fast Infoset compare to compression?
Can I use both Fast Infoset and compression?
Why is compressing Fast Infoset better than compressing text?
Does Fast Infoset require a schema?
How does Fast Infoset handle internationalization?
Does FastInfoset.NET affect user experience in any way?
Can FastInfoset.NET be used on the Compact Framework?
On which versions of .NET can FastInfoset.NET be used?
Can I try FastInfoset.NET?
Is the source code of FastInfoset.NET available?
Free FI Viewer
 » More  » Download
Free FI Converter
 » More  » Download
© 2010 Noemax Technologies  |  Terms of Use  |  Privacy Policy  |  Need Help?