reflow comments in modules/webdatabase

third_party/WebKit/Source/modules/webdatabase/DatabaseContext.cpp

 /*
  * Copyright (C) 2008 Apple Inc. All Rights Reserved.
  * Copyright (C) 2011 Google, Inc. All Rights Reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions
  * are met:
  * 1. Redistributions of source code must retain the above copyright
  *    notice, this list of conditions and the following disclaimer.
  * 2. Redistributions in binary form must reproduce the above copyright
@@ skipping 32 matching lines @@
 // ========================================
 // ... in other words, who's keeping the DatabaseContext alive and how long does
 // it need to stay alive?
 //
 // The DatabaseContext is referenced from:
 // 1. DatabaseManager
 // 2. Database
 //
 // At Birth:
 // ========
-// We create a DatabaseContext only when there is a need i.e. the script tries to
-// open a Database via DatabaseManager::openDatabase().
+// We create a DatabaseContext only when there is a need i.e. the script tries
+// to open a Database via DatabaseManager::openDatabase().
 //
 // The DatabaseContext constructor will register itself to DatabaseManager. This
 // lets DatabaseContext keep itself alive until it is unregisterd in
 // contextDestroyed().
 //
 // Once a DatabaseContext is associated with a ExecutionContext, it will
 // live until after the ExecutionContext destructs. This is true even if
 // we don't succeed in opening any Databases for that context. When we do
 // succeed in opening Databases for this ExecutionContext, the Database
 // will re-use the same DatabaseContext.
 //
 // At Shutdown:
 // ===========
 // During shutdown, the DatabaseContext needs to:
 // 1. "outlive" the ExecutionContext.
-//    - This is needed because the DatabaseContext needs to remove itself from the
+//    - This is needed because the DatabaseContext needs to remove itself from
+//    the
 //      ExecutionContext's ActiveDOMObject list and ContextLifecycleObserver
-//      list. This removal needs to be executed on the script's thread. Hence, we
+//      list. This removal needs to be executed on the script's thread. Hence,
+//      we
 //      rely on the ExecutionContext's shutdown process to call
 //      stop() and contextDestroyed() to give us a chance to clean these up from
 //      the script thread.
 //
 // 2. "outlive" the Databases.
-//    - This is because they may make use of the DatabaseContext to execute a close
-//      task and shutdown in an orderly manner. When the Databases are destructed,
-//      they will release the DatabaseContext reference from the DatabaseThread.
+//    - This is because they may make use of the DatabaseContext to execute a
+//      close task and shutdown in an orderly manner. When the Databases are
+//      destructed, they will release the DatabaseContext reference from the
+//      DatabaseThread.
 //
 // During shutdown, the ExecutionContext is shutting down on the script thread
-// while the Databases are shutting down on the DatabaseThread. Hence, there can be
-// a race condition as to whether the ExecutionContext or the Databases
+// while the Databases are shutting down on the DatabaseThread. Hence, there can
+// be a race condition as to whether the ExecutionContext or the Databases
 // destruct first.
 //
 // The Members in the Databases and DatabaseManager will ensure that the
 // DatabaseContext will outlive Database and ExecutionContext regardless of
 // which of the 2 destructs first.
 
 DatabaseContext* DatabaseContext::create(ExecutionContext* context) {
   DatabaseContext* self = new DatabaseContext(context);
   DatabaseManager::manager().registerDatabaseContext(self);
   return self;
@@ skipping 47 matching lines @@
 }
 
 DatabaseThread* DatabaseContext::databaseThread() {
   if (!m_databaseThread && !m_hasOpenDatabases) {
     // It's OK to ask for the m_databaseThread after we've requested
     // termination because we're still using it to execute the closing
     // of the database. However, it is NOT OK to create a new thread
     // after we've requested termination.
     ASSERT(!m_hasRequestedTermination);
 
-    // Create the database thread on first request - but not if at least one database was already opened,
-    // because in that case we already had a database thread and terminated it and should not create another.
+    // Create the database thread on first request - but not if at least one
+    // database was already opened, because in that case we already had a
+    // database thread and terminated it and should not create another.
     m_databaseThread = DatabaseThread::create();
     m_databaseThread->start();
   }
 
   return m_databaseThread.get();
 }
 
 bool DatabaseContext::databaseThreadAvailable() {
   return databaseThread() && !m_hasRequestedTermination;
 }
@@ skipping 22 matching lines @@
 
 SecurityOrigin* DatabaseContext::getSecurityOrigin() const {
   return getExecutionContext()->getSecurityOrigin();
 }
 
 bool DatabaseContext::isContextThread() const {
   return getExecutionContext()->isContextThread();
 }
 
 }  // namespace blink