Fawkes API  Fawkes Development Version
WebviewThread Class Reference

Webview Thread. More...

#include "webview_thread.h"

Inheritance diagram for WebviewThread:

List of all members.

Public Member Functions

 WebviewThread ()
 Constructor.
virtual void init ()
 Initialize the thread.
virtual void finalize ()
 Finalize the thread.
virtual void loop ()
 Code to execute in the thread.

Static Public Attributes

static const char * STATIC_URL_PREFIX = "/static"
 Prefix for the WebStaticRequestProcessor.
static const char * BLACKBOARD_URL_PREFIX = "/blackboard"
 Prefix for the WebBlackBoardRequestProcessor.
static const char * PLUGINS_URL_PREFIX = "/plugins"
 Prefix for the WebPluginsRequestProcessor.

Protected Member Functions

virtual void run ()
 Stub to see name in backtrace for easier debugging.

Detailed Description

Webview Thread.

This thread runs the HTTP server and handles requests via the WebRequestDispatcher.

Author:
Tim Niemueller

Constructor & Destructor Documentation

WebviewThread::WebviewThread ( )

Constructor.

Definition at line 56 of file webview_thread.cpp.

References fawkes::Thread::set_prepfin_conc_loop().


Member Function Documentation

void WebviewThread::finalize ( ) [virtual]

Finalize the thread.

This method is executed just before the thread is canceled and destroyed. It is always preceeded by a call to prepare_finalize(). If this is not the case this is a failure. The condition can be checked with the boolean variable finalize_prepared.

This method is meant to be used in conjunction with aspects and to cover thread inter-dependencies. This routine MUST bring the thread into a safe state such that it may be canceled and destroyed afterwards. If there is any reason that this cannot happen make your prepare_finalize() reports so.

This method is called by the thread manager just before the thread is being cancelled. Here you can do whatever steps are necessary just before the thread is cancelled. Note that you thread is still running and might be in the middle of a loop, so it is not a good place to give up on all resources used. Mind segmentation faults that could happen. Protect the area with a mutex that you lock at the beginning of your loop and free in the end, and that you lock at the beginning of finalize and then never unlock. Also not that the finalization may be canceled afterwards. The next thing that happens is that either the thread is canceled and destroyed or that the finalization is canceled and the thread has to run again.

Finalize is called on a thread just before it is deleted. It is guaranteed to be called on a fully initialized thread (if no exception is thrown in init()) (this guarantee holds in the Fawkes framework).

The default implementation does nothing besides throwing an exception if prepare_finalize() has not been called.

Exceptions:
Exceptionthrown if prepare_finalize() has not been called.
See also:
prepare_finalize()
cancel_finalize()

Reimplemented from fawkes::Thread.

Definition at line 109 of file webview_thread.cpp.

References fawkes::NetworkAspect::service_publisher, fawkes::ServicePublisher::unpublish_service(), fawkes::NetworkAspect::service_browser, and fawkes::ServiceBrowser::unwatch_service().

void WebviewThread::init ( ) [virtual]

Initialize the thread.

This method is meant to be used in conjunction with aspects. Some parts of the initialization may only happen after some aspect of the thread has been initialized. Implement the init method with these actions. It is guaranteed to be called just after all aspects have been initialized and only once in the lifetime of the thread. Throw an exception if any problem occurs and the thread should not run.

Just because your init() routine suceeds and everything looks fine for this thread does not automatically imply that it will run. If it belongs to a group of threads in a ThreadList and any of the other threads fail to initialize then no thread from this group is run and thus this thread will never run. In that situation finalize() is called for this very instance, prepare_finalize() however is not called.

See also:
Fawkes Thread Aspects

Reimplemented from fawkes::Thread.

Definition at line 70 of file webview_thread.cpp.

References fawkes::ConfigurableAspect::config, fawkes::Configuration::get_uint(), fawkes::CacheLogger::clear(), fawkes::NetworkAspect::nnresolver, fawkes::NetworkService::add_txt(), fawkes::LoggingAspect::logger, STATIC_URL_PREFIX, BLACKBOARD_URL_PREFIX, fawkes::BlackBoardAspect::blackboard, PLUGINS_URL_PREFIX, fawkes::PluginDirectorAspect::plugin_manager, fawkes::WebRequestDispatcher::add_processor(), WebviewHeaderGenerator::add_nav_entry(), fawkes::Logger::log_info(), fawkes::NetworkAspect::service_publisher, fawkes::ServicePublisher::publish_service(), fawkes::NetworkAspect::service_browser, and fawkes::ServiceBrowser::watch_service().

void WebviewThread::loop ( ) [virtual]

Code to execute in the thread.

Implement this method to hold the code you want to be executed continously. If you do not implement this method, the default is that the thread will exit. This is useful if you choose to only implement once().

Reimplemented from fawkes::Thread.

Definition at line 131 of file webview_thread.cpp.

References fawkes::WebServer::process().

virtual void WebviewThread::run ( ) [inline, protected, virtual]

Stub to see name in backtrace for easier debugging.

See also:
Thread::run()

Reimplemented from fawkes::Thread.

Definition at line 72 of file webview_thread.h.


Member Data Documentation

const char * WebviewThread::BLACKBOARD_URL_PREFIX = "/blackboard" [static]

Prefix for the WebBlackBoardRequestProcessor.

Definition at line 68 of file webview_thread.h.

Referenced by init().

const char * WebviewThread::PLUGINS_URL_PREFIX = "/plugins" [static]

Prefix for the WebPluginsRequestProcessor.

Definition at line 69 of file webview_thread.h.

Referenced by init().

const char * WebviewThread::STATIC_URL_PREFIX = "/static" [static]

Prefix for the WebStaticRequestProcessor.

Definition at line 67 of file webview_thread.h.

Referenced by init().


The documentation for this class was generated from the following files: