\n+\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml\n------------------------------------------------------------------------------\nsvn:eol-style = native\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml\n------------------------------------------------------------------------------\nsvn:keywords = Id\nAdded: stdcxx/site/forrest/src/documentation/content/xdocs/download.xml\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/download.xml?rev=618441&view=auto\n==============================================================================\n--- stdcxx/site/forrest/src/documentation/content/xdocs/download.xml (added)\n+++ stdcxx/site/forrest/src/documentation/content/xdocs/download.xml Mon Feb 4 13:20:33 2008\n@@ -0,0 +1,58 @@\n+\n+\n+\n+\n+ \n+ Downloading the Apache C++ Standard Library\n+ \n+
\n+ \n+ Viewing the Latest Files Online\n+
The latest versions of stdcxx source files can be viewed or individually downloaded by directly accessing the stdcxx file repository in ASF Subversion by pointing your Web browser to the following URLs:
4.2.0 (pre-release branch) http://svn.apache.org/repos/asf/stdcxx/branches/4.2.0 (closed to development)
\n+
4.1.3 (final release branch) http://svn.apache.org/repos/asf/stdcxx/branches/4.1.3 (closed to development)
\n+
web site http://svn.apache.org/repos/asf/stdcxx/site
\n+
\n+\n+ \n+ \n+ Checking Out Files Using the Subversion Client\n+\n+
\n+\n+ To check out stdcxx files using anonymous Subversion access, read the instructions here.
\n+To check out the latest development version of entire stdcxx repository (i.e., its trunk) into the stdcxx/ directory in current working directory, enter the following command at the command prompt:
\n+$ svn co http://svn.apache.org/repos/asf/stdcxx/trunk stdcxx
\n+To check out stdcxx files for write access (committers only), read the instructions here.
\n+The Subversion command is the same as above, the only thing different is the HTTPS protocol instead of ordinary HTTP:
\n+$ svn co https://svn.apache.org/repos/asf/stdcxx/trunk stdcxx
\n+
\n+ \n+ \n+ Downloading stdcxx Snapshots\n+
See the table below for available snapshots. ","In the table, the version column indicates the library version. ","The date column indicates the date the version was released. ","The file column contains one or more links to the tarball or zip file available for download. ","The size column is the size of the file in kilobytes. ","The md5 sum column indicates the MD5 sum for the file and is also a link pointing to the MD5 sum file that can be downloaded. ","The comment column contains links to the community vote approving the release, and to the Incubator PMC approval of the release.
\n+ \n+ \n+ Downloading stdcxx Releases\n+
See the table below for available releases. ","In the table, the version column indicates the library version. ","The date column indicates the date the version was released. ","The file column contains one or more links to the tarball or zip file available for download. ","The size column is the size of the file in kilobytes. ","The md5 sum column indicates the MD5 sum for the file and is also a link pointing to the MD5 sum file that can be downloaded. ","The fixes column contains 3 numbers: the first, Bug Fixes, indicating the number of bugs affecting previous versions that were resolved in the release, the second, Improvements, indicating the number of improvements made in this release with respect to previous releases, and the third, New Features, indicating the number of entire new features implemented in this release. ","Each non-zero number is a link to the list of the corresponding issues in the bug-tracking database. ","The comment column contains links to the community vote a\npproving the release, and to the Incubator PMC approval of the release.
\n+ \n+ What is the Apache C++ Standard Library?\n+
\n+ The Apache C++ Standard Library project (code name stdcxx, pronounced \"standard C++ library\", not S-T-D-C-X-X) is a collection of algorithms, containers, iterators, and other fundamental components of every piece of software, implemented as C++ classes, templates, and functions essential for writing C++ programs.","\n+
\n+
The goal of the Apache C++ Standard Library is to provide a free implementation of the ISO/IEC 14882 international standard for C++ that enables source code portability and consistent behavior of programs across all major hardware implementations, operating systems, and compilers, open source and commercial alike. ","An additional goal is to achieve maximum implementation efficiency on each platform by taking advantage of platform-specific high-performance facilities and features which are often unique to the type of hardware, the operating system or the compiler.","\n+
\n+
As the starting point for future efforts, in summer 2005 Rogue Wave Software has contributed its commercial implementation of the C++ Standard Library to the Apache stdcxx project, a proven code base that has been shipping for over a decade and is among the most widely used cross-platform implementations of the library.","\n+
\n+
The key features of the stdcxx project at the time of submission include:\n+
\n+
\n+
Full conformance to the C++ standard
\n+
Complete implementation of the localization library independent of the underlying operating system, including a large set of locale definition files, character set description files, and utility programs to process these files and generate locale databases
\n+
User control over strict or permissive conformance checking
\n+
Thread-safe implementation of strings, iostreams, and locales
\n+
Reference counted basic_string implementation using atomic locking with the ability to switch to a non-reference counted implementation
\n+
Excellent runtime performance
\n+
Optimized for fast compiles and extremely small executable file sizes
\n+
Portable to and fully tested on a large set of operating systems, including AIX, HP-UX, Linux, Solaris, Windows, etc.
\n+
Portable to most leading commercial as well as open source compilers
\n+
Debugging facilities such as safe iterators, precondition and postcondition checking, and the ability to generate stack traces
\n+
Fully documented configuration and build infrastructure
\n+
Thorough, well-maintained documentation
\n+
Ten years of deployment in the world's most critical enterprise systems
\n+
\n+ \n+ \n+ Objectives\n+
The long-term objectives of the project include:
\n+
\n+
Standards Conformance. ","Continue to closely track the C++ Standard, as well as any other relevant standards.
\n+
Portablity. ","Continue to provide support for a broad set of platforms (C++ compilers, operating systems, and hardware architectures)
\n+
Quality of Implementation. ","Maintain the current high quality of implementation, which has come to be expected of all Apache projects. ","This ranges from high runtime efficiency to high space efficiency, to high portability of data (in areas such as localization and internationalization which are typically not specified by the C++ or C standards), to facilitating the portability of program source code.
\n+
\n+ \n+ \n+ Project News\n+
\n+
12/14/2007 STDCXX graduates from the Incubator and becomes a Top Level Project.
\n+
11/29/2007 STDCXX community adds a new committer, Travis Vitek.
\n+
10/29/2007 With the approval of the Incubator PMC, STDCXX 4.2.0 was released.
\n+
10/16/2007 Proposal to graduate STDCXX to a Top Level Project passes the Incubator PMC vote.
\n+
9/5/2007 STDCXX community adds two new committers, Eric (Brad) Lemings and Mark Brown.
\n+
10/11/2006 STDCXX community adds a new committer, Andrew Black.
\n+
8/26/2007 Started tracking project metrics at www.ohloh.net under Apache C++ Standard Library.
\n+
6/1/2007 Started tracking site visitation at Google Analytics under stdcxx. ","Send an email from your Google Mail account to dev to request access to the account.
\n+
3/26/2007 Tim Triemstra joins the PPMC.
\n+
2/13/2007 Andrew Black and Farid Zaripov join the PPMC.
\n+
10/11/2006 STDCXX community adds a new committer, Andrew Black.
\n+
8/10/2006 STDCXX community adds a new committer, Farid Zaripov.
\n+
1/30/2006 With the approval of the Incubator PMC, STDCXX 4.1.3 was released.
\n+
1/13/2006 STDCXX community adds a new committer, Anton Pevtsov.
\n+
11/25/2005 Windows configuration and build infarstructure committed to Subversion (stdcxx-5).
\n+
9/16/2005 The first snapshot of stdcxx 4.1.2 has been published.
\n+
9/5/2005 The test suite driver committed to Subversion (stdcxx-3).
\n+
9/1/2005 A proposal to publish the first stdcxx snapshot on the stdcxx Web site has passed the community vote.
\n+
8/28/2005 The process of downloading stdcxx files documented on the Download page. (","See stdcxx-17).
\n+
8/01/2005 The process of reporting bugs in the stdcxx bug tracking database documented and published on the Bugs page. (","See stdcxx-9.)
\n+
7/19/2005 stdcxx project page committed to Subversion. ","The project status page committed to Subversion.
\n+
7/18/2005 stdcxx sources and documentation committed Subversion.
\n+
5/19/2005 stdcxx project accepted for incubation.
\n+
5/13/2005 stdcxx project proposal submitted to the Incubator mailing list.
\n+
\n+ \n+ \n+ Platforms\n+
A key stdcxx objective is to facilitate the portability of C++ programs to as many platforms (hardware architectures, operating systems, and compilers) as practical. ","It is envisaged that the set of platforms will evolve and grow as the project attracts contributors.
\n+
\n+\n+The project sources initially committed to the Subversion repository\n+(revision 219596)\n+are based on Rogue Wave C++ Standard Library version 4.1.0. ","The list\n+of platforms to which this version of the project was ported (but\n+which is expected to grow as the stdcxx project evolves) is:
\n+ \n+ \n+ Project Status\n+
Stdcxx status reports to the ASF Board of Directors are stored in the status/ subdirectory of the site.
\n+ \n+ \n+ Users\n+
\n+Stdcxx Users are Developers with read-only access, i.e., without Commit Access to the stdcxx Codebase who are using the project.","\n+
\n+
\n+The mailing list appropriate for discussions of using the stdcxx project is user@stdcxx.apache.org. ","This is an archived, moderated mailing list open to all subscribers.","\n+You may subscribe by sending a blank email to user-subscribe@stdcxx.apache.org. ","To obtain additional information about this list send a blank email to user-info@stdcxx.apache.org.","\n+
\n+\n+ \n+ \n+ Contributors\n+
Stdcxx Contributors are Developers without commit (or write) access to the stdcxx codebase who directly or otherwise make improvements to the project codebase, including its Web pages. ","This includes but is not limited to individuals who respond to questions on the project's mailing lists, review and provide helpful feedback on patches or commits, submit, provide helpful comments on, or triage bug reports, or contribute useful patches of their own. ","Interested contributors may be voted to become Committers after a period of valuable activity.
\n+
Because Contributors have read but not write access to stdcxx code repository, they can check stdcxx out and make changes to their local copy of stdcxx files but they cannot check them back in. ","To get their changes committed, they must follow the process for Submitting Patches.
\n+
The stdcxx community welcomes new contributors. ","If you are interested in getting involved, the first thing to do after reading the project Web pages is to subscribe to the dev mailing list and skimming the archives. ","If you're looking for ideas for where your help might be needed, browse the bug database or simply ask on the maling list.","\n+Committers\n+
\n+ \n+ \n+ Committers\n+
Stdcxx Committers are Developers with commit (or write) access to the stdcxx codebase. ","For safe changes on trunk all stdcxx committers follow the Commit-Then-Review policy (CTR for short). ","For potentially unsafe changes or any changes to branches all stdcxx committers follow the Review-Then-Commit policy (RTC for short). ","Whether a change is safe or not is a judgment call that should be made after careful testing of the change on at least two different platforms with two different compilers. ","The list of current committers in alphabetical order is below:
\n+
Committers in italics do not yet have a signed Contributor License Agreement on file. ","This indicates a transient state after a committer has been voted in but their CLA hasn't been received or processed by the foundation.","\n+\n+An up-to-date list of all Apache committers (or committers-to-be) is being maintained by Jim Jagielski on this page.","\n+\n+The mailing list used by stdcxx committers for discussions of the maintenance, development, and porting of the stdcxx project is dev@stdcxx.apache.org. ","This is an archived, moderated mailing list open to all subscribers. ","You may subscribe by sending a blank email to dev-subscribe@stdcxx.apache.org.","\n+
\n+ \n+ \n+ PMC\n+
The stdcxx Project Management Committee (PMC) is a group of volunteers responsible for the formal oversight of the stdcxx podling, its management, and for interfacing with the Apache Board of Directors. ","The members of the stdcxx PMC are:
\n+ \n+
The PMC mailing list is private@stdcxx.apache.org. ","This is a moderated, by-invitation-only mailing list closed to the public. ","Invited individuals can subscribe by sending a blank email to private-subscribe@stdcxx.apache.org.","\n+\n+An example of a topic that might be appropriate for this list is a discussion of the merits of a proposed committer.","\n+
\n+ \n+ \n+ Communication\n+\n+
\n+ Communication about the project and all decisions take place on the project's mailing lists. ","There are a number good reasons why communicating on mailing lists is preferable to other ways of communicating, including private email or instant messaging. ","Some of the important ones include:
\n+
\n+
Unlike communicating in private, mailing lists make it possible for all list subscribers to benefit from the discussion, and provides an opportunity for those who wouldn't be invited to the private discussion to offer their own feedback on the subject.
\n+
Unlike Instant Messaging, mailing list make it possible for interested parties to participate asynchronously, regardless of which time zone they are located in.
\n+
Unlike private communications, mailing list discussions are archived for future reference, with the archives being easily searchable by anyone interested. ","Mailing list archives are important not just so that new contributors can learn from past decisions but they are an indispensable tool also for long-time committers when we forget why certain things were done a certain way.
\n+
It is the preferred mode of communicating for all Apache projects. ","See the Communication section of How the ASF works.
\n+
\n+
\n+If you choose to contact one of the project committers in private expect to be directed to the mailing lists.","\n+
\n+ \n+ \n+ Mailing Lists\n+
The following table provides a summary of information about stdcxx mailing lists along with a number of interfaces to their archives.","\n+ All lists are moderated. ","Only subscribers may post. ","Subscription to private is by invitation of the PMC only.","\n+ With one exception, the activity of each list is monitored and can be viewed along with other interesting information on this page maintained by Ken Coar.","\n+
\n+ \n+ \n+ References\n+\n+\n+
A number of excellent design and programming books describe the C++ Standard Library in an approachable way. ","In addition, besides the required Class Reference, this implementation of the library also includes an extensive User Guide complete with tutorials and example programs. ","That being said, the ultimate reference to the C++ Standard Library is, of course, the C++ Standard itself (and to a smaller extent, also the C Standard). ","An electronic copy of the most recent version of the C++ and C standards can be obtained from the ANSI eStandards store.
\n+
\n+
INCITS/ISO/IEC 14882-2003 Programming Languages -- C++
\n+
INCITS/ISO/IEC 9899-1999 Programming Languages -- C
\n+
The C++ Standard Library: A Tutorial and Reference by Nicolai M. Josuttis
\n+
Generic Programming and the STL: Using and Extending the C++ Standard Template Library by Matthew H. Austern
\n+
Stl Tutorial & Reference Guide: C++ Programming With the Standard Template Library by David R. Musser and Atul Saini
\n+
The C++ Standard Template Library by P.J. Plauger, Alexander A. Stepanov, Meng Lee, and David R. Musser
\n+
Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library by Scott Meyers
\n+
Standard C++ IOStreams and Locales: Advanced Programmer's Guide and Reference by Angelika Langer, Klaus Kreft
\n+
\n+ \n+
\n+\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/index.xml\n------------------------------------------------------------------------------\nsvn:eol-style = native\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/index.xml\n------------------------------------------------------------------------------\nsvn:keywords = Id\nAdded: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/site.xml?rev=618441&view=auto\n==============================================================================\n--- stdcxx/site/forrest/src/documentation/content/xdocs/site.xml (added)\n+++ stdcxx/site/forrest/src/documentation/content/xdocs/site.xml Mon Feb 4 13:20:33 2008\n@@ -0,0 +1,62 @@\n+\n+\n+\n+\n+\n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+ \n+\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml\n------------------------------------------------------------------------------\nsvn:eol-style = native\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml\n------------------------------------------------------------------------------\nsvn:keywords = Id\nAdded: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml?rev=618441&view=auto\n==============================================================================\n--- stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml (added)\n+++ stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml Mon Feb 4 13:20:33 2008\n@@ -0,0 +1,39 @@\n+\n+\n+\n+\n+\n+ \n+ \n+\n+\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml\n------------------------------------------------------------------------------\nsvn:eol-style = native\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml\n------------------------------------------------------------------------------\nsvn:keywords = Id\nAdded: stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db?rev=618441&view=auto\n==============================================================================\nBinary file - no diff available.","\nPropchange: stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db\n------------------------------------------------------------------------------\nsvn:mime-type = application/octet-stream\nAdded: stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png?rev=618441&view=auto\n==============================================================================\nBinary file - no diff available.","\nPropchange: stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png\n------------------------------------------------------------------------------\nsvn:mime-type = application/octet-stream\nAdded: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat?rev=618441&view=auto\n==============================================================================\n--- stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat (added)\n+++ stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat Mon Feb 4 13:20:33 2008\n@@ -0,0 +1,29 @@\n+\n+\n+\n+\n+\n+\n+ \n+\n+ \n+\nPropchange: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat\n------------------------------------------------------------------------------\nsvn:eol-style = native\nPropchange: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat\n------------------------------------------------------------------------------\nsvn:keywords = Id"],"string":"[\n \"Author: sebor\\nDate: Mon Feb 4 13:20:33 2008\\nNew Revision: 618441\\nURL: http://svn.apache.org/viewvc?rev=618441&view=rev\\nLog:\\n2008-02-04 Gavin \\nSTDCXX-686\\n* forrest/forrest.properties: Added sources for the initial (though\\nincomplete) pass at a Forrest-based site redesign/reimplementation.\",\n \"\\n* forrest/src/documentation: Same.\",\n \"\\n* forrest/src/documentation/sitemap.xmap: Same.\",\n \"\\n* forrest/src/documentation/skinconf.xml: Same.\",\n \"\\n* forrest/src/documentation/content: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/bugs.xml: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/site.xml: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/images: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/images/project.svg: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/images/project-logo.gif: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/images/group.svg: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/images/icon.png: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/images/group-logo.gif: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/images/usemap.gif: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/download.xml: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/index.xml: Same.\",\n \"\\n* forrest/src/documentation/content/xdocs/tabs.xml: Same.\",\n \"\\n* forrest/src/documentation/content/locationmap.xml: Same.\",\n \"\\n* forrest/src/documentation/resources: Same.\",\n \"\\n* forrest/src/documentation/resources/schema: Same.\",\n \"\\n* forrest/src/documentation/resources/schema/catalog.xcat: Same.\",\n \"\\n* forrest/src/documentation/resources/themes: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/panels: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/panels/pelt-html.panel.xml: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/panels/pelt-css.panel.xml: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/html: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/html/siteinfo-credits.ft: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/html/content-main.ft: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/html/nav-main-sub.ft: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/html/nav-section-round-bottom.ft: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/html/search-input.ft: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/html/branding-logo.ft: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/page.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/spacer.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/singlepage.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/label.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/search-right.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/sidebar_bg.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/tab-right.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/current.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/printer.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/header-background.png: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/chapter.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/xmldoc.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/chapter_white.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/tl-off.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/tl-on.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/tr-off.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/search-left.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/tab-left.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/header-background-grad.png: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/header_white_line.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/pdfdoc.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/tr-on.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/header-background.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/doc.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/chapter_open.gif: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/images/instruction_arrow.png: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/css: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/css/pelt.print.css: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/css/leather-dev.css: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/css/pelt.screen.css: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt/css/pelt.basic.css: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/common: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/common/css: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/common/css/branding-theme-profiler.ft: Same.\",\n \"\\n* forrest/src/documentation/resources/themes/pelt.fv: Same.\",\n \"\\n* forrest/src/documentation/resources/images: Same.\",\n \"\\n* forrest/src/documentation/resources/images/stdcxx.png: Same.\",\n \"\\n* forrest/src/documentation/resources/images/Thumbs.db: Same.\",\n \"\\n* forrest/src/documentation/README.txt: Same.\",\n \"\\n* forrest/src/documentation/classes: Same.\",\n \"\\n* forrest/src/documentation/classes/CatalogManager.properties: Same.\",\n \"\\n* forrest/forrest.properties.xml: Same.\",\n \"\\nAdded:\\nstdcxx/site/forrest/\\nstdcxx/site/forrest/forrest.properties (with props)\\nstdcxx/site/forrest/forrest.properties.xml (with props)\\nstdcxx/site/forrest/src/\\nstdcxx/site/forrest/src/documentation/\\nstdcxx/site/forrest/src/documentation/README.txt (with props)\\nstdcxx/site/forrest/src/documentation/classes/\\nstdcxx/site/forrest/src/documentation/classes/CatalogManager.properties (with props)\\nstdcxx/site/forrest/src/documentation/content/\\nstdcxx/site/forrest/src/documentation/content/locationmap.xml (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/\\nstdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/download.xml (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/images/\\nstdcxx/site/forrest/src/documentation/content/xdocs/images/group-logo.gif (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/images/group.svg (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/images/icon.png (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/images/project-logo.gif (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/images/project.svg (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/images/usemap.gif (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/index.xml (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/site.xml (with props)\\nstdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml (with props)\\nstdcxx/site/forrest/src/documentation/resources/\\nstdcxx/site/forrest/src/documentation/resources/images/\\nstdcxx/site/forrest/src/documentation/resources/images/Thumbs.db (with props)\\nstdcxx/site/forrest/src/documentation/resources/images/stdcxx.png (with props)\\nstdcxx/site/forrest/src/documentation/resources/schema/\\nstdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/\\nstdcxx/site/forrest/src/documentation/resources/themes/common/\\nstdcxx/site/forrest/src/documentation/resources/themes/common/css/\\nstdcxx/site/forrest/src/documentation/resources/themes/common/css/branding-theme-profiler.ft (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt.fv (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/css/\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/css/leather-dev.css (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/css/pelt.basic.css (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/css/pelt.print.css (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/css/pelt.screen.css (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/html/\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/html/branding-logo.ft (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/html/content-main.ft (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/html/nav-main-sub.ft (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/html/nav-section-round-bottom.ft (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/html/search-input.ft (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/html/siteinfo-credits.ft (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/chapter.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/chapter_open.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/chapter_white.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/current.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/doc.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header-background-grad.png (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header-background.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header-background.png (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/header_white_line.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/instruction_arrow.png (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/label.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/page.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/pdfdoc.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/printer.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/search-left.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/search-right.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/sidebar_bg.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/singlepage.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/spacer.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tab-left.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tab-right.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tl-off.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tl-on.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tr-off.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/tr-on.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/images/xmldoc.gif (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/panels/\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/panels/pelt-css.panel.xml (with props)\\nstdcxx/site/forrest/src/documentation/resources/themes/pelt/panels/pelt-html.panel.xml (with props)\\nstdcxx/site/forrest/src/documentation/sitemap.xmap (with props)\\nstdcxx/site/forrest/src/documentation/skinconf.xml (with props)\\nAdded: stdcxx/site/forrest/forrest.properties\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/forrest.properties?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/forrest.properties (added)\\n+++ stdcxx/site/forrest/forrest.properties Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,25 @@\\n+# Licensed to the Apache Software Foundation (ASF) under one or more\\n+# contributor license agreements. \",\n \"See the NOTICE file distributed with\\n+# this work for additional information regarding copyright ownership.\",\n \"\\n+# The ASF licenses this file to You under the Apache License, Version 2.0\\n+# (the \\\"License\\\"); you may not use this file except in compliance with\\n+# the License. \",\n \"You may obtain a copy of the License at\\n+#\\n+# http://www.apache.org/licenses/LICENSE-2.0\\n+#\\n+# Unless required by applicable law or agreed to in writing, software\\n+# distributed under the License is distributed on an \\\"AS IS\\\" BASIS,\\n+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\",\n \"\\n+# See the License for the specific language governing permissions and\\n+# limitations under the License.\",\n \"\\n+\\n+##############\\n+# This is a minimal properties file.\",\n \"\\n+# These are defaults, un-comment them only if you need to change them.\",\n \"\\n+# See the full set of default properties in a 'forrest seed-sample' site.\",\n \"\\n+# Copy properties from there as needed.\",\n \"\\n+##############\\n+project.required.plugins=org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.inputModule\\n+# codename: Dispatcher\\n+# Add the following plugins to project.required.plugins:\\n+#org.apache.forrest.plugin.internal.dispatcher,org.apache.forrest.themes.core,org.apache.forrest.plugin.output.inputModule\\nPropchange: stdcxx/site/forrest/forrest.properties\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/forrest.properties\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/forrest.properties.xml\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/forrest.properties.xml?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/forrest.properties.xml (added)\\n+++ stdcxx/site/forrest/forrest.properties.xml Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,26 @@\\n+\\n+\\n+\\n+\\n+ \\n+ \\n+\\nPropchange: stdcxx/site/forrest/forrest.properties.xml\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/forrest.properties.xml\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/README.txt\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/README.txt?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/README.txt (added)\\n+++ stdcxx/site/forrest/src/documentation/README.txt Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,7 @@\\n+This is the base documentation directory.\",\n \"\\n+\\n+skinconf.xml # This file customizes Forrest for your project. \",\n \"In it, you\\n+ # tell forrest the project name, logo, copyright info, etc\\n+\\n+sitemap.xmap # Optional. \",\n \"This sitemap is consulted before all core sitemaps.\",\n \"\\n+ # See http://forrest.apache.org/docs/project-sitemap.html\\nPropchange: stdcxx/site/forrest/src/documentation/README.txt\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/README.txt\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties (added)\\n+++ stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,62 @@\\n+# Licensed to the Apache Software Foundation (ASF) under one or more\\n+# contributor license agreements. \",\n \"See the NOTICE file distributed with\\n+# this work for additional information regarding copyright ownership.\",\n \"\\n+# The ASF licenses this file to You under the Apache License, Version 2.0\\n+# (the \\\"License\\\"); you may not use this file except in compliance with\\n+# the License. \",\n \"You may obtain a copy of the License at\\n+#\\n+# http://www.apache.org/licenses/LICENSE-2.0\\n+#\\n+# Unless required by applicable law or agreed to in writing, software\\n+# distributed under the License is distributed on an \\\"AS IS\\\" BASIS,\\n+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\",\n \"\\n+# See the License for the specific language governing permissions and\\n+# limitations under the License.\",\n \"\\n+\\n+#=======================================================================\\n+# CatalogManager.properties for Catalog Entity Resolver.\",\n \"\\n+#\\n+# This is the default properties file for your project.\",\n \"\\n+# This facilitates local configuration of application-specific catalogs.\",\n \"\\n+# If you have defined any local catalogs, then they will be loaded\\n+# before Forrest's core catalogs.\",\n \"\\n+#\\n+# See the Apache Forrest documentation:\\n+# http://forrest.apache.org/docs/your-project.html\\n+# http://forrest.apache.org/docs/validation.html\\n+\\n+# verbosity:\\n+# The level of messages for status/debug (messages go to standard output).\",\n \"\\n+# The setting here is for your own local catalogs.\",\n \"\\n+# The verbosity of Forrest's core catalogs is controlled via\\n+# main/webapp/WEB-INF/cocoon.xconf\\n+#\\n+# The following messages are provided ...\\n+# 0 = none\\n+# 1 = ? (... \",\n \"not sure yet)\\n+# 2 = 1+, Loading catalog, Resolved public, Resolved system\\n+# 3 = 2+, Catalog does not exist, resolvePublic, resolveSystem\\n+# 10 = 3+, List all catalog entries when loading a catalog\\n+# (Cocoon also logs the \\\"Resolved public\\\" messages.)\",\n \"\\n+verbosity=1\\n+\\n+# catalogs ... list of additional catalogs to load\\n+# (Note that Apache Forrest will automatically load its own default catalog\\n+# from main/webapp/resources/schema/catalog.xcat)\\n+# Use either full pathnames or relative pathnames.\",\n \"\\n+# pathname separator is always semi-colon (;) regardless of operating system\\n+# directory separator is always slash (/) regardless of operating system\\n+# The project catalog is expected to be at ../resources/schema/catalog.xcat\\n+#catalogs=../resources/schema/catalog.xcat\\n+# FIXME: Workaround FOR-548 \\\"project DTD catalogs are not included\\n+# when running as a servlet WAR\\\".\",\n \"\\n+# Same catalog, different path\\n+catalogs=../resources/schema/catalog.xcat;../../project/src/documentation/resources/schema/catalog.xcat\\n+\\n+# relative-catalogs\\n+# If false, relative catalog URIs are made absolute with respect to the\\n+# base URI of the CatalogManager.properties file. \",\n \"This setting only\\n+# applies to catalog URIs obtained from the catalogs property in the\\n+# CatalogManager.properties file\\n+# Example: relative-catalogs=[yes|no]\\n+relative-catalogs=no\\nPropchange: stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/classes/CatalogManager.properties\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/content/locationmap.xml\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/locationmap.xml?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/content/locationmap.xml (added)\\n+++ stdcxx/site/forrest/src/documentation/content/locationmap.xml Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,47 @@\\n+\\n+\\n+\\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+\\n+ \\n+\\nPropchange: stdcxx/site/forrest/src/documentation/content/locationmap.xml\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/content/locationmap.xml\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml (added)\\n+++ stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,109 @@\\n+\\n+\\n+\\n+\\n+ \\n+ Bugs in Apache C++ Standard Library\\n+ \\n+
\\n+ \\n+ What Is a Bug\\n+\\n+\\n+
Wikipedia, the free online encyclopedia, defines a bug as follows:
\\n+A computer bug is an error, flaw, mistake, failure, or fault in a computer program that prevents it from working correctly or produces an incorrect result.\",\n \"\\n+
\\n+ \\n+\\n+ \\n+ Before Reporting a Bug\\n+ \\n+
If you have discovered a bug in stdcxx and would like to report it to the development team, please be sure to first check the project's issue tracking database to see whether the bug has already been reported and, if so, what its status is. \",\n \"If the bug has not been reported yet, follow the instructions on Reporting a Bug below. \",\n \"Otherwise, feel free to add a comment to the issue in the issue tracking database if you think it might help resolve it more quickly (for example, if you have a smaller or better test case).
\\n+
If you think but aren't 100% sure that you have discovered a bug in the source code of the project, please consult a reliable reference on the subject first and confirm that the behavior you are experiencing is, in fact, a bug and not a feature. \",\n \"If even after reading the relevant references you are still not sure, you should send an email to stdcxx-user@incubator.apache.org and ask. \",\n \"If the problem is indeed a bug, go back to step 1.
\\n+
If you have a suggestion for a change or an addition to the interface or the behavior of this implementation of the library that you would like to propose to the development team (e.g., an enhancement request), please make sure that the change is not in conflict with the requirements of the C++ Standard. \",\n \"You can get an electronic copy of the C++ Standard from the ANSI eStandards store. \",\n \"If your request is not in conflict with any requirements of the C++ standard, open a request for Improvement or New Feature to the issue tracking database (see the stdcxx issue tracking database documentation for the available issue types).
\\n+ \\n+ \\n+\\n+ \\n+ Saved Bug Reports\\n+
The table below contains links to a number of saved bug tracking database queries along with their summary results. \",\n \"The version column indicates the version and contains a link to a query that pulls up all issues of any type scheduled to be fixed in that version. \",\n \"The Resolved column indicates the number of issues of any type resolved (but not closed) in that version. \",\n \"The Closed column indicates the number of issues of any type closed in that version. \",\n \"The Bugs column indicates the number of issues of type Bug resolved or closed in that version. \",\n \"The Improvements column indicates the number of issues of type Improvement resolved or closed in that version. \",\n \"The New Features column indicates the number of issues of type New Feature resolved or closed in that version. \",\n \"The Regressions column indicates the number of issues of any type both introduced and resolved or closed in that version. \",\n \"The Pending column indicates the number of issues of any type schedule for that\\nversion that haven't yet been resolved or closed.
\\n+
The value in each cell in the table is either a number (for released versions), or TBD (for To Be Determined) for a version that is in active development, or N/A (for Not Available) for a future version for which there is no data yet.
\\n+ \\n+\\n+ \\n+ External Bugs Affecting the Apache C++ Standard Library\\n+
We track bugs in compilers, operating systems, and other software external to the Apache C++ Standard Library that affect the correct behavior or performance of the library or programs that use it in the issue tracking database along with other bugs. \",\n \"These bug reports are often quite useful when porting the project to new versions of the software. \",\n \"See the table below for filters with predefined searches for bugs relevant to specific compilers, operating systems, and/or common hardware architectures.
\\n+ \\n+\\n+ \\n+ Reporting a Bug\\n+
To report a new bug in this implementation of the C++ Standard Library or the accompanying utilities or example programs, or a problem in any other part of the stdcxx project such as its documentation or Web pages, open an issue in the project's issue tracking database and choose Bug for the Issue Type. \",\n \"Make sure you assign the bug the appropriate component. \",\n \"For example, if the bug has to do with the formatting of numbers using iostreams, the likely components will be 22. \",\n \"Localization, or 27. \",\n \"Input/Output.
\\n+
When reporting a bug in this implementation of the library, be sure to demonstrate the problem in a small (50 lines of code or less) C++ program that does not depend on any third party libraries (system libraries excluded). \",\n \"In addition to the program, make sure to include the details of the environment in which the bug can be reproduces, including the full command line used to compile, link, and run the program, and the output of each of the mentioned stages, specifically any compiler or linker diagnostics, and, if applicable, the output of the program itself. \",\n \"When the problem manisfests itself in the form of an abnormal program termination (e.g., crash), it helps to include the full stack trace at the crash site. \",\n \"To demonstrate incorrect behavior, use the assert() macro to assert any postconditions. \",\n \"Refer to existing bug reports (such as STDCXX-2) for examples. \",\n \"By following this advice you will increase the chances that the bug will be resolved quickly.
\\n+ \\n+\\n+ \\n+ Requesting an Enhancement\\n+
The process for requesting enhancements and new features in stdcxx is essentially the same as the process for Reporting a bug except that instead choosing Bug as the Issue Type you will choose either Improvevement when requesting an enhancement to an existing feature, or New Feature when requesting an entire new feature.
\\n+ \\n+\\n+ \\n+ Submitting Patches\\n+
Committers who follow the Review-Then-Commit policy, and non-committer Contributors without commit (write) access to the stdcxx source repository must submit patches for review and approval before they can be committed by someone with commit access. \",\n \"If you would like to submit a patch for a bug that you or someone else reported, you can do so in two ways:
\\n+ \\n+
Post the patch to the project development mailing list, stdcxx-dev@incubator.apache.org. \",\n \"The subject line of the email should start with the string [PATCH], followed by a brief description of the patch and the issue number from the issue tracking database if one exists. \",\n \"An easy way to come up with a good description for the patch subject line is to simply copy the Summary from the bug report. \",\n \"Be sure to also include a reference to the bug (preferably in the form of a link to the original bug report).
\\n+
Add the patch to the bug report in the form of a comment (when the patch is just a few lines of text), or in the form of an attachment to the issue. \",\n \"This approach is preferable to sending the patch to the mailing list when the patch is large or when the patch sent to the project development mailing list gets mangled or stripped by the list management software.
\\n+ \\n+
If you would like to submit a patch for a bug that doesn't have a corresponding issue in the issue tracking database, you should start by creating a small test case to demonstrate the problem first. \",\n \"It's not uncommon for this exercise to expose an error in the usage of the library rather than in the library implementation itself. \",\n \"Once you've isolated the bug to a small test case and filed an issue in the issue tracking database you can update the issue with the proposed patch.
\\n+
If you would like to submit a patch with an improvement to the project (such as an optimization tweak), either create an enhancement request in the issue tracking database and attach the patch to it or, for small changes, post the patch along with a detailed description as well as before and after data showing the improvement to the project development mailing list, stdcxx-dev@incubator.apache.org.
\\n+
Patches for documentation or project web pages should follow the same process as above, except that a test case isn't necessary in most situations. \",\n \"A possible exception is a patch for code example listed in the Class Reference.
\\n+
In all cases, make sure your patch follows the expected Patch Format described below.
\\n+ \\n+\\n+ \\n+ Patch Format\\n+
Every patch should address at most one issue from the issue tracking database. \",\n \"Separate issues should be addressed in separate patches. \",\n \"An issue that discusses more than one bug or one enhancement should either be first split up into multiple issues, or into multiple subtasks, before submitting a patch for each.
\\n+
In order to make them easy to review and revert, if necessary (in case they cause regressions not dicovered during review), patches should be as small as possible. \",\n \"Changes should be limited to the bare minimum necessary to address the issue. \",\n \"Gratuitous edits such code reformatting or renanaming of variables should be avoided. \",\n \"Such changes should be made separately and independently of any functional changes to the code.
\\n+
Every patch should include the following information:
\\n+ \\n+
Detailed description of the change. \",\n \"It should be obvious from reading the description alone (i.e., without reading the Change Log or looking at the source code) what the change does and why. \",\n \"See this post for an example of such a description.
\\n+
Changes that might have an impact on the efficiency of the changed component should be accompanied by a small program exercising the component, either by timings showing the performance difference between the original and the changed code in user and system times (for example, using the POSIX time command), or by sizes of the original and the code for changes affetcting the space efficiency of code.
\\n+\\n+
Change Log entry. \",\n \"The format of Change Log entries follows the established GNU Change Log convention. \",\n \"Emacs users can take advantage of the add-change-log-entry command. \",\n \"See the Change Log section of the Emacs manual.\",\n \"\\n+\\n+Each Change Log entry starts with a submission date followed by the name and email address of the submitter, all on the same line. \",\n \"Separated by a blank line is a reference to the issue key representing the corresponding issue in the issue tracking database (if applicable). \",\n \"The rest of the entry consists of a bullet list of changed files and the names and descriptions of the symbols affected by the change in each file. \",\n \"A maximum line length of 78 characters should be observed. \",\n \"For examples of stdcxx Change Log entries view the logs of some stdcxx source files, such as time_put.cpp, or wcodecvt.cpp.\",\n \"\\n+\\n+The format of the issue key is especially important in order for the the issue tracking database to be able to update the issue in the issue tracking database with information about the change. \",\n \"The issue key format is STDCXX-NNN where the NNN part is the issue number (for example, STDCXX-2).\",\n \"\\n+
\\n+
The diff between the most recent versions of the file being modified and the modified version. \",\n \"The diff should be in a format suitable for processing by the standard POSIX patch utility, or in the Unified format produced by the Subversion svn diff command by default as well as by the GNU diff utility and understood by GNU patch. \",\n \"When creating patches on Windows it is important to keep in mind that the newline sequences (carriage-return followed by line-feed, or <CR><LF>) may not be recognized by traditional UNIX implementations of the patch utility (as is the case on Solaris). \",\n \"For portability, it is best to strip the carriage-returns from the patch before posting it. \",\n \"The standard tr utility can be used to do that.\",\n \"\\n+\\n+New Files\\n+
\\n+ \\n+ \\n+\\n+ \\n+ New Files\\n+\\n+
New files included as part of a patch (such as new tests) should be submitted in the original format and not as the output of the patch utility since patch cannot create new files. \",\n \"Multiple files can be submitted individually or as a gzipped tarball. \",\n \"Be aware of the size limit imposed on posts to the mailing list. \",\n \"In general, it is better to avoid posting very large files and instead attach them to an issue in the issue tracking database.
\\n+
\\n+Each new source or header file should contain the license header described in the ASF Source Header and Copyright Notice Policy.\",\n \"\\n+
\\n+ \\n+\\n+
\\n+\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/bugs.xml\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/content/xdocs/download.xml\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/download.xml?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/content/xdocs/download.xml (added)\\n+++ stdcxx/site/forrest/src/documentation/content/xdocs/download.xml Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,58 @@\\n+\\n+\\n+\\n+\\n+ \\n+ Downloading the Apache C++ Standard Library\\n+ \\n+
\\n+ \\n+ Viewing the Latest Files Online\\n+
The latest versions of stdcxx source files can be viewed or individually downloaded by directly accessing the stdcxx file repository in ASF Subversion by pointing your Web browser to the following URLs:
4.2.0 (pre-release branch) http://svn.apache.org/repos/asf/stdcxx/branches/4.2.0 (closed to development)
\\n+
4.1.3 (final release branch) http://svn.apache.org/repos/asf/stdcxx/branches/4.1.3 (closed to development)
\\n+
web site http://svn.apache.org/repos/asf/stdcxx/site
\\n+
\\n+\\n+ \\n+ \\n+ Checking Out Files Using the Subversion Client\\n+\\n+
\\n+\\n+ To check out stdcxx files using anonymous Subversion access, read the instructions here.
\\n+To check out the latest development version of entire stdcxx repository (i.e., its trunk) into the stdcxx/ directory in current working directory, enter the following command at the command prompt:
\\n+$ svn co http://svn.apache.org/repos/asf/stdcxx/trunk stdcxx
\\n+To check out stdcxx files for write access (committers only), read the instructions here.
\\n+The Subversion command is the same as above, the only thing different is the HTTPS protocol instead of ordinary HTTP:
\\n+$ svn co https://svn.apache.org/repos/asf/stdcxx/trunk stdcxx
\\n+
\\n+ \\n+ \\n+ Downloading stdcxx Snapshots\\n+
See the table below for available snapshots. \",\n \"In the table, the version column indicates the library version. \",\n \"The date column indicates the date the version was released. \",\n \"The file column contains one or more links to the tarball or zip file available for download. \",\n \"The size column is the size of the file in kilobytes. \",\n \"The md5 sum column indicates the MD5 sum for the file and is also a link pointing to the MD5 sum file that can be downloaded. \",\n \"The comment column contains links to the community vote approving the release, and to the Incubator PMC approval of the release.
\\n+ \\n+ \\n+ Downloading stdcxx Releases\\n+
See the table below for available releases. \",\n \"In the table, the version column indicates the library version. \",\n \"The date column indicates the date the version was released. \",\n \"The file column contains one or more links to the tarball or zip file available for download. \",\n \"The size column is the size of the file in kilobytes. \",\n \"The md5 sum column indicates the MD5 sum for the file and is also a link pointing to the MD5 sum file that can be downloaded. \",\n \"The fixes column contains 3 numbers: the first, Bug Fixes, indicating the number of bugs affecting previous versions that were resolved in the release, the second, Improvements, indicating the number of improvements made in this release with respect to previous releases, and the third, New Features, indicating the number of entire new features implemented in this release. \",\n \"Each non-zero number is a link to the list of the corresponding issues in the bug-tracking database. \",\n \"The comment column contains links to the community vote a\\npproving the release, and to the Incubator PMC approval of the release.
\\n+ \\n+ What is the Apache C++ Standard Library?\\n+
\\n+ The Apache C++ Standard Library project (code name stdcxx, pronounced \\\"standard C++ library\\\", not S-T-D-C-X-X) is a collection of algorithms, containers, iterators, and other fundamental components of every piece of software, implemented as C++ classes, templates, and functions essential for writing C++ programs.\",\n \"\\n+
\\n+
The goal of the Apache C++ Standard Library is to provide a free implementation of the ISO/IEC 14882 international standard for C++ that enables source code portability and consistent behavior of programs across all major hardware implementations, operating systems, and compilers, open source and commercial alike. \",\n \"An additional goal is to achieve maximum implementation efficiency on each platform by taking advantage of platform-specific high-performance facilities and features which are often unique to the type of hardware, the operating system or the compiler.\",\n \"\\n+
\\n+
As the starting point for future efforts, in summer 2005 Rogue Wave Software has contributed its commercial implementation of the C++ Standard Library to the Apache stdcxx project, a proven code base that has been shipping for over a decade and is among the most widely used cross-platform implementations of the library.\",\n \"\\n+
\\n+
The key features of the stdcxx project at the time of submission include:\\n+
\\n+
\\n+
Full conformance to the C++ standard
\\n+
Complete implementation of the localization library independent of the underlying operating system, including a large set of locale definition files, character set description files, and utility programs to process these files and generate locale databases
\\n+
User control over strict or permissive conformance checking
\\n+
Thread-safe implementation of strings, iostreams, and locales
\\n+
Reference counted basic_string implementation using atomic locking with the ability to switch to a non-reference counted implementation
\\n+
Excellent runtime performance
\\n+
Optimized for fast compiles and extremely small executable file sizes
\\n+
Portable to and fully tested on a large set of operating systems, including AIX, HP-UX, Linux, Solaris, Windows, etc.
\\n+
Portable to most leading commercial as well as open source compilers
\\n+
Debugging facilities such as safe iterators, precondition and postcondition checking, and the ability to generate stack traces
\\n+
Fully documented configuration and build infrastructure
\\n+
Thorough, well-maintained documentation
\\n+
Ten years of deployment in the world's most critical enterprise systems
\\n+
\\n+ \\n+ \\n+ Objectives\\n+
The long-term objectives of the project include:
\\n+
\\n+
Standards Conformance. \",\n \"Continue to closely track the C++ Standard, as well as any other relevant standards.
\\n+
Portablity. \",\n \"Continue to provide support for a broad set of platforms (C++ compilers, operating systems, and hardware architectures)
\\n+
Quality of Implementation. \",\n \"Maintain the current high quality of implementation, which has come to be expected of all Apache projects. \",\n \"This ranges from high runtime efficiency to high space efficiency, to high portability of data (in areas such as localization and internationalization which are typically not specified by the C++ or C standards), to facilitating the portability of program source code.
\\n+
\\n+ \\n+ \\n+ Project News\\n+
\\n+
12/14/2007 STDCXX graduates from the Incubator and becomes a Top Level Project.
\\n+
11/29/2007 STDCXX community adds a new committer, Travis Vitek.
\\n+
10/29/2007 With the approval of the Incubator PMC, STDCXX 4.2.0 was released.
\\n+
10/16/2007 Proposal to graduate STDCXX to a Top Level Project passes the Incubator PMC vote.
\\n+
9/5/2007 STDCXX community adds two new committers, Eric (Brad) Lemings and Mark Brown.
\\n+
10/11/2006 STDCXX community adds a new committer, Andrew Black.
\\n+
8/26/2007 Started tracking project metrics at www.ohloh.net under Apache C++ Standard Library.
\\n+
6/1/2007 Started tracking site visitation at Google Analytics under stdcxx. \",\n \"Send an email from your Google Mail account to dev to request access to the account.
\\n+
3/26/2007 Tim Triemstra joins the PPMC.
\\n+
2/13/2007 Andrew Black and Farid Zaripov join the PPMC.
\\n+
10/11/2006 STDCXX community adds a new committer, Andrew Black.
\\n+
8/10/2006 STDCXX community adds a new committer, Farid Zaripov.
\\n+
1/30/2006 With the approval of the Incubator PMC, STDCXX 4.1.3 was released.
\\n+
1/13/2006 STDCXX community adds a new committer, Anton Pevtsov.
\\n+
11/25/2005 Windows configuration and build infarstructure committed to Subversion (stdcxx-5).
\\n+
9/16/2005 The first snapshot of stdcxx 4.1.2 has been published.
\\n+
9/5/2005 The test suite driver committed to Subversion (stdcxx-3).
\\n+
9/1/2005 A proposal to publish the first stdcxx snapshot on the stdcxx Web site has passed the community vote.
\\n+
8/28/2005 The process of downloading stdcxx files documented on the Download page. (\",\n \"See stdcxx-17).
\\n+
8/01/2005 The process of reporting bugs in the stdcxx bug tracking database documented and published on the Bugs page. (\",\n \"See stdcxx-9.)
\\n+
7/19/2005 stdcxx project page committed to Subversion. \",\n \"The project status page committed to Subversion.
\\n+
7/18/2005 stdcxx sources and documentation committed Subversion.
\\n+
5/19/2005 stdcxx project accepted for incubation.
\\n+
5/13/2005 stdcxx project proposal submitted to the Incubator mailing list.
\\n+
\\n+ \\n+ \\n+ Platforms\\n+
A key stdcxx objective is to facilitate the portability of C++ programs to as many platforms (hardware architectures, operating systems, and compilers) as practical. \",\n \"It is envisaged that the set of platforms will evolve and grow as the project attracts contributors.
\\n+
\\n+\\n+The project sources initially committed to the Subversion repository\\n+(revision 219596)\\n+are based on Rogue Wave C++ Standard Library version 4.1.0. \",\n \"The list\\n+of platforms to which this version of the project was ported (but\\n+which is expected to grow as the stdcxx project evolves) is:
\\n+ \\n+ \\n+ Project Status\\n+
Stdcxx status reports to the ASF Board of Directors are stored in the status/ subdirectory of the site.
\\n+ \\n+ \\n+ Users\\n+
\\n+Stdcxx Users are Developers with read-only access, i.e., without Commit Access to the stdcxx Codebase who are using the project.\",\n \"\\n+
\\n+
\\n+The mailing list appropriate for discussions of using the stdcxx project is user@stdcxx.apache.org. \",\n \"This is an archived, moderated mailing list open to all subscribers.\",\n \"\\n+You may subscribe by sending a blank email to user-subscribe@stdcxx.apache.org. \",\n \"To obtain additional information about this list send a blank email to user-info@stdcxx.apache.org.\",\n \"\\n+
\\n+\\n+ \\n+ \\n+ Contributors\\n+
Stdcxx Contributors are Developers without commit (or write) access to the stdcxx codebase who directly or otherwise make improvements to the project codebase, including its Web pages. \",\n \"This includes but is not limited to individuals who respond to questions on the project's mailing lists, review and provide helpful feedback on patches or commits, submit, provide helpful comments on, or triage bug reports, or contribute useful patches of their own. \",\n \"Interested contributors may be voted to become Committers after a period of valuable activity.
\\n+
Because Contributors have read but not write access to stdcxx code repository, they can check stdcxx out and make changes to their local copy of stdcxx files but they cannot check them back in. \",\n \"To get their changes committed, they must follow the process for Submitting Patches.
\\n+
The stdcxx community welcomes new contributors. \",\n \"If you are interested in getting involved, the first thing to do after reading the project Web pages is to subscribe to the dev mailing list and skimming the archives. \",\n \"If you're looking for ideas for where your help might be needed, browse the bug database or simply ask on the maling list.\",\n \"\\n+Committers\\n+
\\n+ \\n+ \\n+ Committers\\n+
Stdcxx Committers are Developers with commit (or write) access to the stdcxx codebase. \",\n \"For safe changes on trunk all stdcxx committers follow the Commit-Then-Review policy (CTR for short). \",\n \"For potentially unsafe changes or any changes to branches all stdcxx committers follow the Review-Then-Commit policy (RTC for short). \",\n \"Whether a change is safe or not is a judgment call that should be made after careful testing of the change on at least two different platforms with two different compilers. \",\n \"The list of current committers in alphabetical order is below:
\\n+
Committers in italics do not yet have a signed Contributor License Agreement on file. \",\n \"This indicates a transient state after a committer has been voted in but their CLA hasn't been received or processed by the foundation.\",\n \"\\n+\\n+An up-to-date list of all Apache committers (or committers-to-be) is being maintained by Jim Jagielski on this page.\",\n \"\\n+\\n+The mailing list used by stdcxx committers for discussions of the maintenance, development, and porting of the stdcxx project is dev@stdcxx.apache.org. \",\n \"This is an archived, moderated mailing list open to all subscribers. \",\n \"You may subscribe by sending a blank email to dev-subscribe@stdcxx.apache.org.\",\n \"\\n+
\\n+ \\n+ \\n+ PMC\\n+
The stdcxx Project Management Committee (PMC) is a group of volunteers responsible for the formal oversight of the stdcxx podling, its management, and for interfacing with the Apache Board of Directors. \",\n \"The members of the stdcxx PMC are:
\\n+ \\n+
The PMC mailing list is private@stdcxx.apache.org. \",\n \"This is a moderated, by-invitation-only mailing list closed to the public. \",\n \"Invited individuals can subscribe by sending a blank email to private-subscribe@stdcxx.apache.org.\",\n \"\\n+\\n+An example of a topic that might be appropriate for this list is a discussion of the merits of a proposed committer.\",\n \"\\n+
\\n+ \\n+ \\n+ Communication\\n+\\n+
\\n+ Communication about the project and all decisions take place on the project's mailing lists. \",\n \"There are a number good reasons why communicating on mailing lists is preferable to other ways of communicating, including private email or instant messaging. \",\n \"Some of the important ones include:
\\n+
\\n+
Unlike communicating in private, mailing lists make it possible for all list subscribers to benefit from the discussion, and provides an opportunity for those who wouldn't be invited to the private discussion to offer their own feedback on the subject.
\\n+
Unlike Instant Messaging, mailing list make it possible for interested parties to participate asynchronously, regardless of which time zone they are located in.
\\n+
Unlike private communications, mailing list discussions are archived for future reference, with the archives being easily searchable by anyone interested. \",\n \"Mailing list archives are important not just so that new contributors can learn from past decisions but they are an indispensable tool also for long-time committers when we forget why certain things were done a certain way.
\\n+
It is the preferred mode of communicating for all Apache projects. \",\n \"See the Communication section of How the ASF works.
\\n+
\\n+
\\n+If you choose to contact one of the project committers in private expect to be directed to the mailing lists.\",\n \"\\n+
\\n+ \\n+ \\n+ Mailing Lists\\n+
The following table provides a summary of information about stdcxx mailing lists along with a number of interfaces to their archives.\",\n \"\\n+ All lists are moderated. \",\n \"Only subscribers may post. \",\n \"Subscription to private is by invitation of the PMC only.\",\n \"\\n+ With one exception, the activity of each list is monitored and can be viewed along with other interesting information on this page maintained by Ken Coar.\",\n \"\\n+
\\n+ \\n+ \\n+ References\\n+\\n+\\n+
A number of excellent design and programming books describe the C++ Standard Library in an approachable way. \",\n \"In addition, besides the required Class Reference, this implementation of the library also includes an extensive User Guide complete with tutorials and example programs. \",\n \"That being said, the ultimate reference to the C++ Standard Library is, of course, the C++ Standard itself (and to a smaller extent, also the C Standard). \",\n \"An electronic copy of the most recent version of the C++ and C standards can be obtained from the ANSI eStandards store.
\\n+
\\n+
INCITS/ISO/IEC 14882-2003 Programming Languages -- C++
\\n+
INCITS/ISO/IEC 9899-1999 Programming Languages -- C
\\n+
The C++ Standard Library: A Tutorial and Reference by Nicolai M. Josuttis
\\n+
Generic Programming and the STL: Using and Extending the C++ Standard Template Library by Matthew H. Austern
\\n+
Stl Tutorial & Reference Guide: C++ Programming With the Standard Template Library by David R. Musser and Atul Saini
\\n+
The C++ Standard Template Library by P.J. Plauger, Alexander A. Stepanov, Meng Lee, and David R. Musser
\\n+
Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library by Scott Meyers
\\n+
Standard C++ IOStreams and Locales: Advanced Programmer's Guide and Reference by Angelika Langer, Klaus Kreft
\\n+
\\n+ \\n+
\\n+\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/index.xml\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/index.xml\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/site.xml?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/content/xdocs/site.xml (added)\\n+++ stdcxx/site/forrest/src/documentation/content/xdocs/site.xml Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,62 @@\\n+\\n+\\n+\\n+\\n+\\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+ \\n+\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/site.xml\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml (added)\\n+++ stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,39 @@\\n+\\n+\\n+\\n+\\n+\\n+ \\n+ \\n+\\n+\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/content/xdocs/tabs.xml\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\\nAdded: stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db?rev=618441&view=auto\\n==============================================================================\\nBinary file - no diff available.\",\n \"\\nPropchange: stdcxx/site/forrest/src/documentation/resources/images/Thumbs.db\\n------------------------------------------------------------------------------\\nsvn:mime-type = application/octet-stream\\nAdded: stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png?rev=618441&view=auto\\n==============================================================================\\nBinary file - no diff available.\",\n \"\\nPropchange: stdcxx/site/forrest/src/documentation/resources/images/stdcxx.png\\n------------------------------------------------------------------------------\\nsvn:mime-type = application/octet-stream\\nAdded: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat\\nURL: http://svn.apache.org/viewvc/stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat?rev=618441&view=auto\\n==============================================================================\\n--- stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat (added)\\n+++ stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat Mon Feb 4 13:20:33 2008\\n@@ -0,0 +1,29 @@\\n+\\n+\\n+\\n+\\n+\\n+\\n+ \\n+\\n+ \\n+\\nPropchange: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat\\n------------------------------------------------------------------------------\\nsvn:eol-style = native\\nPropchange: stdcxx/site/forrest/src/documentation/resources/schema/catalog.xcat\\n------------------------------------------------------------------------------\\nsvn:keywords = Id\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"Pile-CC\"\n}"},"scores":{"kind":"list like","value":[0.0007035451708361506,0.0006134049035608768,0.0006426551844924688,0.0005986348260194063,0.0005946924793533981,0.0006146807572804391,0.0006447124178521335,0.0006465214537456632,0.00060706224758178,0.0006409477209672332,0.0006330204196274281,0.0006295026396401227,0.0006632183212786913,0.000627842964604497,0.0006325240829028189,0.0006570584955625236,0.0006447404157370329,0.0006689723231829703,0.0006020688451826572,0.0005992219084873796,0.0006020045839250088,0.0006627409602515399,0.0005866767605766654,0.0006062683532945812,0.0005934128421358764,0.0006488974904641509,0.0006389496265910566,0.0006094641285017133,0.0006368949543684721,0.0006322559202089906,0.0006821296410635114,0.0006836375105194747,0.0006272194441407919,0.0006191080319695175,0.0005980400601401925,0.0006310789613053203,0.0006212379666976631,0.0006298369262367487,0.0006284763803705573,0.0006393885123543441,0.0006875270628370345,0.0006413537194021046,0.0006232029991224408,0.0006189779378473759,0.0006463292520493269,0.0006288993754424155,0.0006579354521818459,0.0006903401226736605,0.0006609490374103189,0.0006472949171438813,0.0006630363059230149,0.0006438893615268171,0.0006471360684372485,0.0006663364474661648,0.000708877865690738,0.00066899269586429,0.0006472535897046328,0.0006312557961791754,0.0006063013570383191,0.0006563910283148289,0.0006515209097415209,0.0005951764178462327,0.0006454785470850766,0.000604617758654058,0.000634308613371104,0.0006294376216828823,0.0005842981045134366,0.000584679190069437,0.0006231388542801142,0.0006678301724605262,0.0005940973642282188,0.0006898350547999144,0.000642087368760258,0.0006287681753747165,0.0006028555217199028,0.0006199529743753374,0.000662679725792259,0.001221468672156334,0.0005477136583067477,0.000623601081315428,0.0005565897445194423,0.0005869667511433363,0.0009662400116212666,0.0007823980413377285,0.0005743929068557918,0.0005983915762044489,0.0014559132978320122,0.0006190649583004415,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.0009717977955006063,0.0007816170109435916,0.0008957785903476179,0.0006253810133785009,0.0006547874072566628,0.0005927636520937085,0.0010083367815241218,0.0005477136583067477,0.000623601081315428,0.0005565897445194423,0.0005869667511433363,0.001465709414333105,0.0007171027828007936,0.000594776647631079,0.0006270706653594971,0.0005961725837551057,0.0015280952211469412,0.0007698246045038104,0.0006735803908668458,0.0007196921505965292,0.0008892136393114924,0.0006909788935445249,0.0011855942429974675,0.0006190649583004415,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.0008267214871011674,0.0037748434115201235,0.000928986060898751,0.0006190649583004415,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.007233304902911186,0.0013376508140936494,0.0007124932017177343,0.0006559666944667697,0.0005457323859445751,0.0005901496624574065,0.0007320291479118168,0.0006010952638462186,0.0006480016745626926,0.0005952322972007096,0.0005453049670904875,0.0005909275496378541,0.0005999276763759553,0.0005600978620350361,0.0005866694846190512,0.0005629306542687118,0.0005898867966607213,0.0005908396560698748,0.0006052580429241061,0.0009262634557671845,0.0006221789517439902,0.000675845833029598,0.0006468953215517104,0.0006162598729133606,0.0008214362896978855,0.0007991212187334895,0.000562206725589931,0.0007186982547864318,0.0007290307548828423,0.0005337951006367803,0.000560545886401087,0.0005907154991291463,0.0006480696029029787,0.0006504572229459882,0.0005776354810222983,0.0006043910398148,0.000548947078641504,0.000578820938244462,0.0006057361606508493,0.0007704249583184719,0.0005903276614844799,0.000528634584043175,0.0005862396792508662,0.000612983014434576,0.0006403038860298693,0.0005977796390652657,0.0005868744337931275,0.0006082101026549935,0.0006044270121492445,0.000542239286005497,0.0007016212330199778,0.0005489224568009377,0.0006461207522079349,0.0008776969043537974,0.0006736622308380902,0.0005928514874540269,0.0006959016318432987,0.0005953590734861791,0.0008048847084864974,0.0032831528224051,0.0006772339693270624,0.0006276849890127778,0.0012899214634671807,0.0006190649583004415,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.007233304902911186,0.000739838695153594,0.0005846151034347713,0.0005861572572030127,0.0006248745485208929,0.0009523595799691975,0.0006846454925835133,0.0005888399900868535,0.0005846151034347713,0.0005861572572030127,0.0006248745485208929,0.0009523595799691975,0.0006846454925835133,0.0005741578643210232,0.0006685927510261536,0.0010959033388644457,0.0020671545062214136,0.0006098801386542618,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.007091951556503773,0.000809315824881196,0.000568951538298279,0.0006509710219688714,0.007091951556503773,0.00072290695970878,0.0009610773995518684,0.0012872436782345176,0.0007906529353931546,0.0007629032479599118,0.0014538108371198177,0.0008885340066626668,0.0007778097642585635,0.0010375767014920712,0.0013712223153561354,0.0020995482336729765,0.0006098801386542618,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.007091951556503773,0.000809315824881196,0.000568951538298279,0.0006509710219688714,0.007091951556503773,0.00072290695970878,0.0009610773995518684,0.0012872436782345176,0.0007940237410366535,0.0007585434941574931,0.0014538108371198177,0.0008885340066626668,0.0007778097642585635,0.0010453838622197509,0.001365393283776939,0.0006190649583004415,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.007233304902911186,0.0006755253998562694,0.0006541156908497214,0.0005484431749209762,0.0005974193918518722,0.0007635829388163984,0.0006340638501569629,0.0005605747574009001,0.0005798728088848293,0.0007468181429430842,0.0008020828827284276,0.000670330657158047,0.00068721326533705,0.0006552094127982855,0.0006337653612717986,0.0006724405684508383,0.000801420072093606,0.0005935715162195265,0.0007049199775792658,0.0006520675378851593,0.0008802153170108795,0.0006099577876739204,0.0005948619800619781,0.0005561647121794522,0.0005971167702227831,0.0009275281336158514,0.0010236932430416346,0.0006138538010418415,0.0005776533507741988,0.0005608994397334754,0.0006524964701384306,0.0005635899142362177,0.0006534169078804553,0.0007309768698178232,0.0005935715162195265,0.0007375666173174977,0.0006553190178237855,0.0007263147854246199,0.0006903191097080708,0.00063770153792575,0.0005823891260661185,0.0007037977338768542,0.0005850822199136019,0.0005446354043669999,0.0006321679102256894,0.0006111541879363358,0.0007056113099679351,0.0006223227828741074,0.0007517353515140712,0.000575026439037174,0.0005855204071849585,0.0006390538183040917,0.0005478968960233033,0.0005738367326557636,0.0007353877881541848,0.0006190649583004415,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.00572609156370163,0.0005828391877003014,0.0006760196993127465,0.000738517555873841,0.0006937016150914133,0.0005947358440607786,0.0006648672861047089,0.0008089522598311305,0.0009720831294544041,0.0006190649583004415,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.007233304902911186,0.0007005168008618057,0.0007180780521593988,0.0007721713627688587,0.0006562877097167075,0.0007277767290361226,0.0006896043196320534,0.0007684573065489531,0.0013787433272227645,0.0013050043489784002,0.0016743148444220424,0.0006361918640322983,0.0018269948195666075,0.0005986185860820115,0.0005576575640588999,0.0006254241452552378,0.0005535128293558955,0.0005704997456632555,0.007233304902911186,0.0006556938169524074,0.000626199587713927,0.0006537841400131583,0.0007128252764232457,0.0008640309097245336],"string":"[\n 0.0007035451708361506,\n 0.0006134049035608768,\n 0.0006426551844924688,\n 0.0005986348260194063,\n 0.0005946924793533981,\n 0.0006146807572804391,\n 0.0006447124178521335,\n 0.0006465214537456632,\n 0.00060706224758178,\n 0.0006409477209672332,\n 0.0006330204196274281,\n 0.0006295026396401227,\n 0.0006632183212786913,\n 0.000627842964604497,\n 0.0006325240829028189,\n 0.0006570584955625236,\n 0.0006447404157370329,\n 0.0006689723231829703,\n 0.0006020688451826572,\n 0.0005992219084873796,\n 0.0006020045839250088,\n 0.0006627409602515399,\n 0.0005866767605766654,\n 0.0006062683532945812,\n 0.0005934128421358764,\n 0.0006488974904641509,\n 0.0006389496265910566,\n 0.0006094641285017133,\n 0.0006368949543684721,\n 0.0006322559202089906,\n 0.0006821296410635114,\n 0.0006836375105194747,\n 0.0006272194441407919,\n 0.0006191080319695175,\n 0.0005980400601401925,\n 0.0006310789613053203,\n 0.0006212379666976631,\n 0.0006298369262367487,\n 0.0006284763803705573,\n 0.0006393885123543441,\n 0.0006875270628370345,\n 0.0006413537194021046,\n 0.0006232029991224408,\n 0.0006189779378473759,\n 0.0006463292520493269,\n 0.0006288993754424155,\n 0.0006579354521818459,\n 0.0006903401226736605,\n 0.0006609490374103189,\n 0.0006472949171438813,\n 0.0006630363059230149,\n 0.0006438893615268171,\n 0.0006471360684372485,\n 0.0006663364474661648,\n 0.000708877865690738,\n 0.00066899269586429,\n 0.0006472535897046328,\n 0.0006312557961791754,\n 0.0006063013570383191,\n 0.0006563910283148289,\n 0.0006515209097415209,\n 0.0005951764178462327,\n 0.0006454785470850766,\n 0.000604617758654058,\n 0.000634308613371104,\n 0.0006294376216828823,\n 0.0005842981045134366,\n 0.000584679190069437,\n 0.0006231388542801142,\n 0.0006678301724605262,\n 0.0005940973642282188,\n 0.0006898350547999144,\n 0.000642087368760258,\n 0.0006287681753747165,\n 0.0006028555217199028,\n 0.0006199529743753374,\n 0.000662679725792259,\n 0.001221468672156334,\n 0.0005477136583067477,\n 0.000623601081315428,\n 0.0005565897445194423,\n 0.0005869667511433363,\n 0.0009662400116212666,\n 0.0007823980413377285,\n 0.0005743929068557918,\n 0.0005983915762044489,\n 0.0014559132978320122,\n 0.0006190649583004415,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.0009717977955006063,\n 0.0007816170109435916,\n 0.0008957785903476179,\n 0.0006253810133785009,\n 0.0006547874072566628,\n 0.0005927636520937085,\n 0.0010083367815241218,\n 0.0005477136583067477,\n 0.000623601081315428,\n 0.0005565897445194423,\n 0.0005869667511433363,\n 0.001465709414333105,\n 0.0007171027828007936,\n 0.000594776647631079,\n 0.0006270706653594971,\n 0.0005961725837551057,\n 0.0015280952211469412,\n 0.0007698246045038104,\n 0.0006735803908668458,\n 0.0007196921505965292,\n 0.0008892136393114924,\n 0.0006909788935445249,\n 0.0011855942429974675,\n 0.0006190649583004415,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.0008267214871011674,\n 0.0037748434115201235,\n 0.000928986060898751,\n 0.0006190649583004415,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.007233304902911186,\n 0.0013376508140936494,\n 0.0007124932017177343,\n 0.0006559666944667697,\n 0.0005457323859445751,\n 0.0005901496624574065,\n 0.0007320291479118168,\n 0.0006010952638462186,\n 0.0006480016745626926,\n 0.0005952322972007096,\n 0.0005453049670904875,\n 0.0005909275496378541,\n 0.0005999276763759553,\n 0.0005600978620350361,\n 0.0005866694846190512,\n 0.0005629306542687118,\n 0.0005898867966607213,\n 0.0005908396560698748,\n 0.0006052580429241061,\n 0.0009262634557671845,\n 0.0006221789517439902,\n 0.000675845833029598,\n 0.0006468953215517104,\n 0.0006162598729133606,\n 0.0008214362896978855,\n 0.0007991212187334895,\n 0.000562206725589931,\n 0.0007186982547864318,\n 0.0007290307548828423,\n 0.0005337951006367803,\n 0.000560545886401087,\n 0.0005907154991291463,\n 0.0006480696029029787,\n 0.0006504572229459882,\n 0.0005776354810222983,\n 0.0006043910398148,\n 0.000548947078641504,\n 0.000578820938244462,\n 0.0006057361606508493,\n 0.0007704249583184719,\n 0.0005903276614844799,\n 0.000528634584043175,\n 0.0005862396792508662,\n 0.000612983014434576,\n 0.0006403038860298693,\n 0.0005977796390652657,\n 0.0005868744337931275,\n 0.0006082101026549935,\n 0.0006044270121492445,\n 0.000542239286005497,\n 0.0007016212330199778,\n 0.0005489224568009377,\n 0.0006461207522079349,\n 0.0008776969043537974,\n 0.0006736622308380902,\n 0.0005928514874540269,\n 0.0006959016318432987,\n 0.0005953590734861791,\n 0.0008048847084864974,\n 0.0032831528224051,\n 0.0006772339693270624,\n 0.0006276849890127778,\n 0.0012899214634671807,\n 0.0006190649583004415,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.007233304902911186,\n 0.000739838695153594,\n 0.0005846151034347713,\n 0.0005861572572030127,\n 0.0006248745485208929,\n 0.0009523595799691975,\n 0.0006846454925835133,\n 0.0005888399900868535,\n 0.0005846151034347713,\n 0.0005861572572030127,\n 0.0006248745485208929,\n 0.0009523595799691975,\n 0.0006846454925835133,\n 0.0005741578643210232,\n 0.0006685927510261536,\n 0.0010959033388644457,\n 0.0020671545062214136,\n 0.0006098801386542618,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.007091951556503773,\n 0.000809315824881196,\n 0.000568951538298279,\n 0.0006509710219688714,\n 0.007091951556503773,\n 0.00072290695970878,\n 0.0009610773995518684,\n 0.0012872436782345176,\n 0.0007906529353931546,\n 0.0007629032479599118,\n 0.0014538108371198177,\n 0.0008885340066626668,\n 0.0007778097642585635,\n 0.0010375767014920712,\n 0.0013712223153561354,\n 0.0020995482336729765,\n 0.0006098801386542618,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.007091951556503773,\n 0.000809315824881196,\n 0.000568951538298279,\n 0.0006509710219688714,\n 0.007091951556503773,\n 0.00072290695970878,\n 0.0009610773995518684,\n 0.0012872436782345176,\n 0.0007940237410366535,\n 0.0007585434941574931,\n 0.0014538108371198177,\n 0.0008885340066626668,\n 0.0007778097642585635,\n 0.0010453838622197509,\n 0.001365393283776939,\n 0.0006190649583004415,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.007233304902911186,\n 0.0006755253998562694,\n 0.0006541156908497214,\n 0.0005484431749209762,\n 0.0005974193918518722,\n 0.0007635829388163984,\n 0.0006340638501569629,\n 0.0005605747574009001,\n 0.0005798728088848293,\n 0.0007468181429430842,\n 0.0008020828827284276,\n 0.000670330657158047,\n 0.00068721326533705,\n 0.0006552094127982855,\n 0.0006337653612717986,\n 0.0006724405684508383,\n 0.000801420072093606,\n 0.0005935715162195265,\n 0.0007049199775792658,\n 0.0006520675378851593,\n 0.0008802153170108795,\n 0.0006099577876739204,\n 0.0005948619800619781,\n 0.0005561647121794522,\n 0.0005971167702227831,\n 0.0009275281336158514,\n 0.0010236932430416346,\n 0.0006138538010418415,\n 0.0005776533507741988,\n 0.0005608994397334754,\n 0.0006524964701384306,\n 0.0005635899142362177,\n 0.0006534169078804553,\n 0.0007309768698178232,\n 0.0005935715162195265,\n 0.0007375666173174977,\n 0.0006553190178237855,\n 0.0007263147854246199,\n 0.0006903191097080708,\n 0.00063770153792575,\n 0.0005823891260661185,\n 0.0007037977338768542,\n 0.0005850822199136019,\n 0.0005446354043669999,\n 0.0006321679102256894,\n 0.0006111541879363358,\n 0.0007056113099679351,\n 0.0006223227828741074,\n 0.0007517353515140712,\n 0.000575026439037174,\n 0.0005855204071849585,\n 0.0006390538183040917,\n 0.0005478968960233033,\n 0.0005738367326557636,\n 0.0007353877881541848,\n 0.0006190649583004415,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.00572609156370163,\n 0.0005828391877003014,\n 0.0006760196993127465,\n 0.000738517555873841,\n 0.0006937016150914133,\n 0.0005947358440607786,\n 0.0006648672861047089,\n 0.0008089522598311305,\n 0.0009720831294544041,\n 0.0006190649583004415,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.007233304902911186,\n 0.0007005168008618057,\n 0.0007180780521593988,\n 0.0007721713627688587,\n 0.0006562877097167075,\n 0.0007277767290361226,\n 0.0006896043196320534,\n 0.0007684573065489531,\n 0.0013787433272227645,\n 0.0013050043489784002,\n 0.0016743148444220424,\n 0.0006361918640322983,\n 0.0018269948195666075,\n 0.0005986185860820115,\n 0.0005576575640588999,\n 0.0006254241452552378,\n 0.0005535128293558955,\n 0.0005704997456632555,\n 0.007233304902911186,\n 0.0006556938169524074,\n 0.000626199587713927,\n 0.0006537841400131583,\n 0.0007128252764232457,\n 0.0008640309097245336\n]"},"avg_score":{"kind":"number","value":0.0009091587420552968,"string":"0.000909"},"num_sents":{"kind":"number","value":375,"string":"375"}}},{"rowIdx":726,"cells":{"texts":{"kind":"list like","value":["using System;\n\nnamespace ViennaNET.ArcSight.","Exceptions\n{\n /// \n /// Исключение, возникающее при наличии ошибки в\n /// значениях полей передаваемого сообщения. ","\n /// \n public class CefMessageValidationException : Exception\n {\n public CefMessageValidationException(string message) : base (message)\n {\n }\n }\n}"],"string":"[\n \"using System;\\n\\nnamespace ViennaNET.ArcSight.\",\n \"Exceptions\\n{\\n /// \\n /// Исключение, возникающее при наличии ошибки в\\n /// значениях полей передаваемого сообщения. \",\n \"\\n /// \\n public class CefMessageValidationException : Exception\\n {\\n public CefMessageValidationException(string message) : base (message)\\n {\\n }\\n }\\n}\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"Github\"\n}"},"scores":{"kind":"list like","value":[0.0006794374203309417,0.0010087413247674704,0.0010803121840581298],"string":"[\n 0.0006794374203309417,\n 0.0010087413247674704,\n 0.0010803121840581298\n]"},"avg_score":{"kind":"number","value":0.0009228303097188473,"string":"0.000923"},"num_sents":{"kind":"number","value":3,"string":"3"}}},{"rowIdx":727,"cells":{"texts":{"kind":"list like","value":["The Senate passed legislation on Thursday breaking with President Trump Donald John TrumpBubba Wallace to be driver of Michael Jordan, Denny Hamlin NASCAR team Graham: GOP will confirm Trump's Supreme Court nominee before the election Southwest Airlines, unions call for six-month extension of government aid MORE’s Syria policy.","\n\nSenators voted 77-23 to send the legislation to the House that includes a provision warning Trump against a “precipitous” withdrawal of troops from Syria and Afghanistan.","\n\nADVERTISEMENT\n\nIt also asks the administration to certify that certain conditions have been met \"for the enduring defeat of al Qaeda and ISIS before initiating any significant withdrawal of United States forces from Syria or Afghanistan.\"","\n\nThe bill was approved after it overcame a filibuster earlier this week.","\n\n“I keep reading where the national media writes that the United States Senate rebuked — they used the word 'rebuked' — President Trump. ","Nothing could be further from the truth,” Risch, the chairman of the Foreign Relations Committee, said.","\n\nIn addition to the Syria amendment, the bill also included sanctions against the Syrian government, increased support for Israel and Jordan and a provision that would let states penalize businesses that take part in boycotts or divestments of Israel.","\n\nBoth the Syria amendment and the anti-BDS provisions sparked division among Democrats.","\n\nSen. Chris Murphy Christopher (Chris) Scott MurphyDemocratic senator calls for 'more flexible' medical supply chain to counter pandemics The Hill's 12:30 Report - Presented by Facebook - Don't expect a government check anytime soon GOP chairman to release interim report on Biden probe 'in about a week' MORE (D-Conn.) warned that the Syria proposal, offered by Senate Majority Leader Mitch McConnell Addison (Mitch) Mitchell McConnellGraham: GOP will confirm Trump's Supreme Court nominee before the election Trump puts Supreme Court fight at center of Ohio rally The Memo: Dems face balancing act on SCOTUS fight MORE (R-Ky.), is “the absolute wrong way to address President Trump’s backwards foreign policy in the Middle East.”","\n\nIn response to concerns from Democrats, the Senate easily cleared a tweak to McConnell's amendment that would clarify that the resolution should not be \"constructed as a declaration of war or an authorization of the use of military force.\"","\n\nTrump's decision to withdraw troops from Syria, which precipitated the resignation of former Defense Secretary James Mattis James Norman MattisBiden courts veterans amid fallout from Trump military controversies Trump says he wanted to take out Syria's Assad but Mattis opposed it Gary Cohn: 'I haven't made up my mind' on vote for president in November MORE, sparked fierce backlash on Capitol Hill.","\n\nTwo officials told The New York Times last year that the administration had ordered the U.S. military to start withdrawing troops in Afghanistan, but Trump, who has long railed against the war there, has not made an official announcement.","\n\nThe Washington Post reported last week that the United States and the Taliban were moving closer to a deal that could result in the removal of U.S. troops from the country.","\n\nMeanwhile, Democrats had raised First Amendment concerns about the anti-BDS provision, which splintered most of the party’s 2020 contenders and caucus leadership.","\n\n“While I do not support the BDS movement, we must defend every American’s constitutional right to engage in political activity. ","It is clear to me that this bill would violate Americans’ First Amendment rights,” Sen. Bernie Sanders Bernie SandersJacobin editor: Primarying Schumer would force him to fight Trump's SCOTUS nominee Trump campaign plays up Biden's skills ahead of Cleveland debate: 'He's actually quite good' Young voters backing Biden by 2:1 margin: poll MORE (I-Vt.) ","said in a statement last week."],"string":"[\n \"The Senate passed legislation on Thursday breaking with President Trump Donald John TrumpBubba Wallace to be driver of Michael Jordan, Denny Hamlin NASCAR team Graham: GOP will confirm Trump's Supreme Court nominee before the election Southwest Airlines, unions call for six-month extension of government aid MORE’s Syria policy.\",\n \"\\n\\nSenators voted 77-23 to send the legislation to the House that includes a provision warning Trump against a “precipitous” withdrawal of troops from Syria and Afghanistan.\",\n \"\\n\\nADVERTISEMENT\\n\\nIt also asks the administration to certify that certain conditions have been met \\\"for the enduring defeat of al Qaeda and ISIS before initiating any significant withdrawal of United States forces from Syria or Afghanistan.\\\"\",\n \"\\n\\nThe bill was approved after it overcame a filibuster earlier this week.\",\n \"\\n\\n“I keep reading where the national media writes that the United States Senate rebuked — they used the word 'rebuked' — President Trump. \",\n \"Nothing could be further from the truth,” Risch, the chairman of the Foreign Relations Committee, said.\",\n \"\\n\\nIn addition to the Syria amendment, the bill also included sanctions against the Syrian government, increased support for Israel and Jordan and a provision that would let states penalize businesses that take part in boycotts or divestments of Israel.\",\n \"\\n\\nBoth the Syria amendment and the anti-BDS provisions sparked division among Democrats.\",\n \"\\n\\nSen. Chris Murphy Christopher (Chris) Scott MurphyDemocratic senator calls for 'more flexible' medical supply chain to counter pandemics The Hill's 12:30 Report - Presented by Facebook - Don't expect a government check anytime soon GOP chairman to release interim report on Biden probe 'in about a week' MORE (D-Conn.) warned that the Syria proposal, offered by Senate Majority Leader Mitch McConnell Addison (Mitch) Mitchell McConnellGraham: GOP will confirm Trump's Supreme Court nominee before the election Trump puts Supreme Court fight at center of Ohio rally The Memo: Dems face balancing act on SCOTUS fight MORE (R-Ky.), is “the absolute wrong way to address President Trump’s backwards foreign policy in the Middle East.”\",\n \"\\n\\nIn response to concerns from Democrats, the Senate easily cleared a tweak to McConnell's amendment that would clarify that the resolution should not be \\\"constructed as a declaration of war or an authorization of the use of military force.\\\"\",\n \"\\n\\nTrump's decision to withdraw troops from Syria, which precipitated the resignation of former Defense Secretary James Mattis James Norman MattisBiden courts veterans amid fallout from Trump military controversies Trump says he wanted to take out Syria's Assad but Mattis opposed it Gary Cohn: 'I haven't made up my mind' on vote for president in November MORE, sparked fierce backlash on Capitol Hill.\",\n \"\\n\\nTwo officials told The New York Times last year that the administration had ordered the U.S. military to start withdrawing troops in Afghanistan, but Trump, who has long railed against the war there, has not made an official announcement.\",\n \"\\n\\nThe Washington Post reported last week that the United States and the Taliban were moving closer to a deal that could result in the removal of U.S. troops from the country.\",\n \"\\n\\nMeanwhile, Democrats had raised First Amendment concerns about the anti-BDS provision, which splintered most of the party’s 2020 contenders and caucus leadership.\",\n \"\\n\\n“While I do not support the BDS movement, we must defend every American’s constitutional right to engage in political activity. \",\n \"It is clear to me that this bill would violate Americans’ First Amendment rights,” Sen. Bernie Sanders Bernie SandersJacobin editor: Primarying Schumer would force him to fight Trump's SCOTUS nominee Trump campaign plays up Biden's skills ahead of Cleveland debate: 'He's actually quite good' Young voters backing Biden by 2:1 margin: poll MORE (I-Vt.) \",\n \"said in a statement last week.\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"OpenWebText2\"\n}"},"scores":{"kind":"list like","value":[0.0006662983214482665,0.0009312902693636715,0.0006580276531167328,0.004975206684321165,0.000600165338255465,0.0006978631718084216,0.0008212320390157402,0.0030958724673837423,0.0008649060619063675,0.0006967872031964362,0.0008795374887995422,0.000678174605127424,0.0010114791803061962,0.0007534482865594327,0.001376995351165533,0.0011004531988874078,0.0006655615288764238],"string":"[\n 0.0006662983214482665,\n 0.0009312902693636715,\n 0.0006580276531167328,\n 0.004975206684321165,\n 0.000600165338255465,\n 0.0006978631718084216,\n 0.0008212320390157402,\n 0.0030958724673837423,\n 0.0008649060619063675,\n 0.0006967872031964362,\n 0.0008795374887995422,\n 0.000678174605127424,\n 0.0010114791803061962,\n 0.0007534482865594327,\n 0.001376995351165533,\n 0.0011004531988874078,\n 0.0006655615288764238\n]"},"avg_score":{"kind":"number","value":0.0012043116970316453,"string":"0.001204"},"num_sents":{"kind":"number","value":17,"string":"17"}}},{"rowIdx":728,"cells":{"texts":{"kind":"list like","value":["Properties of Cobalt and Nickel in Aqueous Solution\nCobalt and nickel have very similar chemical properties. ","In aqueous solution both elements are normally found as divalent cations (e.g. Co++ or Ni++) in acid solution, with similar solubilities.","\nBoth are soluble as the respective sulphates, chlorides, or nitrates in acid solution, but are largely insoluble in alkaline conditions unless chelating agents are present. (","Both cations are chelated strongly by ammonia, for example). ","Their sulphide compounds have similar properties, (the KSP values are similar leading to a similar pH of formation with S2− ions), as do their respective carbonates.","\nThis phenomenon presents an ongoing problem for the extractive metallurgist, as Co and Ni are invariably found together in naturally occurring ores, but must ultimately be separated to make maximum use of each metal. ","Fortunately however, there are exceptions to this pattern of similar behavior, which can be exploited, and will be discussed below.","\nRatio of Cobalt to Nickel Occurring Naturally in Nickel Ores\nNi and Co commonly occur together in nature as sulphide ore deposits, and the ratio of Co:Ni in Ni ores is surprisingly constant in the range of about 1:15 up to 1:30. ","This is true at least in unaltered sulphide ores; although this ratio can be quite different if weathering of the ores has occurred, (over many millennia),\nA general review of nickel metallurgy is to be found in the excellent book “The Winning of Nickel”, by Joseph P. Boldt Jr., and Paul Queneau Sr., ","published by Methuen and Co. 1967. ","A more recent review of laterites in particular is found in “The Past and Future of Nickel Laterites,” by Ashok Dalvi, Gordon Bacon, and Robert Osborne in: PDAC 2004 International Convention, Trade Show and Investors' Exchange, (Mar. 7-10, 2004).","\nWeathering of surface Ni deposits is common especially in tropical countries, and such deposits are usually referred to as Ni laterites; due to slight differences in chemistry, this weathering frequently results in a partial separation of Ni and Co over a vertical horizon, compared to the original sulphide ore. ","Some concentration of Co into the so-called limonite layer often is the result, so Co:Ni ratios in laterites considered for hydrometallurgical processing vary substantially from the usual ratio in sulphides, e.g. a ratio of 1:10 or even lower may be found in limonite.","\nCo Separation from Nickel in a Leach Solution . . . . ","Overview\nThe distribution of Co and Ni in most leaching processes is very similar. ","Thus leaching of Ni—Co ores or concentrates usually results in a mixed solution of Co and Ni, as well as other materials.","\nHowever, Ni and Co have to be separated eventually to obtain maximum use and payment for each element, as their end-use is significantly different, e.g. different metal alloys. ","With only a few notable exceptions, Ni is much more abundant in ores or concentrates than Co. Thus in a mixed Ni—Co solution, the problem of separation can be more accurately stated as separating Co (as an impurity, albeit of value) from a Ni solution. ","It also happens that Co has a few specific chemical properties that allow for its selective extraction from a mixture of elements in solution, whereas Ni in general does not have such properties.","\nA variety of processes have been (and some still are) used commercially to achieve this objective, but all of them have significant costs, and it is the objective of the present invention to provide a more efficient and more cost-effective method.","\nAlso, because of the greater value of Co, this need to purify the Ni solution of Co should not obscure the secondary need to also recover Co itself in an economic manner, which is part of the present invention.","\nA number of processes have been used commercially for Co separation from Ni, for example:\nPrecipitation of Co from Ni—Co Solution as Co(OH)3 \nThis is an old process, (see the above-referenced book by Boldt and Queneau), one of the first known methods, and still used commercially. ","With strong oxidants, a Co++ solution can readily be oxidized to Co+++, which is essentially insoluble in dilute acid solution (say pH 2-6). ","Co is thus precipitated as Co(OH)3 whilst the Ni stays largely in solution. ","Oxidants used for this purpose include Cl2 and ozone. ","Electro-oxidation can also be used. ","However, the process is costly and inefficient, due to significant co-oxidation of Ni++ to a similar product, and has generally fallen out of favour.","\nSelective Solvent Extraction (SX) of Co from Ni—Co Solution\nThis approach has been the subject of many investigations, some of which have been commercialized, and some of these are listed in the referenced article, “Cobalt-Nickel Separation in Hydrometallurgy: a Review,” by Douglas S. Flett, in: Chemistry for Sustainable Development 12 (2004), pages 81-91. ","There are some organic extractants which will selectively extract Co with respect to Ni. ","Primarily these are one of two types:\ni) Ternary and quaternary amines (Alamine™ 336 for example), which can extract some metal chloride complexes (e.g. CoCl42−) from a strong chloride aqueous environment. ","Unusually, Ni doesn't form such chloride complexes, so a good separation of Ni from other elements can sometimes be achieved. ","However, the requirement of the strong chloride concentration (several molar) severely limits the applicability of the process, and in reality omits it from serious consideration for a typical leach liquor.","\nii) Phosphinic acids (e.g. bis 2,4,4-trimethylpentyl phosphinic acid, sold commercially as Cyanex™ 272), which will extract Co selectively over Ni, without the need for a chelating agent as in the amines. ","Although this extractant works well in pure solutions, unfortunately it also extracts many other metals commonly found in leach solutions, such as Mg and Mn, which limits its usefulness. ","This limitation is illustrated in the first two Examples described below. ","Although Mg can be scrubbed off the loaded organic stream by Ni/Co (with difficulty), by using a large number of mixer/settlers in counter-current mode, as was done at the Bulong plant (described by Donegan (“Direct Solvent Extraction of Nickel at Bulong Operations,” by S. Donegan, in: Minerals Engineering 19 (2006), pages 1234-1245), Mn cannot be scrubbed off. ","The only remedy is to co-extract all the Mn along with the Co, and pay for the cost of the Mn extraction/stripping, particularly the cost of the ammonia used for neutralization of the organic extractant. ","As a result of this limitation, Cyanex 272 is best applied after some prior purification, which itself is both costly and inefficient.","\nSelective SX of Ni from Ni—Co Solution\nThis approach was invented and commercialized at the Queensland Nickel (QNI) plant in Yabulu, Queensland, Australia, very successfully in the 80's, and is well summarized by the above-referenced Flett review article, and also by Reid and Price.","\n(Reid, J G and Price, M J, 1993. ","Ammoniacal solvent extraction at Queensland Nickel: Process installation and operation, in Solvent Extraction in the Process Industries Volume 1 (Proceedings of International Solvent Extraction Conference 1993) (eds: D H Logsdail and M J Slater), pp 225-231 (Elsevier Applied Science: London and New York.","\nThe process is effective but suffers from high cost, as the major component (Ni), is being extracted away from the ‘impurity’ (Co), generally a more expensive route than the opposite. ","The impurities are all left with the Co.\nAlso the extractant used (hydroxyoxime) is prone to rapid degradation by Co II oxidation, and hence must be re-oximated on a regular basis, at considerable cost. ","Pre-oxidation of Co II to Co III is necessary to minimize this problem, but is not 100% effective, leading to continuous re-oximation of the extractant, at high cost.","\nStripping of the Ni from the loaded organic can be done with either strong ammonia solutions (250 g/l NH3), or by acid, as was done at the Cawse mine in Western Australia for a while, as discussed by Flett (referenced above). ","The former fits in well with NiCO3 production, (by steam stripping of NH3), the latter with a Ni electrowinning flowsheet.","\nAlthough technically feasible, this approach is relatively expensive as noted, and does not produce a pure Co product, as the Ni left in the raffinate produces a Ni:Co ratio in this stream of at least 1:1. ","At Yabulu, a separate Co refinery had to be built eventually for re-processing of the Co-rich stream, and this refinery had its own technical and financial challenges.","\nHydrogen Reduction of Ni from Ni—Co Solution\nThis approach was first commercialized in about 1950 at the Sherritt Gordon plant in Fort Saskatchewan, Alberta, as described by Boldt et al. ","The method has been considered the standard process for nickel recovery by some designers; it has been installed in several other nickel plants since, but suffers from significant drawbacks: Batch mode operation. ","The process apparently can only be operated in this way, (instead of the usual continuous mode). ","This then requires multiple units (autoclaves), with low operating time (need to fill and discharge each batch autoclave frequently) These features lead to high capital and operating costs Heightened safety and occupational health requirements Need for concentrated Ni solution (50-100 g/l [Ni]), and high solution feed temperatures, approx 200° C., again leading to high costs. "," Need for careful control of pH, in pH 7.0 range, with high background levels of ammonium sulphate (200 g/l). "," Large by-product production of ammonium sulphate crystals, at about 7× tonnage of Ni metal production, necessitating evaporative crystallizers, filters, dryers, bagging, storage facilities, etc. ","All leading to high costs. "," Technically complex, thus requiring high level of technical skill, and expensive engineering input from a very limited number of qualified suppliers Further processing costs, downstream from the actual hydrogen reduction due to need for further purification to remove trace amounts of impurities such as S and O. High temperature oxidation and reduction furnaces are needed for this purification. "," Relatively poor quality of Ni product, regarding Co content Poor quality of Co product, as the raffinate contains a Ni:Co ratio of about 1:1, leading to need for another Co refining step, similar to the process described in previous section.","Difficulties with Separation of Cobalt from Nickel in the Presence of Impurities \nAs described in the previous section, Co separation from Ni is difficult, and specific to each situation, e.g. solution chemistry and particularly the impurities in the Co—Ni solution. ","For solutions derived from leaching sulphide concentrates (as at Sherritt Gordon, for example), impurities are generally confined to other base metals such as Fe, Cu and Zn, which can be removed efficiently by known purification methods.","\nHowever, for acidic solutions derived from leaching of laterite ores, other impurities are found, particularly Mg and Mn, and often in much greater concentrations relative to the Ni and Co concentrations, e.g. as much as 10× greater. ","This situation makes it near difficult to use the preferred Cyanex 272 Co extraction method described above without some form of pre-treatment to separate Co and Ni from these impurities, or alternatively pay for the expense of co-extracting Mn.","\nThus, unless Mn extraction is to be tolerated and paid for, treatment of laterite leach liquors is usually required to choose one of two routes: Precipitation of Ni and Co in acid solution away from impurities as much as possible, followed by re-leaching to form a new solution with reduced impurity content. ","This approach for example was followed in the Murrin plant, which is described by Campbell et al in U.S. Pat. ","No. ","7,387,767, and also in the Cawse plant, described by White in U.S. Pat. ","No. ","6,409,979. "," Leach in an ammoniacal alkaline environment, wherein most of damaging impurities are largely absent. ","This approach is adopted by the Caron process, for example (described in Boldt and Queneau), which was used at the QNI plant in Yabulu mentioned above, (now under different ownership and renamed). "," \nThe Caron process requires a pretreatment process of its own, a reductive roast at high temperature. ","This is a pyrometallurgical process, and requires high capital investment. ","It also has high energy requirements and thus has high operating costs. ","For these reasons, it is generally not considered today, although a few plants built years ago are still operating.","\nPractically then, one is confined to the precipitation and releach option as a pre-treatment prior to Co—Ni separation.","\nFor laterite ores therefore, it is desirable, even necessary, that the Mn/Mg be separated out from Ni/Co by first precipitating the Ni/Co from solution, and then releaching. ","This is usually done by one of two methods: 1. ","H2S precipitation of mixed Ni/Co sulphides, (which selectively precipitates Ni/Co over Mn/Mg), followed by filtration and then pressure oxidation of mixed sulphides precipitate, with associated filtration steps, to produce a Ni/Co solution suitable for efficient Cyanex 272 extraction of Co, (as is now done at Murrin Murrin, op cit), or 2. ","Mixed hydroxide precipitation of Ni/Co with MgO (which can be done selectively over Mn and Mg, as practiced at Cawse plant for example, and patented by White, op cit), or with CaO, which is not so selective with respect to Mg/Mn. ","At Cawse, this was followed by re-leaching of mixed hydroxides with ammonium carbonate solution, filtering, then steam stripping the NH3/CO2 from the leach liquor to precipitate Mn/Mg, (and re-adsorbing the same NH3/CO2), and re-filtering. "," \nEither of these processes for Mn/Mg rejection is expensive, especially in capital costs (H2S generating plant, or stripping and absorption plants for NH3/CO2). ","It is an objective of the present invention to be able to treat high Mn/Mg solutions containing both Ni and Co, and separate Co from this solution, without going through either of the existing Mn/Mg rejection alternatives sketched out above.","\nUnfortunately, a large amount of gypsum is formed along with the mixed Ni—Co hydroxide precipitate (MHP) when slaked lime is used as the precipitant for Ni and Co; consequently the MHP contains about 50 wt % gypsum, and only 50 wt % actual Ni and Co hydroxides, (and hence about 22% Ni).","\nAlso both Mg and Mn are partly precipitated from solution (as hydroxides) at about the same pH as Ni and Co, thus further contaminating the product. ","This is a particular problem for laterites where these impurities are usually present in high concentration, e.g. in leach liquors derived from laterites by a High Pressure Acid Leach (HPAL) process.","\nMn is of special interest as well because MHP is of course a mixture of Ni and Co compounds, which eventually have to be separated to make commercial Ni and Co products. ","The conventional technology for this separation is to use solvent extraction on a Ni/Co solution, in particular the extractant Cyanex 272. ","This Cyanex 272 separation is only feasible if Mn and Mg are very low in the feed solution, otherwise they interfere with the Co extraction. ","Generally this limits such refining to feed materials that are already low in Mn: Ni sulphide concentrates generally fall into this category, or are smelted to matte anyway, which is an effective Mn removal step, (into the slag). ","For feed materials that have not been smelted, e.g. laterite high pressure acid leach liquors, a significant Mn presence may be a serious impediment to further processing.","\nCommercial Value of Nickel Hydroxide Products\nMixed Ni—Co hydroxide (MHP) has been produced by at least one Ni mine in the recent past, and several announced projects have included this intermediate in the process flowsheet. ","However, this product has uncertain market value and a limited marketing history, due in part to its purity and grade. ","Since Ni and Co must be separated eventually, the presence of other impurities in the MHP can be a serious impediment to said separation, as described in the previous section.","\nIf slaked lime, (Ca(OH)2), is used as the reagent, it typically precipitates some Mg and Mn from solution along with Ni and Co; and if any traces of base metal impurities, (e.g. Cu, Fe, Zn and Cd), are left in solution from the prior purification, they are also precipitated into the MHP. ","In addition, gypsum is formed of course, thus degrading the Ni grade of product by about 50%. ","If MgO is used instead of slaked lime, better selectivity is found in respect to Mg, and of course no gypsum is formed, so the Ni grade is much better, but most of the same impurity issues remain.","\nAll of the above can affect on the marketing of the MHP, and hence its commercial value. ","Nevertheless for projects with limited Ni/Co production it may be advantageous to be able to sell the MHP as an intermediate product, and thus avoid the extra cost of full refining to metal products on a small scale. ","It was of some importance therefore to improve the quality of MHP, by Co separation upstream.","\nTherefore if the Co is separated out before the precipitation process, the resultant Ni Hydroxide Product (NHP) may have enhanced value.","\nU.S. Pat. ","No. ","6,171,564 relates to a process for treatment of nickel ores and concentrates to recover both Ni and Co as refined metals. ","It is a ‘comprehensive’ process in the sense that: a) Both sulphides and oxides (laterites) are considered as suitable feeds, and b) The process describes a complete flowsheet going all the way to metal product: Acid leaching of solid feed to produce an acidic leach solution, containing Ni, Co and numerous impurities purification of leach solution, in several steps, including solvent extraction precipitation of Ni and Co together as an impure mixed hydroxide by neutralizing acidic solution Releaching of mixed hydroxide in (recycled) ammoniacal solution to redissolve Ni and Co values Separation of Co from Ni in said solution by solvent extraction, followed by stripping and recovery of Co product Further purification of (ammoniacal) raffinate from Co solvent extraction by additional solvent extraction steps Extraction of Ni from purified ammoniacal solution, followed by acidic stripping of organic stream to form purified acidic Ni solution Ni recovery from purified solution by electrowinning, with recycling of spent acid to solvent extraction \nThe Ni and Co content in the feed material are first leached by pressure oxidation (in the case of sulphides) or by acid pressure leaching (in the case of laterites); then the solution is purified to remove primarily Cu, Zn and Fe. ","From the purified solution, Ni and Co are precipitated together at about pH 7-8, using slaked lime, as a mixture of Ni and Co hydroxides, (MHP).","\nMHP is then re-leached in mild conditions, (ambient temperature, dilute solids, neutral pH) with a strong ammonium sulphate solution (200 g/l) at about pH 7.0, as in Reaction (1):Ni(OH)2+(NH4)2SO4→Ni(NH3)2SO4+2H2O (1)\nThus this leach produces a solution of Ni and Co diammine, (Ni(NH3)2++ and Co(NH3)2++ ions), which also contains some impurities, notably Mg and Ca.","\nThe leaching of Ni and Co by this method is not very efficient, (about 90%), due to the mild conditions selected, i.e. the neutral pH and hence very low free ammonia content of the leach solution; almost none of the Ni species in solution is present as free ammonia, NH3. ","As a consequence, significant Ni and Co are left behind in the residue, which therefore has to be releached to avoid unacceptable losses. ","However, the choice of the neutral pH is very important to enable the subsequent solvent extraction steps to proceed efficiently.","\nCo is then extracted selectively from this impure Ni/Co diammine solution using as extractant the Cyanex 272 reagent at about this same pH 7.0, leaving Ni in the raffinate.","\nSince the extraction is from a diammine, (i.e. Co(NH3)2SO4), no neutralization is required to maintain a constant pH, as the ammine is simultaneously converted to ammonia (NH3) during the extraction, which exactly balances the acid production (H+ ions) from the organic reagent, and thus produces ammonium sulphate in the overall extraction reaction (2):Co(NH3)2SO4+2RH (organic reagent)→CoR2 (organic phase)+(NH4)2SO4 (2)\nThus the pH stays almost constant throughout the Co extraction, negating the usual need for neutralizing agent. ","This is an unusual and most beneficial feature of this solvent extraction process, as most other Co and Ni solvent extraction processes need in situ neutralization with ammonia or caustic to counteract acid production, and thus maintain the solution pH within the required range during the reaction, (or else the extraction stops prematurely). ","The significance of the neutralization goes far beyond the simple avoidance of reagent consumption; the normal byproduct of such neutralization with ammonia or caustic is a salt such as ammonium sulphate or sodium sulphate, which rapidly accumulates in the raffinate stream, and must be disposed of in some fashion. ","This is a serious challenge, given the constraints of the system, such as metal contamination of said salt as a potential byproduct, and is sometimes fatal to a process design.","\nCo extraction at this point is only about 90% of the Co contained in the diammine solution, and co-extraction of Ni and Mg is negligible, thus providing a relatively pure Co stream (in the loaded organic), in the absence of Mn, Fe, Cu or Zn (all of which can co-extract with Co). ","Co extraction is kept deliberately less than 100%, to ensure that the loaded organic (loaded organic) is fully loaded with Co, thus minimizing co-extraction of Mg and Ni, (which are less strongly extracted than Co). ","Even then, some scrubbing of loaded organic is required to remove the small amounts of Mg and Ni that are extracted. ","Scrub feed is derived from a fraction of the (pure) cobalt strip liquor, which is in limited supply, since the Ni:Co ratio in the solution is typically >10:1; so minimizing of scrubbing requirements is essential.","\nCo is then stripped from the loaded organic in conventional fashion with dilute sulphuric acid solution to form a concentrated and pure Co solution, (low in Mg and Ni), and then recovered from this strip solution by conventional electrowinning (as pure metallic cathode), or by precipitation with some suitable reagent (e.g. sodium carbonate) as a pure Co salt, carbonate or hydroxide, etc.","\nCyanex 272 is applied as an extractant again at pH 7.0-7.5 to the Co raffinate, to recover the residual Co, (about 10% of feed Co in ammonium sulphate solution), and also to remove any Mg and Ca from this solution prior to Ni recovery. ","This is called the magnesium extraction stage for sake of reference. ","About 10% of feed Ni is also extracted here into the loaded organic, leaving about 90% of feed Ni in raffinate from this operation. ","Stripping of the loaded organic stream with acid produces an acidic aqueous stream which is recycled to the leach circuit for recovery of Ni/Co values. ","Co in raffinate is very low, (˜1 ppm [Co]), in order to produce high purity Ni in the next step.","\nNi is extracted from Mg raffinate with LIX™ 84 extractant at about pH 7.0-7.5, as in Reaction (3);Ni(NH3)2SO4+2RH (organic reagent)→NiR2 (organic phase)+(NH4)2SO4 (3)\nThe Ni extraction is followed by acidic stripping of the loaded organic, to produce a pure Ni electrolyte, (4), and recovery of Ni metal as cathodes by conventional electrowinning, reaction (5):NiR2 (organic phase)+H2SO4→2RH (organic phase)+H2SO4+H2O (4)NiSO4+H2O→Ni0↓+H2SO4+½O2 (5)\nThe final Ni raffinate is recycled to the original ammonium sulphate leach, completing the circuit.","\nIt is to be noticed that the overall reaction, i.e. combining leaching of Ni hydroxide, solvent extraction, solvent stripping and electrowinning, reaction (6), has no reagent consumed and no byproducts, other than water and oxygen:Ni(OH)2→Ni0↓+H2O+½O2 (6)\nNumerous other steps, (e.g. washing, scrubbing and stripping), are combined with each of the three main extractions, i.e. Co, Mg and Ni. ","Altogether about 40 individual mixer-settlers are used, making for quite a complicated and expensive process for Co removal, hence the incentive to make it simpler.","\nFinally it is worth emphasizing that the Co extraction by solvent extraction in U.S. Pat. ","No. ","6,171,564 is only performed after first precipitating a mixed hydroxide, and then re-leaching this solid.","\nIn case it might be wondered why this sequence is required, it is our contention that Co extraction by solvent extraction is quite inefficient if such precipitation/re-leach is not carried out, due to the impurities present in the feed liquor to precipitation.","\nIn other words the Co solvent extraction with Cyanex 272 when applied to the (acidic) feed liquor to this precipitation is inefficient as it contains too many interfering impurities, particularly Mg and Mn; both of these impurities compete with Co in the acidic solutions.","\nEffectively this means that the hydroxide precipitate has to stay as a mixed hydroxide, containing both Ni and Co, as well as Mg and Mn, which limits its marketability in practice. ","It is worth noting that most Ni refineries now use Cyanex 272 for separating Co from Ni, so feed materials to these refineries are usually restricted to low Mg and low Mn materials. ","In practice, this means feed materials to Ni refineries are currently either Ni mattes or mixed sulphides, not mixed hydroxides or concentrates; hence the marketability for mixed hydroxide has not been established so far, and represents a significant uncertainty for any mine project that depends on selling such a product at a good price.","\nReference is also made to patent applications WO 02/22896 A1; WO 02/22897 A1; WO 2005/073415 A1; WO 2005/073416 A1 and WO 2006/032097 A1 of the Commonwealth Scientific and Industrial Research Organisation (CSIRO) which has been engaged for some years in researching the field known as Synergistic Solvent Extraction (SSX). ","This technique makes use of two or more extractants combined together to achieve beneficial effects superior to those of the individual extractants.","\nCo and/or Ni extraction from solution is the subject of a number of these patent applications, but generally they are extracted together from other impurities. ","The concept of trying to separate Ni from Co is evidently not contemplated in any of these patent applications.","\nAlso, these patent applications do not contemplate trying to take advantage of kinetic differences between Ni and Co in extraction, which is an important and unusual feature of the present invention, i.e. unusual in solvent extraction.","\nRather, extraction efficiencies in these prior applications by CSIRO are generally based on steady-state results, i.e. results which approach equilibrium, (the normal situation in solvent extraction).","\nPatent Application WO 2005/073415 discloses a process for selectively extracting Co and/or Mn from leach solutions containing Mg, Ca (and possibly Mn), using a combination of two organic extractants. ","This combination is made up of a carboxylic acid such as Versatic™ 10 (2-methyl, 2-ethyl heptanoic acid) and a hydroxyoxime such as LIX™ 63 (5,8-diethyl-7-hydroxy-6-dodecanone oxime).","\nThe extraction process with this blend has superior selectivity possibilities for Co, Ni and Mn over the impurities mentioned, compared to extraction with Versatic 10 alone.","\nThis improvement is expressed as a downward (synergistic) shift in the isotherm for Co, Ni and Mn (the pH50 is reduced by 1-3 pH units). ","Cu and Zn behave similarly (synergistic shift), whereas Mg and Ca behaved in the opposite sense, i.e. antagonistic shifts to higher pH50.","\nTaken together, this picture indicates improved separation possibilities for Co, Mn, Ni, Cu and Zn from Mg and Ca. ","However, it is noted that extraction of Ni with this organic combination is relatively slow compared to Co and Mn; Example 2 and FIG. ","3 indicate that 10 minutes extraction is needed to get even 85% Ni extraction, (compared to <1 minute for Co and Zn), whereas the isotherm (where steady state conditions apply) indicates almost quantitative Ni extraction is possible at say pH 5. ","The implications are that the Ni extraction kinetics aren't fast enough to allow for a practical process for Ni extraction, and thus the focus is primarily on Co and/or Mn extraction.","\nStripping of Mn and Co from the loaded organic (LO) is accomplished quickly with dilute acid, presumably at ambient temperatures (not specified though).","\nConsidering the overall process, (extraction plus scrubbing and stripping), Co can be extracted together with Mn from a leach solution, and thus separated from Mg and Ca; alternatively Co can be extracted preferentially from Mn as well, presumably by operating at a lower pH. Small concentrations of Mn can also be scrubbed from the LO by Co if desired, (presumably this only works if Mn extraction is modest compared to Co loading).","\nAs explained above, Ni extraction with this system is not attractive, as the Ni extraction kinetics are too slow to be useful, even though the Ni isotherm is similar to that of Co. Some Ni will extract inevitably though if present in the feed solution, and has to be stripped with Co or separated out subsequent to stripping. ","So Ni is more of a nuisance to a Co purification process, if anything. ","If present, Cu and Zn also extract in a similar fashion to Co, and must be separated out by selective stripping or in subsequent steps on the strip product stream.","\nThus this process is particularly aimed at Co extraction away from common leach liquor impurities, particularly Mg and Ca, where the Co is the only metal of interest (i.e. Cu, Zn and Ni are missing or in minor concentrations), and is not particularly attractive for solutions that contain high Ni as well as Co.\nPatent Application WO 2005/073416 is particularly aimed at Co and/or Ni extraction away from common leach liquor impurities, particularly Mn, Mg and Ca. ","It uses a similar organic mixture as WO 2005/073415, e.g. Versatic 10 and LIX 63, except that a 3rd component is added, a so-called kinetic accelerator like TBP.","\nThis 3rd component literally accelerates the extraction of Ni, so that both Ni and Co are extracted together, and thus compensates for the perceived slow extraction kinetics of Ni. ","It also accelerates the stripping of Ni from the organic.","\nThe benefits of the synergistic system together with the accelerator are described in Examples 1-8, and shown in FIGS. ","4-9, 11 and 12.","\nThe process has several embodiments, distinguished largely by the design of the stripping circuit, to separate Ni from Co, after the two metals have been co-extracted into the organic phase. ","Co strips more easily than Ni, so selective stripping is an option for separating the two metals, using mild conditions, e.g. with dilute acid or at higher pH.\nThus in Option 1 (page 13), Co is selectively stripped from the loaded organic, leaving the Ni behind for later stripping under more severe conditions. ","This option is shown as flowsheets in FIGS. ","1-3, and described in Examples 9 and 10.","\nIn Option 2 (page 16), Co and Ni are stripped together, and then the strip product liquor containing both metals (but notably free from Mg) is then subjected to a 2nd extraction, typically using Cyanex 272, which is selective for Co over Ni, (as noted above) in the absence of Mg and other metals. ","This option is described in Example 11, and shown in FIG. ","10.","\nVarious complications in both options arise with other metals, e.g. Cu, Mn and Zn, which co-extract with Co and Ni, and have to be subsequently separated out during stripping, or by scrubbing, from Co and Ni.","\nIn none of the examples shown, nor in the text or claims, is Co separated from the Ni in the solution by selective extraction, as in the present invention."],"string":"[\n \"Properties of Cobalt and Nickel in Aqueous Solution\\nCobalt and nickel have very similar chemical properties. \",\n \"In aqueous solution both elements are normally found as divalent cations (e.g. Co++ or Ni++) in acid solution, with similar solubilities.\",\n \"\\nBoth are soluble as the respective sulphates, chlorides, or nitrates in acid solution, but are largely insoluble in alkaline conditions unless chelating agents are present. (\",\n \"Both cations are chelated strongly by ammonia, for example). \",\n \"Their sulphide compounds have similar properties, (the KSP values are similar leading to a similar pH of formation with S2− ions), as do their respective carbonates.\",\n \"\\nThis phenomenon presents an ongoing problem for the extractive metallurgist, as Co and Ni are invariably found together in naturally occurring ores, but must ultimately be separated to make maximum use of each metal. \",\n \"Fortunately however, there are exceptions to this pattern of similar behavior, which can be exploited, and will be discussed below.\",\n \"\\nRatio of Cobalt to Nickel Occurring Naturally in Nickel Ores\\nNi and Co commonly occur together in nature as sulphide ore deposits, and the ratio of Co:Ni in Ni ores is surprisingly constant in the range of about 1:15 up to 1:30. \",\n \"This is true at least in unaltered sulphide ores; although this ratio can be quite different if weathering of the ores has occurred, (over many millennia),\\nA general review of nickel metallurgy is to be found in the excellent book “The Winning of Nickel”, by Joseph P. Boldt Jr., and Paul Queneau Sr., \",\n \"published by Methuen and Co. 1967. \",\n \"A more recent review of laterites in particular is found in “The Past and Future of Nickel Laterites,” by Ashok Dalvi, Gordon Bacon, and Robert Osborne in: PDAC 2004 International Convention, Trade Show and Investors' Exchange, (Mar. 7-10, 2004).\",\n \"\\nWeathering of surface Ni deposits is common especially in tropical countries, and such deposits are usually referred to as Ni laterites; due to slight differences in chemistry, this weathering frequently results in a partial separation of Ni and Co over a vertical horizon, compared to the original sulphide ore. \",\n \"Some concentration of Co into the so-called limonite layer often is the result, so Co:Ni ratios in laterites considered for hydrometallurgical processing vary substantially from the usual ratio in sulphides, e.g. a ratio of 1:10 or even lower may be found in limonite.\",\n \"\\nCo Separation from Nickel in a Leach Solution . . . . \",\n \"Overview\\nThe distribution of Co and Ni in most leaching processes is very similar. \",\n \"Thus leaching of Ni—Co ores or concentrates usually results in a mixed solution of Co and Ni, as well as other materials.\",\n \"\\nHowever, Ni and Co have to be separated eventually to obtain maximum use and payment for each element, as their end-use is significantly different, e.g. different metal alloys. \",\n \"With only a few notable exceptions, Ni is much more abundant in ores or concentrates than Co. Thus in a mixed Ni—Co solution, the problem of separation can be more accurately stated as separating Co (as an impurity, albeit of value) from a Ni solution. \",\n \"It also happens that Co has a few specific chemical properties that allow for its selective extraction from a mixture of elements in solution, whereas Ni in general does not have such properties.\",\n \"\\nA variety of processes have been (and some still are) used commercially to achieve this objective, but all of them have significant costs, and it is the objective of the present invention to provide a more efficient and more cost-effective method.\",\n \"\\nAlso, because of the greater value of Co, this need to purify the Ni solution of Co should not obscure the secondary need to also recover Co itself in an economic manner, which is part of the present invention.\",\n \"\\nA number of processes have been used commercially for Co separation from Ni, for example:\\nPrecipitation of Co from Ni—Co Solution as Co(OH)3 \\nThis is an old process, (see the above-referenced book by Boldt and Queneau), one of the first known methods, and still used commercially. \",\n \"With strong oxidants, a Co++ solution can readily be oxidized to Co+++, which is essentially insoluble in dilute acid solution (say pH 2-6). \",\n \"Co is thus precipitated as Co(OH)3 whilst the Ni stays largely in solution. \",\n \"Oxidants used for this purpose include Cl2 and ozone. \",\n \"Electro-oxidation can also be used. \",\n \"However, the process is costly and inefficient, due to significant co-oxidation of Ni++ to a similar product, and has generally fallen out of favour.\",\n \"\\nSelective Solvent Extraction (SX) of Co from Ni—Co Solution\\nThis approach has been the subject of many investigations, some of which have been commercialized, and some of these are listed in the referenced article, “Cobalt-Nickel Separation in Hydrometallurgy: a Review,” by Douglas S. Flett, in: Chemistry for Sustainable Development 12 (2004), pages 81-91. \",\n \"There are some organic extractants which will selectively extract Co with respect to Ni. \",\n \"Primarily these are one of two types:\\ni) Ternary and quaternary amines (Alamine™ 336 for example), which can extract some metal chloride complexes (e.g. CoCl42−) from a strong chloride aqueous environment. \",\n \"Unusually, Ni doesn't form such chloride complexes, so a good separation of Ni from other elements can sometimes be achieved. \",\n \"However, the requirement of the strong chloride concentration (several molar) severely limits the applicability of the process, and in reality omits it from serious consideration for a typical leach liquor.\",\n \"\\nii) Phosphinic acids (e.g. bis 2,4,4-trimethylpentyl phosphinic acid, sold commercially as Cyanex™ 272), which will extract Co selectively over Ni, without the need for a chelating agent as in the amines. \",\n \"Although this extractant works well in pure solutions, unfortunately it also extracts many other metals commonly found in leach solutions, such as Mg and Mn, which limits its usefulness. \",\n \"This limitation is illustrated in the first two Examples described below. \",\n \"Although Mg can be scrubbed off the loaded organic stream by Ni/Co (with difficulty), by using a large number of mixer/settlers in counter-current mode, as was done at the Bulong plant (described by Donegan (“Direct Solvent Extraction of Nickel at Bulong Operations,” by S. Donegan, in: Minerals Engineering 19 (2006), pages 1234-1245), Mn cannot be scrubbed off. \",\n \"The only remedy is to co-extract all the Mn along with the Co, and pay for the cost of the Mn extraction/stripping, particularly the cost of the ammonia used for neutralization of the organic extractant. \",\n \"As a result of this limitation, Cyanex 272 is best applied after some prior purification, which itself is both costly and inefficient.\",\n \"\\nSelective SX of Ni from Ni—Co Solution\\nThis approach was invented and commercialized at the Queensland Nickel (QNI) plant in Yabulu, Queensland, Australia, very successfully in the 80's, and is well summarized by the above-referenced Flett review article, and also by Reid and Price.\",\n \"\\n(Reid, J G and Price, M J, 1993. \",\n \"Ammoniacal solvent extraction at Queensland Nickel: Process installation and operation, in Solvent Extraction in the Process Industries Volume 1 (Proceedings of International Solvent Extraction Conference 1993) (eds: D H Logsdail and M J Slater), pp 225-231 (Elsevier Applied Science: London and New York.\",\n \"\\nThe process is effective but suffers from high cost, as the major component (Ni), is being extracted away from the ‘impurity’ (Co), generally a more expensive route than the opposite. \",\n \"The impurities are all left with the Co.\\nAlso the extractant used (hydroxyoxime) is prone to rapid degradation by Co II oxidation, and hence must be re-oximated on a regular basis, at considerable cost. \",\n \"Pre-oxidation of Co II to Co III is necessary to minimize this problem, but is not 100% effective, leading to continuous re-oximation of the extractant, at high cost.\",\n \"\\nStripping of the Ni from the loaded organic can be done with either strong ammonia solutions (250 g/l NH3), or by acid, as was done at the Cawse mine in Western Australia for a while, as discussed by Flett (referenced above). \",\n \"The former fits in well with NiCO3 production, (by steam stripping of NH3), the latter with a Ni electrowinning flowsheet.\",\n \"\\nAlthough technically feasible, this approach is relatively expensive as noted, and does not produce a pure Co product, as the Ni left in the raffinate produces a Ni:Co ratio in this stream of at least 1:1. \",\n \"At Yabulu, a separate Co refinery had to be built eventually for re-processing of the Co-rich stream, and this refinery had its own technical and financial challenges.\",\n \"\\nHydrogen Reduction of Ni from Ni—Co Solution\\nThis approach was first commercialized in about 1950 at the Sherritt Gordon plant in Fort Saskatchewan, Alberta, as described by Boldt et al. \",\n \"The method has been considered the standard process for nickel recovery by some designers; it has been installed in several other nickel plants since, but suffers from significant drawbacks: Batch mode operation. \",\n \"The process apparently can only be operated in this way, (instead of the usual continuous mode). \",\n \"This then requires multiple units (autoclaves), with low operating time (need to fill and discharge each batch autoclave frequently) These features lead to high capital and operating costs Heightened safety and occupational health requirements Need for concentrated Ni solution (50-100 g/l [Ni]), and high solution feed temperatures, approx 200° C., again leading to high costs. \",\n \" Need for careful control of pH, in pH 7.0 range, with high background levels of ammonium sulphate (200 g/l). \",\n \" Large by-product production of ammonium sulphate crystals, at about 7× tonnage of Ni metal production, necessitating evaporative crystallizers, filters, dryers, bagging, storage facilities, etc. \",\n \"All leading to high costs. \",\n \" Technically complex, thus requiring high level of technical skill, and expensive engineering input from a very limited number of qualified suppliers Further processing costs, downstream from the actual hydrogen reduction due to need for further purification to remove trace amounts of impurities such as S and O. High temperature oxidation and reduction furnaces are needed for this purification. \",\n \" Relatively poor quality of Ni product, regarding Co content Poor quality of Co product, as the raffinate contains a Ni:Co ratio of about 1:1, leading to need for another Co refining step, similar to the process described in previous section.\",\n \"Difficulties with Separation of Cobalt from Nickel in the Presence of Impurities \\nAs described in the previous section, Co separation from Ni is difficult, and specific to each situation, e.g. solution chemistry and particularly the impurities in the Co—Ni solution. \",\n \"For solutions derived from leaching sulphide concentrates (as at Sherritt Gordon, for example), impurities are generally confined to other base metals such as Fe, Cu and Zn, which can be removed efficiently by known purification methods.\",\n \"\\nHowever, for acidic solutions derived from leaching of laterite ores, other impurities are found, particularly Mg and Mn, and often in much greater concentrations relative to the Ni and Co concentrations, e.g. as much as 10× greater. \",\n \"This situation makes it near difficult to use the preferred Cyanex 272 Co extraction method described above without some form of pre-treatment to separate Co and Ni from these impurities, or alternatively pay for the expense of co-extracting Mn.\",\n \"\\nThus, unless Mn extraction is to be tolerated and paid for, treatment of laterite leach liquors is usually required to choose one of two routes: Precipitation of Ni and Co in acid solution away from impurities as much as possible, followed by re-leaching to form a new solution with reduced impurity content. \",\n \"This approach for example was followed in the Murrin plant, which is described by Campbell et al in U.S. Pat. \",\n \"No. \",\n \"7,387,767, and also in the Cawse plant, described by White in U.S. Pat. \",\n \"No. \",\n \"6,409,979. \",\n \" Leach in an ammoniacal alkaline environment, wherein most of damaging impurities are largely absent. \",\n \"This approach is adopted by the Caron process, for example (described in Boldt and Queneau), which was used at the QNI plant in Yabulu mentioned above, (now under different ownership and renamed). \",\n \" \\nThe Caron process requires a pretreatment process of its own, a reductive roast at high temperature. \",\n \"This is a pyrometallurgical process, and requires high capital investment. \",\n \"It also has high energy requirements and thus has high operating costs. \",\n \"For these reasons, it is generally not considered today, although a few plants built years ago are still operating.\",\n \"\\nPractically then, one is confined to the precipitation and releach option as a pre-treatment prior to Co—Ni separation.\",\n \"\\nFor laterite ores therefore, it is desirable, even necessary, that the Mn/Mg be separated out from Ni/Co by first precipitating the Ni/Co from solution, and then releaching. \",\n \"This is usually done by one of two methods: 1. \",\n \"H2S precipitation of mixed Ni/Co sulphides, (which selectively precipitates Ni/Co over Mn/Mg), followed by filtration and then pressure oxidation of mixed sulphides precipitate, with associated filtration steps, to produce a Ni/Co solution suitable for efficient Cyanex 272 extraction of Co, (as is now done at Murrin Murrin, op cit), or 2. \",\n \"Mixed hydroxide precipitation of Ni/Co with MgO (which can be done selectively over Mn and Mg, as practiced at Cawse plant for example, and patented by White, op cit), or with CaO, which is not so selective with respect to Mg/Mn. \",\n \"At Cawse, this was followed by re-leaching of mixed hydroxides with ammonium carbonate solution, filtering, then steam stripping the NH3/CO2 from the leach liquor to precipitate Mn/Mg, (and re-adsorbing the same NH3/CO2), and re-filtering. \",\n \" \\nEither of these processes for Mn/Mg rejection is expensive, especially in capital costs (H2S generating plant, or stripping and absorption plants for NH3/CO2). \",\n \"It is an objective of the present invention to be able to treat high Mn/Mg solutions containing both Ni and Co, and separate Co from this solution, without going through either of the existing Mn/Mg rejection alternatives sketched out above.\",\n \"\\nUnfortunately, a large amount of gypsum is formed along with the mixed Ni—Co hydroxide precipitate (MHP) when slaked lime is used as the precipitant for Ni and Co; consequently the MHP contains about 50 wt % gypsum, and only 50 wt % actual Ni and Co hydroxides, (and hence about 22% Ni).\",\n \"\\nAlso both Mg and Mn are partly precipitated from solution (as hydroxides) at about the same pH as Ni and Co, thus further contaminating the product. \",\n \"This is a particular problem for laterites where these impurities are usually present in high concentration, e.g. in leach liquors derived from laterites by a High Pressure Acid Leach (HPAL) process.\",\n \"\\nMn is of special interest as well because MHP is of course a mixture of Ni and Co compounds, which eventually have to be separated to make commercial Ni and Co products. \",\n \"The conventional technology for this separation is to use solvent extraction on a Ni/Co solution, in particular the extractant Cyanex 272. \",\n \"This Cyanex 272 separation is only feasible if Mn and Mg are very low in the feed solution, otherwise they interfere with the Co extraction. \",\n \"Generally this limits such refining to feed materials that are already low in Mn: Ni sulphide concentrates generally fall into this category, or are smelted to matte anyway, which is an effective Mn removal step, (into the slag). \",\n \"For feed materials that have not been smelted, e.g. laterite high pressure acid leach liquors, a significant Mn presence may be a serious impediment to further processing.\",\n \"\\nCommercial Value of Nickel Hydroxide Products\\nMixed Ni—Co hydroxide (MHP) has been produced by at least one Ni mine in the recent past, and several announced projects have included this intermediate in the process flowsheet. \",\n \"However, this product has uncertain market value and a limited marketing history, due in part to its purity and grade. \",\n \"Since Ni and Co must be separated eventually, the presence of other impurities in the MHP can be a serious impediment to said separation, as described in the previous section.\",\n \"\\nIf slaked lime, (Ca(OH)2), is used as the reagent, it typically precipitates some Mg and Mn from solution along with Ni and Co; and if any traces of base metal impurities, (e.g. Cu, Fe, Zn and Cd), are left in solution from the prior purification, they are also precipitated into the MHP. \",\n \"In addition, gypsum is formed of course, thus degrading the Ni grade of product by about 50%. \",\n \"If MgO is used instead of slaked lime, better selectivity is found in respect to Mg, and of course no gypsum is formed, so the Ni grade is much better, but most of the same impurity issues remain.\",\n \"\\nAll of the above can affect on the marketing of the MHP, and hence its commercial value. \",\n \"Nevertheless for projects with limited Ni/Co production it may be advantageous to be able to sell the MHP as an intermediate product, and thus avoid the extra cost of full refining to metal products on a small scale. \",\n \"It was of some importance therefore to improve the quality of MHP, by Co separation upstream.\",\n \"\\nTherefore if the Co is separated out before the precipitation process, the resultant Ni Hydroxide Product (NHP) may have enhanced value.\",\n \"\\nU.S. Pat. \",\n \"No. \",\n \"6,171,564 relates to a process for treatment of nickel ores and concentrates to recover both Ni and Co as refined metals. \",\n \"It is a ‘comprehensive’ process in the sense that: a) Both sulphides and oxides (laterites) are considered as suitable feeds, and b) The process describes a complete flowsheet going all the way to metal product: Acid leaching of solid feed to produce an acidic leach solution, containing Ni, Co and numerous impurities purification of leach solution, in several steps, including solvent extraction precipitation of Ni and Co together as an impure mixed hydroxide by neutralizing acidic solution Releaching of mixed hydroxide in (recycled) ammoniacal solution to redissolve Ni and Co values Separation of Co from Ni in said solution by solvent extraction, followed by stripping and recovery of Co product Further purification of (ammoniacal) raffinate from Co solvent extraction by additional solvent extraction steps Extraction of Ni from purified ammoniacal solution, followed by acidic stripping of organic stream to form purified acidic Ni solution Ni recovery from purified solution by electrowinning, with recycling of spent acid to solvent extraction \\nThe Ni and Co content in the feed material are first leached by pressure oxidation (in the case of sulphides) or by acid pressure leaching (in the case of laterites); then the solution is purified to remove primarily Cu, Zn and Fe. \",\n \"From the purified solution, Ni and Co are precipitated together at about pH 7-8, using slaked lime, as a mixture of Ni and Co hydroxides, (MHP).\",\n \"\\nMHP is then re-leached in mild conditions, (ambient temperature, dilute solids, neutral pH) with a strong ammonium sulphate solution (200 g/l) at about pH 7.0, as in Reaction (1):Ni(OH)2+(NH4)2SO4→Ni(NH3)2SO4+2H2O (1)\\nThus this leach produces a solution of Ni and Co diammine, (Ni(NH3)2++ and Co(NH3)2++ ions), which also contains some impurities, notably Mg and Ca.\",\n \"\\nThe leaching of Ni and Co by this method is not very efficient, (about 90%), due to the mild conditions selected, i.e. the neutral pH and hence very low free ammonia content of the leach solution; almost none of the Ni species in solution is present as free ammonia, NH3. \",\n \"As a consequence, significant Ni and Co are left behind in the residue, which therefore has to be releached to avoid unacceptable losses. \",\n \"However, the choice of the neutral pH is very important to enable the subsequent solvent extraction steps to proceed efficiently.\",\n \"\\nCo is then extracted selectively from this impure Ni/Co diammine solution using as extractant the Cyanex 272 reagent at about this same pH 7.0, leaving Ni in the raffinate.\",\n \"\\nSince the extraction is from a diammine, (i.e. Co(NH3)2SO4), no neutralization is required to maintain a constant pH, as the ammine is simultaneously converted to ammonia (NH3) during the extraction, which exactly balances the acid production (H+ ions) from the organic reagent, and thus produces ammonium sulphate in the overall extraction reaction (2):Co(NH3)2SO4+2RH (organic reagent)→CoR2 (organic phase)+(NH4)2SO4 (2)\\nThus the pH stays almost constant throughout the Co extraction, negating the usual need for neutralizing agent. \",\n \"This is an unusual and most beneficial feature of this solvent extraction process, as most other Co and Ni solvent extraction processes need in situ neutralization with ammonia or caustic to counteract acid production, and thus maintain the solution pH within the required range during the reaction, (or else the extraction stops prematurely). \",\n \"The significance of the neutralization goes far beyond the simple avoidance of reagent consumption; the normal byproduct of such neutralization with ammonia or caustic is a salt such as ammonium sulphate or sodium sulphate, which rapidly accumulates in the raffinate stream, and must be disposed of in some fashion. \",\n \"This is a serious challenge, given the constraints of the system, such as metal contamination of said salt as a potential byproduct, and is sometimes fatal to a process design.\",\n \"\\nCo extraction at this point is only about 90% of the Co contained in the diammine solution, and co-extraction of Ni and Mg is negligible, thus providing a relatively pure Co stream (in the loaded organic), in the absence of Mn, Fe, Cu or Zn (all of which can co-extract with Co). \",\n \"Co extraction is kept deliberately less than 100%, to ensure that the loaded organic (loaded organic) is fully loaded with Co, thus minimizing co-extraction of Mg and Ni, (which are less strongly extracted than Co). \",\n \"Even then, some scrubbing of loaded organic is required to remove the small amounts of Mg and Ni that are extracted. \",\n \"Scrub feed is derived from a fraction of the (pure) cobalt strip liquor, which is in limited supply, since the Ni:Co ratio in the solution is typically >10:1; so minimizing of scrubbing requirements is essential.\",\n \"\\nCo is then stripped from the loaded organic in conventional fashion with dilute sulphuric acid solution to form a concentrated and pure Co solution, (low in Mg and Ni), and then recovered from this strip solution by conventional electrowinning (as pure metallic cathode), or by precipitation with some suitable reagent (e.g. sodium carbonate) as a pure Co salt, carbonate or hydroxide, etc.\",\n \"\\nCyanex 272 is applied as an extractant again at pH 7.0-7.5 to the Co raffinate, to recover the residual Co, (about 10% of feed Co in ammonium sulphate solution), and also to remove any Mg and Ca from this solution prior to Ni recovery. \",\n \"This is called the magnesium extraction stage for sake of reference. \",\n \"About 10% of feed Ni is also extracted here into the loaded organic, leaving about 90% of feed Ni in raffinate from this operation. \",\n \"Stripping of the loaded organic stream with acid produces an acidic aqueous stream which is recycled to the leach circuit for recovery of Ni/Co values. \",\n \"Co in raffinate is very low, (˜1 ppm [Co]), in order to produce high purity Ni in the next step.\",\n \"\\nNi is extracted from Mg raffinate with LIX™ 84 extractant at about pH 7.0-7.5, as in Reaction (3);Ni(NH3)2SO4+2RH (organic reagent)→NiR2 (organic phase)+(NH4)2SO4 (3)\\nThe Ni extraction is followed by acidic stripping of the loaded organic, to produce a pure Ni electrolyte, (4), and recovery of Ni metal as cathodes by conventional electrowinning, reaction (5):NiR2 (organic phase)+H2SO4→2RH (organic phase)+H2SO4+H2O (4)NiSO4+H2O→Ni0↓+H2SO4+½O2 (5)\\nThe final Ni raffinate is recycled to the original ammonium sulphate leach, completing the circuit.\",\n \"\\nIt is to be noticed that the overall reaction, i.e. combining leaching of Ni hydroxide, solvent extraction, solvent stripping and electrowinning, reaction (6), has no reagent consumed and no byproducts, other than water and oxygen:Ni(OH)2→Ni0↓+H2O+½O2 (6)\\nNumerous other steps, (e.g. washing, scrubbing and stripping), are combined with each of the three main extractions, i.e. Co, Mg and Ni. \",\n \"Altogether about 40 individual mixer-settlers are used, making for quite a complicated and expensive process for Co removal, hence the incentive to make it simpler.\",\n \"\\nFinally it is worth emphasizing that the Co extraction by solvent extraction in U.S. Pat. \",\n \"No. \",\n \"6,171,564 is only performed after first precipitating a mixed hydroxide, and then re-leaching this solid.\",\n \"\\nIn case it might be wondered why this sequence is required, it is our contention that Co extraction by solvent extraction is quite inefficient if such precipitation/re-leach is not carried out, due to the impurities present in the feed liquor to precipitation.\",\n \"\\nIn other words the Co solvent extraction with Cyanex 272 when applied to the (acidic) feed liquor to this precipitation is inefficient as it contains too many interfering impurities, particularly Mg and Mn; both of these impurities compete with Co in the acidic solutions.\",\n \"\\nEffectively this means that the hydroxide precipitate has to stay as a mixed hydroxide, containing both Ni and Co, as well as Mg and Mn, which limits its marketability in practice. \",\n \"It is worth noting that most Ni refineries now use Cyanex 272 for separating Co from Ni, so feed materials to these refineries are usually restricted to low Mg and low Mn materials. \",\n \"In practice, this means feed materials to Ni refineries are currently either Ni mattes or mixed sulphides, not mixed hydroxides or concentrates; hence the marketability for mixed hydroxide has not been established so far, and represents a significant uncertainty for any mine project that depends on selling such a product at a good price.\",\n \"\\nReference is also made to patent applications WO 02/22896 A1; WO 02/22897 A1; WO 2005/073415 A1; WO 2005/073416 A1 and WO 2006/032097 A1 of the Commonwealth Scientific and Industrial Research Organisation (CSIRO) which has been engaged for some years in researching the field known as Synergistic Solvent Extraction (SSX). \",\n \"This technique makes use of two or more extractants combined together to achieve beneficial effects superior to those of the individual extractants.\",\n \"\\nCo and/or Ni extraction from solution is the subject of a number of these patent applications, but generally they are extracted together from other impurities. \",\n \"The concept of trying to separate Ni from Co is evidently not contemplated in any of these patent applications.\",\n \"\\nAlso, these patent applications do not contemplate trying to take advantage of kinetic differences between Ni and Co in extraction, which is an important and unusual feature of the present invention, i.e. unusual in solvent extraction.\",\n \"\\nRather, extraction efficiencies in these prior applications by CSIRO are generally based on steady-state results, i.e. results which approach equilibrium, (the normal situation in solvent extraction).\",\n \"\\nPatent Application WO 2005/073415 discloses a process for selectively extracting Co and/or Mn from leach solutions containing Mg, Ca (and possibly Mn), using a combination of two organic extractants. \",\n \"This combination is made up of a carboxylic acid such as Versatic™ 10 (2-methyl, 2-ethyl heptanoic acid) and a hydroxyoxime such as LIX™ 63 (5,8-diethyl-7-hydroxy-6-dodecanone oxime).\",\n \"\\nThe extraction process with this blend has superior selectivity possibilities for Co, Ni and Mn over the impurities mentioned, compared to extraction with Versatic 10 alone.\",\n \"\\nThis improvement is expressed as a downward (synergistic) shift in the isotherm for Co, Ni and Mn (the pH50 is reduced by 1-3 pH units). \",\n \"Cu and Zn behave similarly (synergistic shift), whereas Mg and Ca behaved in the opposite sense, i.e. antagonistic shifts to higher pH50.\",\n \"\\nTaken together, this picture indicates improved separation possibilities for Co, Mn, Ni, Cu and Zn from Mg and Ca. \",\n \"However, it is noted that extraction of Ni with this organic combination is relatively slow compared to Co and Mn; Example 2 and FIG. \",\n \"3 indicate that 10 minutes extraction is needed to get even 85% Ni extraction, (compared to <1 minute for Co and Zn), whereas the isotherm (where steady state conditions apply) indicates almost quantitative Ni extraction is possible at say pH 5. \",\n \"The implications are that the Ni extraction kinetics aren't fast enough to allow for a practical process for Ni extraction, and thus the focus is primarily on Co and/or Mn extraction.\",\n \"\\nStripping of Mn and Co from the loaded organic (LO) is accomplished quickly with dilute acid, presumably at ambient temperatures (not specified though).\",\n \"\\nConsidering the overall process, (extraction plus scrubbing and stripping), Co can be extracted together with Mn from a leach solution, and thus separated from Mg and Ca; alternatively Co can be extracted preferentially from Mn as well, presumably by operating at a lower pH. Small concentrations of Mn can also be scrubbed from the LO by Co if desired, (presumably this only works if Mn extraction is modest compared to Co loading).\",\n \"\\nAs explained above, Ni extraction with this system is not attractive, as the Ni extraction kinetics are too slow to be useful, even though the Ni isotherm is similar to that of Co. Some Ni will extract inevitably though if present in the feed solution, and has to be stripped with Co or separated out subsequent to stripping. \",\n \"So Ni is more of a nuisance to a Co purification process, if anything. \",\n \"If present, Cu and Zn also extract in a similar fashion to Co, and must be separated out by selective stripping or in subsequent steps on the strip product stream.\",\n \"\\nThus this process is particularly aimed at Co extraction away from common leach liquor impurities, particularly Mg and Ca, where the Co is the only metal of interest (i.e. Cu, Zn and Ni are missing or in minor concentrations), and is not particularly attractive for solutions that contain high Ni as well as Co.\\nPatent Application WO 2005/073416 is particularly aimed at Co and/or Ni extraction away from common leach liquor impurities, particularly Mn, Mg and Ca. \",\n \"It uses a similar organic mixture as WO 2005/073415, e.g. Versatic 10 and LIX 63, except that a 3rd component is added, a so-called kinetic accelerator like TBP.\",\n \"\\nThis 3rd component literally accelerates the extraction of Ni, so that both Ni and Co are extracted together, and thus compensates for the perceived slow extraction kinetics of Ni. \",\n \"It also accelerates the stripping of Ni from the organic.\",\n \"\\nThe benefits of the synergistic system together with the accelerator are described in Examples 1-8, and shown in FIGS. \",\n \"4-9, 11 and 12.\",\n \"\\nThe process has several embodiments, distinguished largely by the design of the stripping circuit, to separate Ni from Co, after the two metals have been co-extracted into the organic phase. \",\n \"Co strips more easily than Ni, so selective stripping is an option for separating the two metals, using mild conditions, e.g. with dilute acid or at higher pH.\\nThus in Option 1 (page 13), Co is selectively stripped from the loaded organic, leaving the Ni behind for later stripping under more severe conditions. \",\n \"This option is shown as flowsheets in FIGS. \",\n \"1-3, and described in Examples 9 and 10.\",\n \"\\nIn Option 2 (page 16), Co and Ni are stripped together, and then the strip product liquor containing both metals (but notably free from Mg) is then subjected to a 2nd extraction, typically using Cyanex 272, which is selective for Co over Ni, (as noted above) in the absence of Mg and other metals. \",\n \"This option is described in Example 11, and shown in FIG. \",\n \"10.\",\n \"\\nVarious complications in both options arise with other metals, e.g. Cu, Mn and Zn, which co-extract with Co and Ni, and have to be subsequently separated out during stripping, or by scrubbing, from Co and Ni.\",\n \"\\nIn none of the examples shown, nor in the text or claims, is Co separated from the Ni in the solution by selective extraction, as in the present invention.\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"USPTO Backgrounds\"\n}"},"scores":{"kind":"list like","value":[0.0006012396770529449,0.0006430022767744958,0.0007894848240539432,0.0008708887035027146,0.0007580640958622098,0.0006394165684469044,0.0005456148646771908,0.0007114486652426422,0.0006886760238558054,0.0006702668615616858,0.0005629915394820273,0.000625224260147661,0.0006800084374845028,0.001063771196641028,0.0005393276805989444,0.0007556532509624958,0.000540397537406534,0.0005862377001903951,0.0006195510504767299,0.0005739778862334788,0.000629554211627692,0.0005505479057319462,0.0008958576363511384,0.0007273323135450482,0.0006137408781796694,0.0005606856429949403,0.000804848677944392,0.0005724456859752536,0.0005484645953401923,0.0005813833558931947,0.0005936670931987464,0.0005939821130596101,0.00089014827972278,0.0006012897356413305,0.0005751327844336629,0.0005898420349694788,0.0007816795841790736,0.0007187609444372356,0.0005804628599435091,0.0007541486411355436,0.0005673373234458268,0.000716374022886157,0.0007334676920436323,0.0006245318800210953,0.000683294259943068,0.0006076142308302224,0.0005939484108239412,0.0006168739637359977,0.0005889185122214258,0.0005963649018667638,0.000577002065256238,0.000664041202981025,0.0006047387723810971,0.0005903203855268657,0.001012116321362555,0.0006082092295400798,0.000700588570907712,0.000606728543061763,0.000736469984985888,0.000614304793998599,0.0007402878836728632,0.0006769567262381315,0.0006132535636425018,0.0013785817427560687,0.0008551131468266249,0.0013785817427560687,0.0011053509078919888,0.0008160340948961675,0.0005693226703442633,0.0006702342070639133,0.0007517840713262558,0.0007675750530324876,0.0005476324004121125,0.0006362485000863671,0.0008219738374464214,0.0006628240225836635,0.0011029242305085063,0.0005770009593106806,0.0008839743677526712,0.0005881820106878877,0.000578445615246892,0.001766564091667533,0.0007033923757262528,0.0008079119143076241,0.0005459945532493293,0.0005602221935987473,0.0006619099876843393,0.001249484485015273,0.0007372015970759094,0.0005526027525775135,0.0005445118877105415,0.0006637982442043722,0.0013372927205637097,0.0053960406221449375,0.0013019255129620433,0.0005448610172607005,0.0006122032646089792,0.0005622073076665401,0.0005418648943305016,0.0010884626535698771,0.0013785817427560687,0.0005927401944063604,0.0007219018298201263,0.0008768268162384629,0.0008248282829299569,0.0007308696513064206,0.0007484700181521475,0.0005094623193144798,0.0014477650402113795,0.0007559438818134367,0.0006011313525959849,0.0007001464255154133,0.0006595181184820831,0.0006690341397188604,0.0006176508613862097,0.0007206646259874105,0.0006499314331449568,0.0008771538850851357,0.0006350374897010624,0.0005502606509253383,0.0006979539757594466,0.0007216472877189517,0.0008010294986888766,0.0007296378607861698,0.0006202972726896405,0.0005827763816341758,0.000587612739764154,0.0013785817427560687,0.0006246705888770521,0.0005663116462528706,0.0006406002212315798,0.0006058342987671494,0.000622313586063683,0.0006884178146719933,0.0005682971677742898,0.0005943428841419518,0.0006013201782479882,0.0006049786461517215,0.0005574586102738976,0.0005961412680335343,0.0006038189749233425,0.0011223144829273224,0.0005443639820441604,0.0005842062528245151,0.000730074301827699,0.0005463319248519838,0.0005467458395287395,0.0005777227343060076,0.0005977764958515763,0.0007262607687152922,0.0005664106574840844,0.0006435307441279292,0.0009435490937903523,0.0006586488452740014,0.0007197195081971586,0.0006494496483355761,0.0006282757385633886,0.0018547518411651254,0.0005440994282253087,0.0007211018237285316,0.0005926585872657597,0.0007828164380043745,0.0005734532023780048,0.0006007312913425267,0.0007322534802369773,0.0005879073869436979,0.0011672148248180747,0.0006774975918233395,0.0006093377596698701],"string":"[\n 0.0006012396770529449,\n 0.0006430022767744958,\n 0.0007894848240539432,\n 0.0008708887035027146,\n 0.0007580640958622098,\n 0.0006394165684469044,\n 0.0005456148646771908,\n 0.0007114486652426422,\n 0.0006886760238558054,\n 0.0006702668615616858,\n 0.0005629915394820273,\n 0.000625224260147661,\n 0.0006800084374845028,\n 0.001063771196641028,\n 0.0005393276805989444,\n 0.0007556532509624958,\n 0.000540397537406534,\n 0.0005862377001903951,\n 0.0006195510504767299,\n 0.0005739778862334788,\n 0.000629554211627692,\n 0.0005505479057319462,\n 0.0008958576363511384,\n 0.0007273323135450482,\n 0.0006137408781796694,\n 0.0005606856429949403,\n 0.000804848677944392,\n 0.0005724456859752536,\n 0.0005484645953401923,\n 0.0005813833558931947,\n 0.0005936670931987464,\n 0.0005939821130596101,\n 0.00089014827972278,\n 0.0006012897356413305,\n 0.0005751327844336629,\n 0.0005898420349694788,\n 0.0007816795841790736,\n 0.0007187609444372356,\n 0.0005804628599435091,\n 0.0007541486411355436,\n 0.0005673373234458268,\n 0.000716374022886157,\n 0.0007334676920436323,\n 0.0006245318800210953,\n 0.000683294259943068,\n 0.0006076142308302224,\n 0.0005939484108239412,\n 0.0006168739637359977,\n 0.0005889185122214258,\n 0.0005963649018667638,\n 0.000577002065256238,\n 0.000664041202981025,\n 0.0006047387723810971,\n 0.0005903203855268657,\n 0.001012116321362555,\n 0.0006082092295400798,\n 0.000700588570907712,\n 0.000606728543061763,\n 0.000736469984985888,\n 0.000614304793998599,\n 0.0007402878836728632,\n 0.0006769567262381315,\n 0.0006132535636425018,\n 0.0013785817427560687,\n 0.0008551131468266249,\n 0.0013785817427560687,\n 0.0011053509078919888,\n 0.0008160340948961675,\n 0.0005693226703442633,\n 0.0006702342070639133,\n 0.0007517840713262558,\n 0.0007675750530324876,\n 0.0005476324004121125,\n 0.0006362485000863671,\n 0.0008219738374464214,\n 0.0006628240225836635,\n 0.0011029242305085063,\n 0.0005770009593106806,\n 0.0008839743677526712,\n 0.0005881820106878877,\n 0.000578445615246892,\n 0.001766564091667533,\n 0.0007033923757262528,\n 0.0008079119143076241,\n 0.0005459945532493293,\n 0.0005602221935987473,\n 0.0006619099876843393,\n 0.001249484485015273,\n 0.0007372015970759094,\n 0.0005526027525775135,\n 0.0005445118877105415,\n 0.0006637982442043722,\n 0.0013372927205637097,\n 0.0053960406221449375,\n 0.0013019255129620433,\n 0.0005448610172607005,\n 0.0006122032646089792,\n 0.0005622073076665401,\n 0.0005418648943305016,\n 0.0010884626535698771,\n 0.0013785817427560687,\n 0.0005927401944063604,\n 0.0007219018298201263,\n 0.0008768268162384629,\n 0.0008248282829299569,\n 0.0007308696513064206,\n 0.0007484700181521475,\n 0.0005094623193144798,\n 0.0014477650402113795,\n 0.0007559438818134367,\n 0.0006011313525959849,\n 0.0007001464255154133,\n 0.0006595181184820831,\n 0.0006690341397188604,\n 0.0006176508613862097,\n 0.0007206646259874105,\n 0.0006499314331449568,\n 0.0008771538850851357,\n 0.0006350374897010624,\n 0.0005502606509253383,\n 0.0006979539757594466,\n 0.0007216472877189517,\n 0.0008010294986888766,\n 0.0007296378607861698,\n 0.0006202972726896405,\n 0.0005827763816341758,\n 0.000587612739764154,\n 0.0013785817427560687,\n 0.0006246705888770521,\n 0.0005663116462528706,\n 0.0006406002212315798,\n 0.0006058342987671494,\n 0.000622313586063683,\n 0.0006884178146719933,\n 0.0005682971677742898,\n 0.0005943428841419518,\n 0.0006013201782479882,\n 0.0006049786461517215,\n 0.0005574586102738976,\n 0.0005961412680335343,\n 0.0006038189749233425,\n 0.0011223144829273224,\n 0.0005443639820441604,\n 0.0005842062528245151,\n 0.000730074301827699,\n 0.0005463319248519838,\n 0.0005467458395287395,\n 0.0005777227343060076,\n 0.0005977764958515763,\n 0.0007262607687152922,\n 0.0005664106574840844,\n 0.0006435307441279292,\n 0.0009435490937903523,\n 0.0006586488452740014,\n 0.0007197195081971586,\n 0.0006494496483355761,\n 0.0006282757385633886,\n 0.0018547518411651254,\n 0.0005440994282253087,\n 0.0007211018237285316,\n 0.0005926585872657597,\n 0.0007828164380043745,\n 0.0005734532023780048,\n 0.0006007312913425267,\n 0.0007322534802369773,\n 0.0005879073869436979,\n 0.0011672148248180747,\n 0.0006774975918233395,\n 0.0006093377596698701\n]"},"avg_score":{"kind":"number","value":0.0007459429766398651,"string":"0.000746"},"num_sents":{"kind":"number","value":169,"string":"169"}}},{"rowIdx":729,"cells":{"texts":{"kind":"list like","value":["The popularity of cloud computing has fuelled a dramatic growth in the number and size of data centers worldwide. ","In such environments, existing networking software and hardware designed for the Internet have shown their limitations. ","A plethora of new design proposals have seen the light recently to address some of the network congestion problems that are intrinsic to data center networks. ","In this spirit we have designed several algorithms and systems and tested them via simulation and/or software deployment in a small scale Data center. ","The goal of this project is to implement some of these mechanisms in the network interface card using the DPDK framework and test them in a small testbed.","\n\nCourse type:\n\nUROP1100\n\nApplicant's Roles:\n\nThe applicant(s) will work with the advisor and graduate students and will be in charge of:\n- studying our proposed algorithms and translating them to the DPDK framework.","\n- Deploying and testing the deployed systems inside our small data center.","\nTo achieve this, the applicant must be a senior CSE or CPEG student with a good knowledge of Computer Networks and Linux Kernel programming\n\nApplicant's Learning Objectives:\n\n- Be able to appreciate the difference between the Internet and data centre networks\n- Be able to appreciate the congestion problems that may arise in data center networks and understand their root causes\n- Be able to appreciate the development cycle of communication protocols\n- Be able to appreciate and code within the DPDK framework\n- Be able to put to practice knowledge learned in Networking, and Linux kernel programming classes"],"string":"[\n \"The popularity of cloud computing has fuelled a dramatic growth in the number and size of data centers worldwide. \",\n \"In such environments, existing networking software and hardware designed for the Internet have shown their limitations. \",\n \"A plethora of new design proposals have seen the light recently to address some of the network congestion problems that are intrinsic to data center networks. \",\n \"In this spirit we have designed several algorithms and systems and tested them via simulation and/or software deployment in a small scale Data center. \",\n \"The goal of this project is to implement some of these mechanisms in the network interface card using the DPDK framework and test them in a small testbed.\",\n \"\\n\\nCourse type:\\n\\nUROP1100\\n\\nApplicant's Roles:\\n\\nThe applicant(s) will work with the advisor and graduate students and will be in charge of:\\n- studying our proposed algorithms and translating them to the DPDK framework.\",\n \"\\n- Deploying and testing the deployed systems inside our small data center.\",\n \"\\nTo achieve this, the applicant must be a senior CSE or CPEG student with a good knowledge of Computer Networks and Linux Kernel programming\\n\\nApplicant's Learning Objectives:\\n\\n- Be able to appreciate the difference between the Internet and data centre networks\\n- Be able to appreciate the congestion problems that may arise in data center networks and understand their root causes\\n- Be able to appreciate the development cycle of communication protocols\\n- Be able to appreciate and code within the DPDK framework\\n- Be able to put to practice knowledge learned in Networking, and Linux kernel programming classes\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"Pile-CC\"\n}"},"scores":{"kind":"list like","value":[0.0006176045862957835,0.000677257776260376,0.0005897372029721737,0.0005453733610920608,0.0005776866455562413,0.0005522164865396917,0.0005655502318404615,0.0005531154456548393],"string":"[\n 0.0006176045862957835,\n 0.000677257776260376,\n 0.0005897372029721737,\n 0.0005453733610920608,\n 0.0005776866455562413,\n 0.0005522164865396917,\n 0.0005655502318404615,\n 0.0005531154456548393\n]"},"avg_score":{"kind":"number","value":0.0005848177170264535,"string":"0.000585"},"num_sents":{"kind":"number","value":8,"string":"8"}}},{"rowIdx":730,"cells":{"texts":{"kind":"list like","value":["By Lauren Hittinger\n\nAOA is taking things a little easy this week for summer break. ","So we thought it'd be a good time to catch up with some local businesses we've covered during the last year (or so) and find out how things are going.","\n\nNext we're revisiting Collar City Hard Pressed (CCHP). ","When we first interviewed owner Jessica Garrity, now Jessica Quijano, she was running her business solely at the Saturday Troy farmers' market. ","Since then, she has moved to working full-time for her juice and smoothie business, taking up residence on Broadway in downtown Troy.","\n\nA snippet from March 2014:\n\n\n\n\n\n\"I found myself basically obsessed with fresh juice and smoothies and was suddenly annoyed that there wasn't a place in my neighborhood where I could get any. ","I kind of hate leaving my neighborhood on the weekend so just thought it was only fair that we had a juice place here downtown. ","I also recognized that juicing was a pretty trendy business and thought downtown Troy would be a great place to get to work.\"","\n\nI caught up with Quijano to see what it's like to be running a small business on her own, and to get the scoop on the different reactions to a juice bar in downtown Troy.","\n\nWhat has happened over the last year?","\n\nA lot has happened! ","I opened in here last August -- so, going on a year. ","That was a major deal. ","It was really great to open when I did, because it was still kind of busy in the fall. ","Winter was definitely a slower season, I think for everyone around here. ","But it's been nice because then I was able to really ramp up for spring and summer. ","I've seen so many new customers and so much new business. ","Having the winter be the time when I was learning everything the hard way was kind of good timing.","\n\nAnd a lot is new -- I have really ramped up social media and I have a website now. ","People can order online through Yelp. ","I have three people who work in here.","\n\nWhat's different since you were just at the farmers' market?","\n\nI have a lot more relationships with farmers and suppliers in general -- local people. ","It's been a tough year, since stuff is coming up later based on weather. ","Seasonally I try to go right to the farmer to get stuff. ","Of course, not for things like pineapples and bananas. ","So I'll never be 100 percent organic or local, just because for some ingredients it just really doesn't make sense.","\n\nAnd I've done stuff with Sage and RPI to get in front of students, and their faculty and staff have been down here a lot. ","Collar City Candle works with me to make candles based upon all of the different drinks. ","I have a phone line in here and people can text in their orders ahead of time. ","I have a good relationship with Empire Zero, the composting company. ","All of our juice pulp either goes directly to a farm and is used for animal feed or it is composted through Empire Zero. ","It's never thrown away.","\n\nWhat have you learned since opening the physical shop?","\n\nOh my god. (","laughs) Well, I've had professional jobs. ","But I've never done anything on the back end of business. ","Most of my work experience was in writing, or marketing, or sales. ","And that's all beneficial, but that's not the meat of what you're really doing. ","I've learned a lot. ","Everything as far as managing all my own books, and I've hired three employees this year. ","I just had never done any of that, so I basically learned it all as I went.","\n\nThe other thing about being in here is Troy is it's such an interesting place. ","I'm in contact with a lot of other local businesses, and the flow of business can be really unpredictable. ","It's such a walkable neighborhood and if for some reason people aren't walking around, because of weather, or something's blocking streets, it can affect you.","\n\nThe positive thing about having my store right here is all of the businesses are so collaborative and everyone really does support each other. ","So it was a very warm welcome. ","For me opening in here it was probably easier than it would be for other people because of the farmers' market and Vic [Christopher] and Heather [LaVine], my landlords, have been so great.","\n\nWhat has surprised you?","\n\nThe timing is a surprise to me. ","I'm open 8 to 4, but the majority of people come here between 10 and 2, no matter what. ","I thought there was more of an early morning type of thing.","\n\nThe other thing that has surprised me is how many customers will come every single day. ","I am getting a lot of new customers, and I can see that coming from Instagram, Facebook, and Yelp. ","But a lot of people come several times a week. ","I didn't think I'd see the same people getting the same things all the time. ","It's nice, though.","\n\nThe other thing that really surprises me are the people that come in that are afraid of food. ","For example, there have been times at the farmers' market where people ask me, 'Do you put pills in the juice? ","How do you get it that color?' ","This is the color that your food should be. ","This is real food. ","It's nice to be able to show people in a positive way that literally just eating carrots, beets, and apples can be really delicious and it looks beautiful, and there's not anything added. ","At least once a week someone is surprised I'm not doctoring the juice up. ","It's been nice to see people try new things and then really really like it and then start adding other more adventurous things like bee pollen. ","It's nice to see people expand.","\n\nWhat has frustrated you?","\n\nWell, that same thing. ","Everything that I just said. ","There are days when you're like, 'Really? ","You really think I'm putting dye in here?'","\n\nEverything in my store is repurposed, and I compost and work with farms and I'm trying to do all of these right things, and I think that you care as a customer. ","But you're telling me you would be drinking this if there were red dye in it?","\n\nIt's frustrating when someone walks in, looks at the menu, and tells me they don't like any fruit or vegetables. ","I don't know what to do in that case. ","I really work to get the person to try something that would just taste delicious, but sometimes it's just not for everyone, I guess. ","All that aside, if I get the person to try something, they usually like it.","\n\nWhat's something that's felt like a win?","\n\nI've seen so many new customers and seen such a difference in the amount of people that know the name of my place and recognize the brand. ","I never did a lot of promotion or press, so it was a little bit slower in the beginning with people knowing the place and recognizing CCHP. ","Now if someone asks me where I work and they say that they know the place or love it here, that's awesome to me, especially when you're not in this neighborhood.","\n\nWhat's next?","\n\nWell, there are a couple top secret things in the works. ","The main thing is continuing to try to make as local connections and source the best product that I can. ","I would also like to be open more often. ","And I'm collaborating with some of my neighbors here on some cool stuff.","\n\nAnd pretty soon I'll be thinking about delicious fall and winter concoctions, like the pumpkin pie smoothie.","\n\nThis interview has been lightly edited and condensed.","\n\n____\n\nLauren Hittinger writes about shopping, crafting, and living well on a small budget at The Thrifty Ginger.","\n\nMore follow-ups from this week:\n\n+ Bread and Honey"],"string":"[\n \"By Lauren Hittinger\\n\\nAOA is taking things a little easy this week for summer break. \",\n \"So we thought it'd be a good time to catch up with some local businesses we've covered during the last year (or so) and find out how things are going.\",\n \"\\n\\nNext we're revisiting Collar City Hard Pressed (CCHP). \",\n \"When we first interviewed owner Jessica Garrity, now Jessica Quijano, she was running her business solely at the Saturday Troy farmers' market. \",\n \"Since then, she has moved to working full-time for her juice and smoothie business, taking up residence on Broadway in downtown Troy.\",\n \"\\n\\nA snippet from March 2014:\\n\\n\\n\\n\\n\\n\\\"I found myself basically obsessed with fresh juice and smoothies and was suddenly annoyed that there wasn't a place in my neighborhood where I could get any. \",\n \"I kind of hate leaving my neighborhood on the weekend so just thought it was only fair that we had a juice place here downtown. \",\n \"I also recognized that juicing was a pretty trendy business and thought downtown Troy would be a great place to get to work.\\\"\",\n \"\\n\\nI caught up with Quijano to see what it's like to be running a small business on her own, and to get the scoop on the different reactions to a juice bar in downtown Troy.\",\n \"\\n\\nWhat has happened over the last year?\",\n \"\\n\\nA lot has happened! \",\n \"I opened in here last August -- so, going on a year. \",\n \"That was a major deal. \",\n \"It was really great to open when I did, because it was still kind of busy in the fall. \",\n \"Winter was definitely a slower season, I think for everyone around here. \",\n \"But it's been nice because then I was able to really ramp up for spring and summer. \",\n \"I've seen so many new customers and so much new business. \",\n \"Having the winter be the time when I was learning everything the hard way was kind of good timing.\",\n \"\\n\\nAnd a lot is new -- I have really ramped up social media and I have a website now. \",\n \"People can order online through Yelp. \",\n \"I have three people who work in here.\",\n \"\\n\\nWhat's different since you were just at the farmers' market?\",\n \"\\n\\nI have a lot more relationships with farmers and suppliers in general -- local people. \",\n \"It's been a tough year, since stuff is coming up later based on weather. \",\n \"Seasonally I try to go right to the farmer to get stuff. \",\n \"Of course, not for things like pineapples and bananas. \",\n \"So I'll never be 100 percent organic or local, just because for some ingredients it just really doesn't make sense.\",\n \"\\n\\nAnd I've done stuff with Sage and RPI to get in front of students, and their faculty and staff have been down here a lot. \",\n \"Collar City Candle works with me to make candles based upon all of the different drinks. \",\n \"I have a phone line in here and people can text in their orders ahead of time. \",\n \"I have a good relationship with Empire Zero, the composting company. \",\n \"All of our juice pulp either goes directly to a farm and is used for animal feed or it is composted through Empire Zero. \",\n \"It's never thrown away.\",\n \"\\n\\nWhat have you learned since opening the physical shop?\",\n \"\\n\\nOh my god. (\",\n \"laughs) Well, I've had professional jobs. \",\n \"But I've never done anything on the back end of business. \",\n \"Most of my work experience was in writing, or marketing, or sales. \",\n \"And that's all beneficial, but that's not the meat of what you're really doing. \",\n \"I've learned a lot. \",\n \"Everything as far as managing all my own books, and I've hired three employees this year. \",\n \"I just had never done any of that, so I basically learned it all as I went.\",\n \"\\n\\nThe other thing about being in here is Troy is it's such an interesting place. \",\n \"I'm in contact with a lot of other local businesses, and the flow of business can be really unpredictable. \",\n \"It's such a walkable neighborhood and if for some reason people aren't walking around, because of weather, or something's blocking streets, it can affect you.\",\n \"\\n\\nThe positive thing about having my store right here is all of the businesses are so collaborative and everyone really does support each other. \",\n \"So it was a very warm welcome. \",\n \"For me opening in here it was probably easier than it would be for other people because of the farmers' market and Vic [Christopher] and Heather [LaVine], my landlords, have been so great.\",\n \"\\n\\nWhat has surprised you?\",\n \"\\n\\nThe timing is a surprise to me. \",\n \"I'm open 8 to 4, but the majority of people come here between 10 and 2, no matter what. \",\n \"I thought there was more of an early morning type of thing.\",\n \"\\n\\nThe other thing that has surprised me is how many customers will come every single day. \",\n \"I am getting a lot of new customers, and I can see that coming from Instagram, Facebook, and Yelp. \",\n \"But a lot of people come several times a week. \",\n \"I didn't think I'd see the same people getting the same things all the time. \",\n \"It's nice, though.\",\n \"\\n\\nThe other thing that really surprises me are the people that come in that are afraid of food. \",\n \"For example, there have been times at the farmers' market where people ask me, 'Do you put pills in the juice? \",\n \"How do you get it that color?' \",\n \"This is the color that your food should be. \",\n \"This is real food. \",\n \"It's nice to be able to show people in a positive way that literally just eating carrots, beets, and apples can be really delicious and it looks beautiful, and there's not anything added. \",\n \"At least once a week someone is surprised I'm not doctoring the juice up. \",\n \"It's been nice to see people try new things and then really really like it and then start adding other more adventurous things like bee pollen. \",\n \"It's nice to see people expand.\",\n \"\\n\\nWhat has frustrated you?\",\n \"\\n\\nWell, that same thing. \",\n \"Everything that I just said. \",\n \"There are days when you're like, 'Really? \",\n \"You really think I'm putting dye in here?'\",\n \"\\n\\nEverything in my store is repurposed, and I compost and work with farms and I'm trying to do all of these right things, and I think that you care as a customer. \",\n \"But you're telling me you would be drinking this if there were red dye in it?\",\n \"\\n\\nIt's frustrating when someone walks in, looks at the menu, and tells me they don't like any fruit or vegetables. \",\n \"I don't know what to do in that case. \",\n \"I really work to get the person to try something that would just taste delicious, but sometimes it's just not for everyone, I guess. \",\n \"All that aside, if I get the person to try something, they usually like it.\",\n \"\\n\\nWhat's something that's felt like a win?\",\n \"\\n\\nI've seen so many new customers and seen such a difference in the amount of people that know the name of my place and recognize the brand. \",\n \"I never did a lot of promotion or press, so it was a little bit slower in the beginning with people knowing the place and recognizing CCHP. \",\n \"Now if someone asks me where I work and they say that they know the place or love it here, that's awesome to me, especially when you're not in this neighborhood.\",\n \"\\n\\nWhat's next?\",\n \"\\n\\nWell, there are a couple top secret things in the works. \",\n \"The main thing is continuing to try to make as local connections and source the best product that I can. \",\n \"I would also like to be open more often. \",\n \"And I'm collaborating with some of my neighbors here on some cool stuff.\",\n \"\\n\\nAnd pretty soon I'll be thinking about delicious fall and winter concoctions, like the pumpkin pie smoothie.\",\n \"\\n\\nThis interview has been lightly edited and condensed.\",\n \"\\n\\n____\\n\\nLauren Hittinger writes about shopping, crafting, and living well on a small budget at The Thrifty Ginger.\",\n \"\\n\\nMore follow-ups from this week:\\n\\n+ Bread and Honey\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"OpenWebText2\"\n}"},"scores":{"kind":"list like","value":[0.0006279069930315018,0.0005063916323706508,0.0006054138648323715,0.0005933215143159032,0.0006595643935725093,0.0009513996192254126,0.0011271728435531259,0.0005385625408962369,0.0005715488223358989,0.0006881636218167841,0.00084668182535097,0.0006735367351211607,0.0007900481577962637,0.0005656696739606559,0.0006757556111551821,0.0005775451427325606,0.0007319471915252507,0.0006785777513869107,0.0007046271930448711,0.001070758793503046,0.0006129079265519977,0.0006149420514702797,0.0005418736836872995,0.0005948378820903599,0.0011546792229637504,0.0014101751148700714,0.0006780903204344213,0.0007821788312867284,0.0005958476103842258,0.0007327054627239704,0.0006521524046547711,0.001060686307027936,0.0008258727029897273,0.0006840109708718956,0.0011239750310778618,0.0006448777858167887,0.0009565131040289998,0.0006176214083097875,0.0019863510970026255,0.0006508193328045309,0.0006282814429141581,0.0006299422821030021,0.0007513124728575349,0.0005288983811624348,0.0011332872090861201,0.0005663161864504218,0.000586584210395813,0.0006163708749227226,0.0008489065221510828,0.0006580543122254312,0.0005724486545659602,0.0006429765489883721,0.0006933658150956035,0.0015985332429409027,0.0005786614492535591,0.0006010614451952279,0.0006319230888038874,0.001264010090380907,0.0006973319686949253,0.000843284884467721,0.0020096534863114357,0.001242258818820119,0.0006536351866088808,0.0006776655209250748,0.0005467241862788796,0.0005389222642406821,0.008656845428049564,0.0007000570185482502,0.0006989054381847382,0.0023367772810161114,0.00406432943418622,0.008033559657633305,0.008535266853868961,0.0006787691963836551,0.0006903230678290129,0.0007120129303075373,0.0007957647903822362,0.0007021409692242742,0.0005806921981275082,0.0005382284871302545,0.0005920093390159309,0.0007726129842922091,0.0005876788054592907,0.0005598045536316931,0.00052513467380777,0.0005335529567673802,0.0006472041714005172,0.0005518440157175064,0.0028291160706430674,0.0005966266617178917],"string":"[\n 0.0006279069930315018,\n 0.0005063916323706508,\n 0.0006054138648323715,\n 0.0005933215143159032,\n 0.0006595643935725093,\n 0.0009513996192254126,\n 0.0011271728435531259,\n 0.0005385625408962369,\n 0.0005715488223358989,\n 0.0006881636218167841,\n 0.00084668182535097,\n 0.0006735367351211607,\n 0.0007900481577962637,\n 0.0005656696739606559,\n 0.0006757556111551821,\n 0.0005775451427325606,\n 0.0007319471915252507,\n 0.0006785777513869107,\n 0.0007046271930448711,\n 0.001070758793503046,\n 0.0006129079265519977,\n 0.0006149420514702797,\n 0.0005418736836872995,\n 0.0005948378820903599,\n 0.0011546792229637504,\n 0.0014101751148700714,\n 0.0006780903204344213,\n 0.0007821788312867284,\n 0.0005958476103842258,\n 0.0007327054627239704,\n 0.0006521524046547711,\n 0.001060686307027936,\n 0.0008258727029897273,\n 0.0006840109708718956,\n 0.0011239750310778618,\n 0.0006448777858167887,\n 0.0009565131040289998,\n 0.0006176214083097875,\n 0.0019863510970026255,\n 0.0006508193328045309,\n 0.0006282814429141581,\n 0.0006299422821030021,\n 0.0007513124728575349,\n 0.0005288983811624348,\n 0.0011332872090861201,\n 0.0005663161864504218,\n 0.000586584210395813,\n 0.0006163708749227226,\n 0.0008489065221510828,\n 0.0006580543122254312,\n 0.0005724486545659602,\n 0.0006429765489883721,\n 0.0006933658150956035,\n 0.0015985332429409027,\n 0.0005786614492535591,\n 0.0006010614451952279,\n 0.0006319230888038874,\n 0.001264010090380907,\n 0.0006973319686949253,\n 0.000843284884467721,\n 0.0020096534863114357,\n 0.001242258818820119,\n 0.0006536351866088808,\n 0.0006776655209250748,\n 0.0005467241862788796,\n 0.0005389222642406821,\n 0.008656845428049564,\n 0.0007000570185482502,\n 0.0006989054381847382,\n 0.0023367772810161114,\n 0.00406432943418622,\n 0.008033559657633305,\n 0.008535266853868961,\n 0.0006787691963836551,\n 0.0006903230678290129,\n 0.0007120129303075373,\n 0.0007957647903822362,\n 0.0007021409692242742,\n 0.0005806921981275082,\n 0.0005382284871302545,\n 0.0005920093390159309,\n 0.0007726129842922091,\n 0.0005876788054592907,\n 0.0005598045536316931,\n 0.00052513467380777,\n 0.0005335529567673802,\n 0.0006472041714005172,\n 0.0005518440157175064,\n 0.0028291160706430674,\n 0.0005966266617178917\n]"},"avg_score":{"kind":"number","value":0.0010862819966860116,"string":"0.001086"},"num_sents":{"kind":"number","value":90,"string":"90"}}},{"rowIdx":731,"cells":{"texts":{"kind":"list like","value":["{% extends 'callisto_core/delivery/form.html' %}\n\n{% block message %}\n
We've sent you an email containing a password reset link. ","If you don't receive it within a few minutes, please check your spam folder.
It seems popular now though for large sites (e.g. twitter.com, github.com, ycombinator.com, stackoverflow.com just to name a few) to use relatively short DNS TTLs, between 1 and 5 minutes, presumably to make failover easier.
Has popular opinion around short TTLs being "OK" changed? ","Are these sites doing something special to make this viable?","\n======\nwahern\nVery large site operators use anycast routing[1] which is particularly well\nsuited to UDP DNS; they can easily spread load and minimize latency. ","If you\ncan leverage anycast directly or indirectly through DNS hosting services then\nlow TTLs are not a problem.","\n\nOtherwise, it depends. ","Even with one DNS query per HTTP request, DNS will only\nrepresent a fraction of your network load. ","It's difficult to make any DNS\nserver break a sweat. ","More likely the network link will saturate beforehand,\ncausing lots of dropped packets. ","But it's trivial to advertise and use\nmultiple DNS servers; much more trivial than a web application stack. ","DNS was\nbuilt for high availability almost since day 1. ","This is also why you shouldn't\nworry too much about low TTLs exacerbating network faults--there's no excuse\nfor not using geographically dispersed authoritative name servers.","\n\nFor example, depending on the site I'll often host the domain on my own\nprimary name server so I can control records without fscking with a web GUI or\nREST API, but the advertised authoritative name servers are EasyDNS servers\nwhich behave as secondaries mirroring my primary.","\n\nThe real issue isn't load but latency. ","That's a more complex problem. ","If\nyou're not using anycast then your site is probably not big enough or\nimportant enough for a few millisecond latency upfront for intermittent page\nloads to matter. ","Also, many caching resolvers these days will preemptively\nrefresh records upon TTL expiration subject to usage patterns, which means if\nyou're seeing moderate, repeat traffic then users may not experience any\nadditional latency at all. (","Similarly, caching resolvers will often remember\nfailing servers and try them last, regardless of ordering in a response.)","\n\nAs for how painful are erroneous DNS changes, low and high TTLs cut both ways.","\nIf it really matters you should be monitoring this stuff 24/7 (e.g. Pingdom),\nwhich means record errors should be quickly identified and reported. ","If you're\nsetup to respond quickly (which you should be for a serious commercial\noperation), that augurs in favor of low TTLs.","\n\n[1]\n[https://en.wikipedia.org/wiki/Anycast](https://en.wikipedia.org/wiki/Anycast)\n\n------\nbigiain\nAWS Route53 defaults to 300 seconds (which is probably why so many articles\nsee that as the median ttl), and I've never encountered problems leaving that\nat the default. ","I suspect the performance problems are real if you're running\nyour own dns servers - but if you're piggybacking on something like AWS I\nseriously doubt you'll see issues (apart from monthly bills, if you suddenly\ngo viral to the moon...)\n\n\"Back in the day\", Internet Explorer was a problem with TTLs, from memory IE6\nwas when they stopped caching all dns lookups for 24hrs no matter what the til\nwas, and IE6 still coached for 4hrs. (","This was a drama for me back in the\nearly 2000's when I was trying to do dns based load balancing...)\n\nMy opinion these days is don't try to go much below 1 minute if you want other\npeoples resolvers or software to honour your ttls, but I do see people using 1\nsec ttls occasionally, so presumably if your application doesn't mind too much\nif not everybody h9onours your ttl - it's still worth doing for some people...\n\n------\nmfincham\nAlso in the mix: is there any point in having multiple A records for a busy\nsite now?","\n\n"],"string":"[\n \"\\nAsk HN: Are we all OK with short DNS TTLs now? - \",\n \"mfincham\\nConventional wisdom has long had it that short DNS TTLs are bad because they increase query loads and any faults in DNS will cause availability problems more quickly.
It seems popular now though for large sites (e.g. twitter.com, github.com, ycombinator.com, stackoverflow.com just to name a few) to use relatively short DNS TTLs, between 1 and 5 minutes, presumably to make failover easier.
Has popular opinion around short TTLs being "OK" changed? \",\n \"Are these sites doing something special to make this viable?\",\n \"\\n======\\nwahern\\nVery large site operators use anycast routing[1] which is particularly well\\nsuited to UDP DNS; they can easily spread load and minimize latency. \",\n \"If you\\ncan leverage anycast directly or indirectly through DNS hosting services then\\nlow TTLs are not a problem.\",\n \"\\n\\nOtherwise, it depends. \",\n \"Even with one DNS query per HTTP request, DNS will only\\nrepresent a fraction of your network load. \",\n \"It's difficult to make any DNS\\nserver break a sweat. \",\n \"More likely the network link will saturate beforehand,\\ncausing lots of dropped packets. \",\n \"But it's trivial to advertise and use\\nmultiple DNS servers; much more trivial than a web application stack. \",\n \"DNS was\\nbuilt for high availability almost since day 1. \",\n \"This is also why you shouldn't\\nworry too much about low TTLs exacerbating network faults--there's no excuse\\nfor not using geographically dispersed authoritative name servers.\",\n \"\\n\\nFor example, depending on the site I'll often host the domain on my own\\nprimary name server so I can control records without fscking with a web GUI or\\nREST API, but the advertised authoritative name servers are EasyDNS servers\\nwhich behave as secondaries mirroring my primary.\",\n \"\\n\\nThe real issue isn't load but latency. \",\n \"That's a more complex problem. \",\n \"If\\nyou're not using anycast then your site is probably not big enough or\\nimportant enough for a few millisecond latency upfront for intermittent page\\nloads to matter. \",\n \"Also, many caching resolvers these days will preemptively\\nrefresh records upon TTL expiration subject to usage patterns, which means if\\nyou're seeing moderate, repeat traffic then users may not experience any\\nadditional latency at all. (\",\n \"Similarly, caching resolvers will often remember\\nfailing servers and try them last, regardless of ordering in a response.)\",\n \"\\n\\nAs for how painful are erroneous DNS changes, low and high TTLs cut both ways.\",\n \"\\nIf it really matters you should be monitoring this stuff 24/7 (e.g. Pingdom),\\nwhich means record errors should be quickly identified and reported. \",\n \"If you're\\nsetup to respond quickly (which you should be for a serious commercial\\noperation), that augurs in favor of low TTLs.\",\n \"\\n\\n[1]\\n[https://en.wikipedia.org/wiki/Anycast](https://en.wikipedia.org/wiki/Anycast)\\n\\n------\\nbigiain\\nAWS Route53 defaults to 300 seconds (which is probably why so many articles\\nsee that as the median ttl), and I've never encountered problems leaving that\\nat the default. \",\n \"I suspect the performance problems are real if you're running\\nyour own dns servers - but if you're piggybacking on something like AWS I\\nseriously doubt you'll see issues (apart from monthly bills, if you suddenly\\ngo viral to the moon...)\\n\\n\\\"Back in the day\\\", Internet Explorer was a problem with TTLs, from memory IE6\\nwas when they stopped caching all dns lookups for 24hrs no matter what the til\\nwas, and IE6 still coached for 4hrs. (\",\n \"This was a drama for me back in the\\nearly 2000's when I was trying to do dns based load balancing...)\\n\\nMy opinion these days is don't try to go much below 1 minute if you want other\\npeoples resolvers or software to honour your ttls, but I do see people using 1\\nsec ttls occasionally, so presumably if your application doesn't mind too much\\nif not everybody h9onours your ttl - it's still worth doing for some people...\\n\\n------\\nmfincham\\nAlso in the mix: is there any point in having multiple A records for a busy\\nsite now?\",\n \"\\n\\n\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"HackerNews\"\n}"},"scores":{"kind":"list like","value":[0.001059523900039494,0.0007822515326552093,0.0006624445668421686,0.0008520829724147916,0.0008316165185533464,0.0006631418946199119,0.0007512214942835271,0.00956298504024744,0.0006297813961282372,0.001019093906506896,0.0006334000499919057,0.0008795978501439095,0.0008989224443212152,0.0008507391321472824,0.001007532118819654,0.004182333126664162,0.000628452398814261,0.0007069807616062462,0.0008148890919983387,0.0006097909645177424,0.000872092496138066,0.0006752524641342461,0.013037290424108505,0.0008243026095442474,0.001995444530621171],"string":"[\n 0.001059523900039494,\n 0.0007822515326552093,\n 0.0006624445668421686,\n 0.0008520829724147916,\n 0.0008316165185533464,\n 0.0006631418946199119,\n 0.0007512214942835271,\n 0.00956298504024744,\n 0.0006297813961282372,\n 0.001019093906506896,\n 0.0006334000499919057,\n 0.0008795978501439095,\n 0.0008989224443212152,\n 0.0008507391321472824,\n 0.001007532118819654,\n 0.004182333126664162,\n 0.000628452398814261,\n 0.0007069807616062462,\n 0.0008148890919983387,\n 0.0006097909645177424,\n 0.000872092496138066,\n 0.0006752524641342461,\n 0.013037290424108505,\n 0.0008243026095442474,\n 0.001995444530621171\n]"},"avg_score":{"kind":"number","value":0.001817246547434479,"string":"0.001817"},"num_sents":{"kind":"number","value":25,"string":"25"}}},{"rowIdx":736,"cells":{"texts":{"kind":"list like","value":["Happy Sunday Everyone; I say this with a fair amount of sarcasm, as the weekend comes to a close. ","This happens to mean little to me as I work pretty much 24 hours a day 7 days a week; it just goes with my job, I just fill the voids with the things in life that I enjoy.","\n\nToday I used a new straight razor I bought and received yesterday, a Ralf Aust 6/8 Spanish point in Olive wood scales. ","Beautiful razor by every account, and came from Straight Razor Design in the fast and professional way in which I am starting to measure everything else by. ","dammit Amazon Prime; FASTER ! ","I really like the feel of the 6/8 blade opposed to the 5/8 mainly due to the weight added; I like the 5/8 just fine, but it is good to know that there are options now for me ranging from 4/8-7/8 in my den.","\n\nBeing my last day of the week shave and it also being a “S” day I decided to end it for the Lord with St. James from Taylor of old Bond street (TOBS). ","This is a great youthful and light scent that really says spring is on its way and is by no means a winter or fall scent. ","Perfect for an oddly hot 80 degree April day in the northeast. ","I used my Plisson synthetic which works amazingly well at lathering creams enough said there. ","I have not tried many synthetic brushes but where this brush lacks is in backbone where it excels is in softness easily being the softest brush I have ever used bar none; hence why it works as a bowl latherer with creams so well.","\n\nI ended the shave with the standard cold water rinse, and alum block, and Thayer’s unscented witch hazel. ","I used the matching St. James after shave splash and Aveeno scent free balm. ","Almost zero feed back from the alum block and my face is getting nearer to BBS smooth with every straight shave. – ","Aaron"],"string":"[\n \"Happy Sunday Everyone; I say this with a fair amount of sarcasm, as the weekend comes to a close. \",\n \"This happens to mean little to me as I work pretty much 24 hours a day 7 days a week; it just goes with my job, I just fill the voids with the things in life that I enjoy.\",\n \"\\n\\nToday I used a new straight razor I bought and received yesterday, a Ralf Aust 6/8 Spanish point in Olive wood scales. \",\n \"Beautiful razor by every account, and came from Straight Razor Design in the fast and professional way in which I am starting to measure everything else by. \",\n \"dammit Amazon Prime; FASTER ! \",\n \"I really like the feel of the 6/8 blade opposed to the 5/8 mainly due to the weight added; I like the 5/8 just fine, but it is good to know that there are options now for me ranging from 4/8-7/8 in my den.\",\n \"\\n\\nBeing my last day of the week shave and it also being a “S” day I decided to end it for the Lord with St. James from Taylor of old Bond street (TOBS). \",\n \"This is a great youthful and light scent that really says spring is on its way and is by no means a winter or fall scent. \",\n \"Perfect for an oddly hot 80 degree April day in the northeast. \",\n \"I used my Plisson synthetic which works amazingly well at lathering creams enough said there. \",\n \"I have not tried many synthetic brushes but where this brush lacks is in backbone where it excels is in softness easily being the softest brush I have ever used bar none; hence why it works as a bowl latherer with creams so well.\",\n \"\\n\\nI ended the shave with the standard cold water rinse, and alum block, and Thayer’s unscented witch hazel. \",\n \"I used the matching St. James after shave splash and Aveeno scent free balm. \",\n \"Almost zero feed back from the alum block and my face is getting nearer to BBS smooth with every straight shave. – \",\n \"Aaron\"\n]"},"meta":{"kind":"string","value":"{\n \"pile_set_name\": \"OpenWebText2\"\n}"},"scores":{"kind":"list like","value":[0.0007421718328259885,0.00075098208617419,0.0006635803147219121,0.0005991914076730609,0.8004761934280396,0.000604144879616797,0.001812380156479776,0.0005986571195535362,0.0007647057645954192,0.0007233414216898382,0.0006677196943201125,0.02625228278338909,0.0011549179907888174,0.11495364457368851,0.0082699628546834],"string":"[\n 0.0007421718328259885,\n 0.00075098208617419,\n 0.0006635803147219121,\n 0.0005991914076730609,\n 0.8004761934280396,\n 0.000604144879616797,\n 0.001812380156479776,\n 0.0005986571195535362,\n 0.0007647057645954192,\n 0.0007233414216898382,\n 0.0006677196943201125,\n 0.02625228278338909,\n 0.0011549179907888174,\n 0.11495364457368851,\n 0.0082699628546834\n]"},"avg_score":{"kind":"number","value":0.06393559175388266,"string":"0.063936"},"num_sents":{"kind":"number","value":15,"string":"15"}}},{"rowIdx":737,"cells":{"texts":{"kind":"list like","value":["Q:\n\nSending data using Ajax to PHP\n\nI am trying to send a string via ajax using the GET method but whenever that string contains some punctuation characters those characters do not appear when I use the echo in php.","\nFor example if I send a string \"sub + 12\" the php will echo \"sub 12\"\nIf I send \"&()*\", php will echo an empty string.","\nWhy does this happen?","\nAre there any special characters that the string cannot contain?","\n\nA:\n\nyou encodeURIComponent(). ","this is demo code which you can check\nsomething like this encodeURIComponent(yourtext)\nfirst this html code . ","in text filed enter your text and check this output, this is onkeyup so enter text and check result\n\n