---
layout: default
title: Home
pinned: true
referrer: no-referrer
description: Established in 2010, the Kernville Saloon is a highlight of this little Valley.
tags:
- kernville saloon
- bar
- pub
- kernville
- bands
- karaoke
---
{% include share-buttons.html text="Check out the Kernville Saloon" facebook=true twitter=true linkedin=true reddit=true gmail=true clipboard=true %}
Location


Uses of Package
io.permazen.core
-
Packages that use io.permazen.core Package Description io.permazen Abstraction layer allowing access to aDatabase
using normal Java objects.io.permazen.annotation io.permazen.app Support for Permazen command line applications.io.permazen.cli Permazen Command Line Interface (CLI) classes.io.permazen.cli.cmd Permazen CLICommand
related classes, including pre-defined commands.io.permazen.cli.telnet Support for Permazen Command Line Interface (CLI) over telnet connections.io.permazen.core Core classes for the Permazen Java persistence layer.io.permazen.core.type PermazenFieldType
s.io.permazen.core.util Permazen core API utility classes.io.permazen.jsck Classes associated withJsck
, the Permazen key/value database consistency checker.io.permazen.parse Permazen parsing related classes.io.permazen.parse.expr Classes for parsing Java expressions with Permazen-specific extensions.io.permazen.schema Classes for modeling PermazenDatabase
schemas.io.permazen.spring Spring Framework integration classes.io.permazen.vaadin Classes to facilitate Vaadin applications that interact with a Permazen database.io.permazen.vaadin.app Support for Permazen GUI applications based on Vaadin. -
Classes in io.permazen.core used by io.permazen Class Description Database Provides an object database abstraction on top of a key/value database.DatabaseException Superclass of all unchecked exceptions thrown by aDatabase
.DeleteAction Describes what action to take when an object that is still referred to by some other object is deleted.EnumValue FieldType Defines the encoding, ordering, and range of possible values for aSimpleField
.ObjId Object IDs.SnapshotTransaction A "snapshot"Transaction
that persists indefinitely.Transaction A PermazenDatabase
transaction. -
Classes in io.permazen.core used by io.permazen.annotation Class Description DeleteAction Describes what action to take when an object that is still referred to by some other object is deleted. -
Classes in io.permazen.core used by io.permazen.app Class Description Database Provides an object database abstraction on top of a key/value database.FieldType Defines the encoding, ordering, and range of possible values for aSimpleField
. -
Classes in io.permazen.core used by io.permazen.cli Class Description Database Provides an object database abstraction on top of a key/value database. -
Classes in io.permazen.core used by io.permazen.cli.cmd Class Description Transaction A PermazenDatabase
transaction. -
Classes in io.permazen.core used by io.permazen.cli.telnet Class Description Database Provides an object database abstraction on top of a key/value database. -
Classes in io.permazen.core used by io.permazen.core Class Description CollectionField Superclass of fields with types assignable toCollection
.ComplexField A complexField
, such as a collection or map field.CompositeIndex Represents a composite index on anObjType
.CoreIndex Core APIIndex
implementation representing a index on a single field.CoreIndex2 Core APIIndex2
implementation representing a composite index on two fields.CoreIndex3 Core APIIndex3
implementation representing a composite index on three fields.CoreIndex4 Core APIIndex4
implementation representing a composite index on four fields.CounterField Counter fields.CreateListener Listener interface for notifications that an object has just been created.Database Provides an object database abstraction on top of a key/value database.DatabaseException Superclass of all unchecked exceptions thrown by aDatabase
.DeleteAction Describes what action to take when an object that is still referred to by some other object is deleted.DeleteListener Listener interface for notifications that an object is about to be deleted.EnumArrayField A field that contains an array (having one or more dimensions) of values chosen from an ordered list of uniqueString
identifiers.EnumField A field that contains a value chosen from in an ordered list of uniqueString
identifiers.Field FieldSwitch Visitor pattern interface forField
s.FieldType Defines the encoding, ordering, and range of possible values for aSimpleField
.FieldTypeRegistry A registry ofFieldType
s.InconsistentDatabaseException Thrown when inconsistent content is detected in aDatabase
indicating a corrupted or invalid database, or a buggy underlying key-value store.InvalidSchemaException Thrown byDatabase.createTransaction(io.permazen.schema.SchemaModel, int, boolean)
when the provided schema is invalid.ListField List field.ListFieldChangeListener Listener interface for notifications of a change in value of aListField
.MapField Map field.MapFieldChangeListener Listener interface for notifications of a change in value of aMapField
.ObjId Object IDs.ObjType Represents aDatabase
object type.ReferenceField A field that references anotherDatabase
object.Schema Contains information describing one schema version.SchemaItem Schemas Contains the set of allSchema
s of objects visible in aTransaction
.SetField Set field.SetFieldChangeListener Listener interface for notifications of a change in value of aSetField
.SimpleField A simpleField
.SimpleFieldChangeListener Listener interface for notifications of a change in value of aSimpleField
.SnapshotTransaction A "snapshot"Transaction
that persists indefinitely.Transaction A PermazenDatabase
transaction.Transaction.Callback Callback interface for notification of transaction completion events.Transaction.ListenerSet A fixed collection of listeners (CreateListener
s,DeleteListener
s,VersionChangeListener
s,SimpleFieldChangeListener
s,SetFieldChangeListener
s,ListFieldChangeListener
s, andMapFieldChangeListener
s) that can be efficiently registered on aTransaction
all at once.TransactionException Superclass of exceptions associated with a specificTransaction
.VersionChangeListener Listener interface for notifications that an object's schema version has been changed to match the current transaction. -
Classes in io.permazen.core used by io.permazen.core.type Class Description EnumValue FieldType Defines the encoding, ordering, and range of possible values for aSimpleField
.ObjId Object IDs. -
Classes in io.permazen.core used by io.permazen.core.util Class Description ObjId Object IDs.ReferenceField A field that references anotherDatabase
object.Transaction A PermazenDatabase
transaction. -
Classes in io.permazen.core used by io.permazen.jsck Class Description FieldTypeRegistry A registry ofFieldType
s.ObjId Object IDs. -
Classes in io.permazen.core used by io.permazen.parse Class Description ComplexField A complexField
, such as a collection or map field.CompositeIndex Represents a composite index on anObjType
.Database Provides an object database abstraction on top of a key/value database.Field FieldType Defines the encoding, ordering, and range of possible values for aSimpleField
.ObjId Object IDs.ObjType Represents aDatabase
object type.Schema Contains information describing one schema version.SimpleField A simpleField
.Transaction A PermazenDatabase
transaction. -
Classes in io.permazen.core used by io.permazen.parse.expr Class Description Field ObjId Object IDs.SimpleField A simpleField
. -
Classes in io.permazen.core used by io.permazen.schema Class Description DeleteAction Describes what action to take when an object that is still referred to by some other object is deleted. -
Classes in io.permazen.core used by io.permazen.spring Class Description Transaction.Callback Callback interface for notification of transaction completion events. -
Classes in io.permazen.core used by io.permazen.vaadin Class Description FieldType Defines the encoding, ordering, and range of possible values for aSimpleField
.ObjId Object IDs. -
Classes in io.permazen.core used by io.permazen.vaadin.app Class Description ObjId Object IDs.


The Get App API lets you retrieve all the metadata associated with any of your apps by providing the app ID. The app ID can be obtained from the Admin panel.
curl 'https://v1.userbase.com/v1/admin/apps/$APP_ID' \
-XGET \
-H 'Authorization: Bearer $ACCESS_TOKEN'
Parameters
-
APP_ID - The app ID to retrieve.
-
ACCESS_TOKEN - Your access token.
Result
- appName [string] - The app's name.
- appId [string] - The app's unique identifier.
- creationDate [string] - The timestamp when the app was created.
- deleted [string] - The timestamp when the app was deleted, if the app has been deleted.
- paymentsMode [string] - The app's payments mode set in your Admin panel. Can be 'disabled', 'test', or 'prod'.
- testSubscriptionPlanId [string] - The app's test subscription plan set in your Admin panel.
- testTrialPeriodDays [number] - The number of trial days set on the app's test subscription plan in your Stripe Dashboard.
- prodSubscriptionPlanId [string] - The app's prod subscription plan set in your Admin panel.
- prodTrialPeriodDays [number] - The number of trial days set on the app's prod subscription plan in your Stripe Dashboard.


Calculates a score of a node depending on the result of executors.
The score for the node is calculated by multiplying scale and executor score. See followings for details.
| score of node | = | (Scale for Scores) * (executor score) |
|---|---|---|
| scale | = | (Scale Adjustment for Older Builds) * (# of builds from the last build) |
| executor score | = | (idle executor score) + (busy executor score) |
| idle executor score | = | (Score for Idle Executor) * (# of builds that the node can accept now) |
| busy executor score | = | (Score for Busy Executor) * (# of builds that are running on the node) |


The Hacker theme
The Hacker theme
Hacker is a Jekyll theme for GitHub Pages. You can preview the theme to see what it looks like, or even use it today.
Usage
To use the Hacker theme:
-
Add the following to your site’s
_config.yml
:theme: jekyll-theme-hacker
-
Optionally, if you’d like to preview your site on your computer, add the following to your site’s
Gemfile
:gem "github-pages", group: :jekyll_plugins
Customizing
Configuration variables
Hacker will respect the following variables, if set in your site’s _config.yml
:
title: [The title of your site]
description: [A short description of your site's purpose]
Additionally, you may choose to set the following optional variables:
show_downloads: ["true" or "false" to indicate whether to provide a download URL]
google_analytics: [Your Google Analytics tracking ID]
Stylesheet
If you’d like to add your own custom styles:
- Create a file called
/assets/css/style.scss
in your site - Add the following content to the top of the file, exactly as shown:
--- --- @import "minimal-mistakes-jekyll";
- Add any custom CSS (or Sass, including imports) you’d like immediately after the
@import
line
Layouts
If you’d like to change the theme’s HTML layout:
- Copy the original template from the theme’s repository
(Pro-tip: click “raw” to make copying easier) - Create a file called
/_layouts/default.html
in your site - Paste the default layout content copied in the first step
- Customize the layout as you’d like
Roadmap
See the open issues for a list of proposed features (and known issues).
Project philosophy
The Hacker theme is intended to make it quick and easy for GitHub Pages users to create their first (or 100th) website. The theme should meet the vast majority of users’ needs out of the box, erring on the side of simplicity rather than flexibility, and provide users the opportunity to opt-in to additional complexity if they have specific needs or wish to further customize their experience (such as adding custom CSS or modifying the default layout). It should also look great, but that goes without saying.
Contributing
Interested in contributing to Hacker? We’d love your help. Hacker is an open source project, built one contribution at a time by users like you. See the CONTRIBUTING file for instructions on how to contribute.
Previewing the theme locally
If you’d like to preview the theme locally (for example, in the process of proposing a change):
- Clone down the theme’s repository (
git clone https://github.com/pages-themes/hacker
) cd
into the theme’s directory- Run
script/bootstrap
to install the necessary dependencies - Run
bundle exec jekyll serve
to start the preview server - Visit
localhost:4000
in your browser to preview the theme
Running tests
The theme contains a minimal test suite, to ensure a site with the theme would build successfully. To run the tests, simply run script/cibuild
. You’ll need to run script/bootstrap
one before the test script will work.


Detailed information about the NOAAPORT NEXRAD feed is available from the Unidata NOAAPORT NEXRAD Feed page, including alternatives to using the LDM to get the data. Most sites will only want to get a subset of the NOAAPORT NEXRAD data via the LDM, because of the large number of products and volume of the data. This document describes how to get selected subsets of the new data stream.
First, determine who your upstream site is for the Family Of Services (FOS) data. There should already be a line in your etc/ldmd.conf configuration file requesting data from your upstream FOS site, which we will call your.floater.feed for the rest of this document. This is the host from which you should get the NEXRAD Floater Feed.
Next, determine who your upstream site is for the NEXRAD feed, by looking at the NEXRAD Feed Scheme, locating your host, and determining the first tier site in italics above your site name. We'll call this your.nexrad.feed in the remainder of this document. This is the assignment for the host from which you will get NEXRAD data other than the NEXRAD Floater Feed, if desired. your.floater.feed and your.nexrad.feed may or may not be identical.
The NEXRAD floater feed is named "FNEXRAD" ("NMC3" for LDM version 5.1.2 and earlier). It is not necessary to upgrade to a later version of the LDM just to be able to use the new FNEXRAD feed type name. In the rest of this document, we will use the "NMC3" feedtype, since a number of sites are still using LDM version 5.1.2 or earlier. "NMC3" will also work for later versions, but if you have LDM 5.1.3 or later, we suggest that you use "FNEXRAD" instead.
Before trying to get the NEXRAD floater data or a subset of the full NEXRAD data feed, you can check that the
data is available to you from upstream sites by using the "notifyme" command. To avoid having to wait for new
products, you can quickly check data for the previous hour with (-o 3600
). For example, for the
NEXRAD floater, use:
notifyme -v -l- -h your.floater.feed -f NMC3 -o 3600
where your.floater.feed refers to the upstream source for Family Of Services (FOS) data such as IDS, DDPLUS, and HDS. Similarly, to check availability for the full NEXRAD feed, use:
notifyme -v -l- -h your.nexrad.feed -f NEXRAD -o 3600
Before you start getting the data, decide what you want to do with it by adding lines to your pqact.conf configuration file for decoding or filing the data.
You will need to know something about the parts of the product ID for NOAAPORT NEXRAD products if you want to be
able to specify actions that depend on information in the product ID. In general, the product ID includes a WMO
header followed by a six-character AFOS PILS code following "/p
":
SDUSij cccc ddhhmm /pyyyzzz
| i | digit identifying the type of data (The first digit is either 2, 3, 5, or 7.) |
|---|---|
| j | digit identifying US region |
| cccc | NWS forecast office |
| ddhhmm | day of month, hour, minute |
| yyy | product code |
| zzz | radar site code |
NMC3 SDUS[2357]. .... (......) /p(...)(...) FILE -close -overwrite data/nexrad/\1\3\2.raw
ldmadmin pqactcheck
ldmadmin pqactHUP
To get all of the Unidata NEXRAD floater feed containing data for several NEXRAD sites where "interesting" weather is occurring and composite imagery created by the UPC from select NEXRAD Level III products from all reporting stations:
request NMC3 ".*" your.floater.feed
ldmadmin stop
ldmadmin start
To get a subset of the NEXRAD Level III products for the floater sites, for example only the base reflectivity and velocity products for the lowest tilt (N0R and N0V products), replace the pattern for all products ".*" in the above with a pattern for the specific products you want:
request NMC3 "/p(N0R|N0V)" your.floater.feed
ldmadmin stop
ldmadmin start
To get only the composite images in PNG-compressed format, replace the pattern for all products ".*" in the above with a pattern for the specific products:
request NMC3 "^(pnga2area|rad)" your.floater.feed
ldmadmin stop
ldmadmin start
To help you refine your ldmd.conf requests for FNEXRAD data, we provide the following examples of IDD headers for the PNG-compressed composite images (current as of May 17, 2002):
| Product Description | Example IDD Header |
| 1 km National Base Reflectivity (GINI format) | rad/NEXRCOMP/1km/n0r_20020517_2035 |
| 2 km National 1-hour Precipitation (GINI format) | rad/NEXRCOMP/2km/n1p_20020517_2038 |
| 4 km National Storm Total Precipitation (GINI format) | rad/NEXRCOMP/4km/ntp_20020517_2039 |
| 6 km National Base Reflectivity (AREA format) | pnga2area Q5 RL 300 RADAR BREF 6km 20020517 1949 |
| 10 km National Radar Coded Message (AREA format) | pnga2area Q5 RN 500 RADAR BREF 10km 20020517 1945 |
To specify a few select sites for which NEXRAD data is always desired, first get the 3-character site codes for the sites from NEXRAD Site Map. For the examples, let's assume you choose to get data from sites designated "ABC" and "XYZ":
request NNEXRAD "/p...(ABC|XYZ)" your.nexrad.feed
ldmadmin stop
ldmadmin start
Note that if you want to change the site selection, it is necessary to repeat all three of the above steps: there is no way to get the LDM to reread the ldmd.conf file without stopping and restarting it.
To get just a subset of products, say base reflectivity and base radial velocity for the lowest tilt (N0R and N0V products), replace the product pattern "..." in the above with a pattern for the specific products you want:
request NNEXRAD "/p(N0R|N0V)(ABC|XYZ)" your.nexrad.feed
which specifies 2 products from each of 2 sites.
To specify NEXRAD products from one of 10 U.S. regions, you can specify a pattern that matches NEXRAD products from only the desired region. For example, "SDUS[2357]4" designates products from the South Central U.S. (TX, AL, MS, LA, AR, TN, OK):
request NNEXRAD "^SDUS[2357]4" your.nexrad.feed
If you only wanted base reflectivity and base radial velocity for the lowest tilt (N0R and N0V products) for radars in this region, use:
request NNEXRAD "^SDUS[2357]4 .* /p(N0R|N0V)" your.nexrad.feed


| Package | com.wemakedigital.layout |
| Class | public class LayoutComponent |
| Inheritance | LayoutComponent flash.display.Sprite |
| Subclasses | LayoutContainer |
| Property | Defined by | ||
|---|---|---|---|
| bottom : Number
Anchor padding from the bottom of the container.
| LayoutComponent | ||
| colour : Number
Optional background colour for component
| LayoutComponent | ||
| colourAlpha : Number
Background colour alpha for component
| LayoutComponent | ||
| container : LayoutContainer
The component's layout container.
| LayoutComponent | ||
| created : Boolean
The created status of the component, true after createChildren is called after being added to the stage.
| LayoutComponent | ||
| explicitHeight : Number
The explicit height of the component.
| LayoutComponent | ||
| explicitMaxHeight : Number
The maximum explicit height of the component
| LayoutComponent | ||
| explicitMaxWidth : Number
The maximum explicit width of the component.
| LayoutComponent | ||
| explicitMinHeight : Number
The minumum explicit height of the component.
| LayoutComponent | ||
| explicitMinWidth : Number
The minumum explicit width of the component.
| LayoutComponent | ||
| explicitWidth : Number
The explicit width of the component.
| LayoutComponent | ||
| fixedHeight : Number
The fixed height of the component.
| LayoutComponent | ||
| fixedMaxHeight : Number
The maximum fixed height of the component
| LayoutComponent | ||
| fixedMaxWidth : Number
The maximum fixed width of the component.
| LayoutComponent | ||
| fixedMinHeight : Number
The minumum fixed height of the component.
| LayoutComponent | ||
| fixedMinWidth : Number
The minumum fixed width of the component.
| LayoutComponent | ||
| fixedWidth : Number
The fixed width of the component.
| LayoutComponent | ||
| horizontalCentre : Number
Anchor padding from the horizontal centre of the container.
| LayoutComponent | ||
| left : Number
Anchor padding from the left of the container.
| LayoutComponent | ||
| relativeHeight : Number
The relative height of the component.
| LayoutComponent | ||
| relativeMaxHeight : Number
The maximum relative height of the component
| LayoutComponent | ||
| relativeMaxWidth : Number
The maximum relative width of the component.
| LayoutComponent | ||
| relativeMinHeight : Number
The minumum relative height of the component.
| LayoutComponent | ||
| relativeMinWidth : Number
The minumum relative width of the component.
| LayoutComponent | ||
| relativeWidth : Number
The relative width of the component.
| LayoutComponent | ||
| right : Number
Anchor padding from the right of the container.
| LayoutComponent | ||
| top : Number
Anchor padding from the top of the container.
| LayoutComponent | ||
| verticalCentre : Number
Anchor padding from the vertical centre of the container.
| LayoutComponent |
| Property | Defined by | ||
|---|---|---|---|
| _bottom : Number = NaN | LayoutComponent | ||
| _colour : Number = NaN | LayoutComponent | ||
| _colourAlpha : Number = 1 | LayoutComponent | ||
| _container : LayoutContainer | LayoutComponent | ||
| _created : Boolean = false | LayoutComponent | ||
| _explicitHeight : Number = 0 | LayoutComponent | ||
| _explicitMaxHeight : Number = NaN | LayoutComponent | ||
| _explicitMaxWidth : Number = NaN | LayoutComponent | ||
| _explicitMinHeight : Number = 0 | LayoutComponent | ||
| _explicitMinWidth : Number = 0 | LayoutComponent | ||
| _explicitWidth : Number = 0 | LayoutComponent | ||
| _fixedHeight : Number = NaN | LayoutComponent | ||
| _fixedMaxHeight : Number = NaN | LayoutComponent | ||
| _fixedMaxWidth : Number = NaN | LayoutComponent | ||
| _fixedMinHeight : Number = 0 | LayoutComponent | ||
| _fixedMinWidth : Number = 0 | LayoutComponent | ||
| _fixedWidth : Number = NaN | LayoutComponent | ||
| _horizontalCentre : Number = NaN | LayoutComponent | ||
| _left : Number = NaN | LayoutComponent | ||
| _relativeHeight : Number = NaN | LayoutComponent | ||
| _relativeMaxHeight : Number = NaN | LayoutComponent | ||
| _relativeMaxWidth : Number = NaN | LayoutComponent | ||
| _relativeMinHeight : Number = 0 | LayoutComponent | ||
| _relativeMinWidth : Number = 0 | LayoutComponent | ||
| _relativeWidth : Number = NaN | LayoutComponent | ||
| _right : Number = NaN | LayoutComponent | ||
| _top : Number = NaN | LayoutComponent | ||
| _verticalCentre : Number = NaN | LayoutComponent |
| Method | Defined by | ||
|---|---|---|---|
|
Constructor.
| LayoutComponent | ||
|
addChild(child:DisplayObject):DisplayObject
| LayoutComponent | ||
|
removeChild(child:DisplayObject):DisplayObject
| LayoutComponent | ||
|
removeChildren():void
Called when the component is removedfrom the stage.
| LayoutComponent | ||
|
updateDisplay():void
Called when the component display changes.
| LayoutComponent | ||
|
updateProperties():void
Called when the component properties change.
| LayoutComponent |
| Method | Defined by | ||
|---|---|---|---|
|
createChildren():void
Called when the component is added to the stage.
| LayoutComponent |
| _bottom | property |
protected var _bottom:Number = NaN
| bottom | property |
bottom:Number
[read-write]Anchor padding from the bottom of the container.
Implementation public function get bottom():Number
public function set bottom(value:Number):void
| _colour | property |
protected var _colour:Number = NaN
| colour | property |
colour:Number
[read-write]Optional background colour for component
Implementation public function get colour():Number
public function set colour(value:Number):void
| _colourAlpha | property |
protected var _colourAlpha:Number = 1
| colourAlpha | property |
colourAlpha:Number
[read-write]Background colour alpha for component
Implementation public function get colourAlpha():Number
public function set colourAlpha(value:Number):void
| _container | property |
protected var _container:LayoutContainer
| container | property |
container:LayoutContainer
[read-write]The component's layout container.
Implementation public function get container():LayoutContainer
public function set container(value:LayoutContainer):void
| _created | property |
protected var _created:Boolean = false
| created | property |
created:Boolean
[read-write]The created status of the component, true after createChildren is called after being added to the stage.
Implementation public function get created():Boolean
public function set created(value:Boolean):void
| _explicitHeight | property |
protected var _explicitHeight:Number = 0
| explicitHeight | property |
explicitHeight:Number
[read-write]The explicit height of the component.
Implementation public function get explicitHeight():Number
public function set explicitHeight(value:Number):void
| _explicitMaxHeight | property |
protected var _explicitMaxHeight:Number = NaN
| explicitMaxHeight | property |
explicitMaxHeight:Number
[read-write]The maximum explicit height of the component
Implementation public function get explicitMaxHeight():Number
public function set explicitMaxHeight(value:Number):void
| _explicitMaxWidth | property |
protected var _explicitMaxWidth:Number = NaN
| explicitMaxWidth | property |
explicitMaxWidth:Number
[read-write]The maximum explicit width of the component.
Implementation public function get explicitMaxWidth():Number
public function set explicitMaxWidth(value:Number):void
| _explicitMinHeight | property |
protected var _explicitMinHeight:Number = 0
| explicitMinHeight | property |
explicitMinHeight:Number
[read-write]The minumum explicit height of the component.
Implementation public function get explicitMinHeight():Number
public function set explicitMinHeight(value:Number):void
| _explicitMinWidth | property |
protected var _explicitMinWidth:Number = 0
| explicitMinWidth | property |
explicitMinWidth:Number
[read-write]The minumum explicit width of the component.
Implementation public function get explicitMinWidth():Number
public function set explicitMinWidth(value:Number):void
| _explicitWidth | property |
protected var _explicitWidth:Number = 0
| explicitWidth | property |
explicitWidth:Number
[read-write]The explicit width of the component.
Implementation public function get explicitWidth():Number
public function set explicitWidth(value:Number):void
| _fixedHeight | property |
protected var _fixedHeight:Number = NaN
| fixedHeight | property |
fixedHeight:Number
[read-write]The fixed height of the component.
Implementation public function get fixedHeight():Number
public function set fixedHeight(value:Number):void
| _fixedMaxHeight | property |
protected var _fixedMaxHeight:Number = NaN
| fixedMaxHeight | property |
fixedMaxHeight:Number
[read-write]The maximum fixed height of the component
Implementation public function get fixedMaxHeight():Number
public function set fixedMaxHeight(value:Number):void
| _fixedMaxWidth | property |
protected var _fixedMaxWidth:Number = NaN
| fixedMaxWidth | property |
fixedMaxWidth:Number
[read-write]The maximum fixed width of the component.
Implementation public function get fixedMaxWidth():Number
public function set fixedMaxWidth(value:Number):void
| _fixedMinHeight | property |
protected var _fixedMinHeight:Number = 0
| fixedMinHeight | property |
fixedMinHeight:Number
[read-write]The minumum fixed height of the component.
Implementation public function get fixedMinHeight():Number
public function set fixedMinHeight(value:Number):void
| _fixedMinWidth | property |
protected var _fixedMinWidth:Number = 0
| fixedMinWidth | property |
fixedMinWidth:Number
[read-write]The minumum fixed width of the component.
Implementation public function get fixedMinWidth():Number
public function set fixedMinWidth(value:Number):void
| _fixedWidth | property |
protected var _fixedWidth:Number = NaN
| fixedWidth | property |
fixedWidth:Number
[read-write]The fixed width of the component.
Implementation public function get fixedWidth():Number
public function set fixedWidth(value:Number):void
| _horizontalCentre | property |
protected var _horizontalCentre:Number = NaN
| horizontalCentre | property |
horizontalCentre:Number
[read-write]Anchor padding from the horizontal centre of the container.
Implementation public function get horizontalCentre():Number
public function set horizontalCentre(value:Number):void
| _left | property |
protected var _left:Number = NaN
| left | property |
left:Number
[read-write]Anchor padding from the left of the container.
Implementation public function get left():Number
public function set left(value:Number):void
| _relativeHeight | property |
protected var _relativeHeight:Number = NaN
| relativeHeight | property |
relativeHeight:Number
[read-write]The relative height of the component.
Implementation public function get relativeHeight():Number
public function set relativeHeight(value:Number):void
| _relativeMaxHeight | property |
protected var _relativeMaxHeight:Number = NaN
| relativeMaxHeight | property |
relativeMaxHeight:Number
[read-write]The maximum relative height of the component
Implementation public function get relativeMaxHeight():Number
public function set relativeMaxHeight(value:Number):void
| _relativeMaxWidth | property |
protected var _relativeMaxWidth:Number = NaN
| relativeMaxWidth | property |
relativeMaxWidth:Number
[read-write]The maximum relative width of the component.
Implementation public function get relativeMaxWidth():Number
public function set relativeMaxWidth(value:Number):void
| _relativeMinHeight | property |
protected var _relativeMinHeight:Number = 0
| relativeMinHeight | property |
relativeMinHeight:Number
[read-write]The minumum relative height of the component.
Implementation public function get relativeMinHeight():Number
public function set relativeMinHeight(value:Number):void
| _relativeMinWidth | property |
protected var _relativeMinWidth:Number = 0
| relativeMinWidth | property |
relativeMinWidth:Number
[read-write]The minumum relative width of the component.
Implementation public function get relativeMinWidth():Number
public function set relativeMinWidth(value:Number):void
| _relativeWidth | property |
protected var _relativeWidth:Number = NaN
| relativeWidth | property |
relativeWidth:Number
[read-write]The relative width of the component.
Implementation public function get relativeWidth():Number
public function set relativeWidth(value:Number):void
| _right | property |
protected var _right:Number = NaN
| right | property |
right:Number
[read-write]Anchor padding from the right of the container.
Implementation public function get right():Number
public function set right(value:Number):void
| _top | property |
protected var _top:Number = NaN
| top | property |
top:Number
[read-write]Anchor padding from the top of the container.
Implementation public function get top():Number
public function set top(value:Number):void
| _verticalCentre | property |
protected var _verticalCentre:Number = NaN
| verticalCentre | property |
verticalCentre:Number
[read-write]Anchor padding from the vertical centre of the container.
Implementation public function get verticalCentre():Number
public function set verticalCentre(value:Number):void
| LayoutComponent | () | constructor |
public function LayoutComponent()
Constructor.
| addChild | () | method |
public override function addChild(child:DisplayObject):DisplayObject
Parameters
child:DisplayObject |
DisplayObject |
| createChildren | () | method |
protected function createChildren():void
Called when the component is added to the stage.
| removeChild | () | method |
public override function removeChild(child:DisplayObject):DisplayObject
Parameters
child:DisplayObject |
DisplayObject |
| removeChildren | () | method |
public function removeChildren():void
Called when the component is removedfrom the stage.
| updateDisplay | () | method |
public function updateDisplay():void
Called when the component display changes.
| updateProperties | () | method |
public function updateProperties():void
Called when the component properties change.


This simulation is designed to teach you about gradient descent. Click on the green below to create points in a dataset. Once you have more than two (2) points, you create a regression line. As more points are added, the program uses gradient descent to find the regression line of those points by adjusting the m and b values in the line equation y=mx+b . Play around with this!
For more info, visit these links:


Struct RPCRequest
An RPC request constructed by the client to send to the RPC server.
struct RPCRequest
;
The RPCRequest contains the ID of the request, the method to call, and any parameters to pass to the method. You should not need to manually create an RPCRequest object; the RPCClient will do this for you.
Constructors
| Name | Description |
|---|---|
this
|
Construct an RPCRequest with the specified remote method name and arguments. |
this
|
Construct a notification with the specified remote method name and arguments. |
Properties
| Name | Type | Description |
|---|---|---|
id [get]
|
auto | Get the ID of this request. |
idType [get]
|
std | Get the type of the underlying ID. There is no type for notifications. |
isNotification [get]
|
bool | Return true if this request is a notification; otherwise, return false. |
method [get]
|
string | Retrieve the method to execute on the RPC server. |
method [set]
|
string | Specify the method to execute on the RPC server. |
params [get]
|
std | Retrieve the parameters that will be passed to the method. |
params [set]
|
std | Set the parameters to the remote method that will be called. |
params [set]
|
string | Set the parameters to the remote method as a JSON string. |
protocolVersion [get]
|
string | Get the JSON-RPC protocol version. |


About Me
My name is Blenda Orellana and I'm 30 years old.
I have just started
learning how to code through this bootcamp.
I'm very excited to keep
learning and to become a developer.

Work
Project 1 - Cocktails, Cuisine & Craft Beers
Deployed Website Link:GitHub Repo: https://github.com/neilburt/group-project-2.git
Project 2 - Event Organizer
Deployed Website Link: https://gentle-reaches-60799.herokuapp.com/GitHub Repo: https://github.com/neilburt/group-project-2.git
Contact Me
-
LinkedIn Profile:
http://www.linkedin.com/in/blenda-orellana -
GitHub Profile:
https://github.com/blen90 -
Email:
blen.or90@gmail.com


Digital Library
Your Personal Collection
Search, organize, and display your collection of books.
View Books
Bookcase
Learning React
Alex Banks,Eve Porcello
Info
Automate the Boring Stuff with Python
Al Sweigart
Info
JavaScript: The Good Parts
Douglas Crockford
Info
JavaScript and JQuery
Jon Duckett
Info
Search
Results


---
creation_epoch:<PHONE_NUMBER>
lastmod_epoch:<PHONE_NUMBER>
categories: Programming
title: Boost C++ libraries on Windows with MinGW
---
I like to use Boost because it makes cross-platform programming easier. I also prefer to use a non-Visual Studio compiler such as MinGW. I needed to install the Boost headers (latest version) along with compiling the extended libraries. I outline the steps below (at the time I used Boost 1.48.0):
Prerequistes
- Boost
- MinGW with MSYS - I used the nice auto-installer. You could also use Visual C++ as your compiler
- MinGW & MSYS in your path (for my system it was C:\mingw\msys\1.0\bin;C:\mingw\bin)
- Lots of time to wait on the compile
Steps
- Extract Boost somewhere (takes a while)
- I used C:\boost_1_48_0 to avoid spaces in paths
- Open a command prompt (cmd) and go to C:\boost_1_48_0\tools\build\v2
- gcc --version to make sure it is in your path
- bootstrap.bat gcc
- b2.exe install --prefix=C:\boost_1_48_0
- set PATH=%PATH%;C:\boost_1_48_0\bin
- b2 -j4 toolset=gcc --build-type=complete stage
- Note that -j4 means use 4 cores. Adjust as needed.
- Your compiled libs will be in C:\boost_1_48_0\stage\lib


They have no news about MP detained by AA: official
by Aung Thu Tun (Kalay)
About ten villages in Paletwa Township, Chin State are destroyed due to fighting and they have received no information of MP Hwei Tin yet, said Soe Htet, minister for development affairs, electricity and industry for the state.
“The villages are destroyed by the fighting occurred between army and Arakan Army (AA). The villagers are not dared to stay in their village as the AA entered and exited in their village every time. Schools in the villages are also closed and villagers are moved to other places. Some moved to Thiki Village, Htantalan Township. The government relocated the IDPs in low cost housing and provided food. We haven’t heard of the MP detained by the AA,” said the minister.
About 100 IDPs from 20 family households from Mipha area in Paletwa are now living at Thiki Village.
About 6,000 IDPs are living in Paletwa Township but they are not living in camps like the IDPs stayed in Rakhine State. They are only living in their relative homes.
IDPs arrived near Mizar Village in the township due to the fighting since two years ago and now the number of IDPs is increased to about 1,200, said the minister.
The authorities have issued Section 144 in the township and the number of IDPs is increased at the present due to the fighting.


Code care
Home
Code Editor
Products
Physical Exercises
Please enter your infomation to place your order:
Name
Phone number
E-mail


{% extends 'base.html'%}
Hello, "Welcome to the Blogs ". by Benard Akaka
{{quote.quote}}
Author:- {{quote.author}}


admin
The admin module provides administrative and utility functionality for the application.
-
fileInputService: reads a file from the local file system


Copyright © 2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use, and software licensing rules apply.
This paper addresses and attempts to clarify two issues pertaining to URIs, and presents recommendations. Section 1 addresses how URI space is partitioned and the relationship between URIs, URLs, and URNs. Section 2 describes how URI schemes and URN namespace ids are registered. Section 3 mentions additional unresolved issues not considered by this paper and section 4 presents recommendations.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C in a list of current W3C technical reports at http://www.w3.org/TR/ .
This is a report from the W3C/IETF URI Planning Interest Group, for review by W3C members, the IETF community, and other interested parties. We invite review and discussion of our recommendations for future work in the IETF and/or W3C. Please address your feedback to<EMAIL_ADDRESS>a mailing list with public archive.
This document has been produced as part of the W3C URI Activity.
There is some confusion in the web community over the partitioning of URI space, specifically, the relationship among the concepts of URL, URN, and URI. The confusion owes to the incompatibility between two different views of URI partitioning, which we call the "classical" and "contemporary" views.
During the early years of discussion of web identifiers (early
to mid 90s), people assumed that an identifer type would be cast
into one of two (or possibly more) classes. An identifier might
specify the location of a resource (a URL) or its name (a URN)
independent of location. Thus a URI was either a URL or a URN.
There was discussion about generalizing this by addition of a
discrete number of additional classes; for example, a URI might
point to metadata rather than the resource itself, in which case
the URI would be a URC (citation). URI space was thus viewed as
partitioned into subspaces: URL and URN, and additional subspaces,
to be defined. The only such additional space ever proposed was URC
and there never was any buy-in; so without loss of generality it's
reasonable to say that URI space was thought to be partitioned into
two classes: URL and URN. Thus for example, "http:
"
was a URL scheme, and "isbn:
" would (someday) be a URN
scheme. Any new scheme would be cast into one or the other of these
two classes.
Over time, the importance of this additional level of hierarchy
seemed to lessen; the view became that an individual scheme does
not need to be cast into one of a discrete set of URI types such as
"URL", "URN", "URC", etc. Web-identifer schemes are in general URI
schemes; a given URI scheme may define subspaces. Thus
"http:
" is a URI scheme. "urn:
" is also a
URI scheme; it defines subspaces, called "namespaces". For example,
the set of URNs of the form "urn:isbn:n-nn-nnnnnn-n
"
is a URN namespace. ("isbn
" is an URN namespace
identifier. It is not a "URN scheme" nor a "URI scheme").
Further according to the contemporary view, the term "URL" does
not refer to a formal partition of URI space; rather, URL is a
useful but informal concept: a URL is a type of URI that identifies
a resource via a representation of its primary access mechanism
(e.g., its network "location"), rather than by some other
attributes it may have. Thus as we noted, "http:
" is a
URI scheme. An http URI is a URL. The phrase "URL scheme" is now
used infrequently, usually to refer to some subclass of URI schemes
which exclude URNs.
The body of documents (RFCs, etc) covering URI architecture, syntax, registration, etc., spans both the classical and contemporary periods. People who are well-versed in URI matters tend to use "URL" and "URI" in ways that seem to be interchangable. Among these experts, this isn't a problem. But among the Internet community at large, it is. People are not convinced that URI and URL mean the same thing, in documents where they (apparently) do. When one sees an RFC that talks about URI schemes (e.g. [RFC 2396]), another that talks about URL schemes (e.g. [RFC 2717]), and yet another that talks of URN schemes ([RFC 2276]) it is natural to wonder what's the difference, and how they relate to one another. While RFC 2396 1.2 attempts to address the distinction between URIs, URLs and URNs, it has not been successful in clearing up the confusion.
This section examines the state of registration of URI schemes and URN namespaces and the mechanisms by which registration currently occurs.
The official register of URI scheme names is maintained by IANA,
at http://www.iana.org/assignments/uri-schemes . For each scheme,
the RFC that defines the scheme is listed, for example
"http:
" is defined by [RFC
2616]. The table currently lists 30 schemes. In addition, there
are a few "reserved" scheme names; at one point in time these were
intended to become registered schemes but have since been
dropped.
We distinguish between public (unregistered) and private schemes. A public scheme (registered or not), is one for which there is some public document describing it.
Dan Connolly maintains a list of known,
public URI schemes, both registered and un-registered, a total of
84 schemes. 50 or so of these are unregistered (not listed in the
IANA register). Some may be obsolete (for example, it appears that
"phone
", is obsolete, superceded by
"tel
"). Some have an RFC, but are not included in the
IANA list.
It's probably impossible to determine all of these, and it's not clear that it's worthwhile to try, except perhaps to get some idea of their number. In the minutes of the August 1997 IETF meeting is the observation that there may be 20-40 in use at Microsoft, with 2-3 being added a day, and that WebTV has 24, with 6 added per year.
[RFC 2717] specifies procedures for registering scheme names, and points to [RFC 2718] which supplies guidelines. RFC 2717 describes an organization of schemes into "trees".
A URN namespace is identified by a "Namespace ID", NID, which is registered with IANA (see 2.2.4 Registration Procedures for URN NIDs).
There are two categories of registered URN NIDs:
Informal: These are of the form "urn-<number>" where <number> is assigned by IANA. There are three registered in this category (urn-1, urn-2, and urn-3).
Formal: The official list of registered NIDs is kept by IANA at http://www.iana.org/assignments/urn-namespaces. Currently it lists eight registered NIDs:
'ietf', defined by [RFC 2648], URN Namespace for IETF Documents
'pin', defined by [RFC 3043], The Network Solutions Personal Internet Name (PIN): A URN Namespace for People and Organizations
'issn' defined by [RFC 3043], Using The ISSN as URN within an ISSN-URN Namespace
'oid' defined by [RFC 3061], A URN Namespace of Object Identifiers
'newsml' defined by [RFC 3085], URN Namespace for NewsML Resources
'oasis' defined by [RFC 3121], A URN Namespace for OASIS
'xmlorg' defined by [RFC 3120], A URN Namespace for XML.org
'publicid' defined by [RFC 3151], A URN Namespace for Public Identifiers
There are a number of pending URN NID registration requests but there is no reliable way to discover them, or their status. For example, 'isbn' and 'nbn' have been approved by the IESG and are in the RFC Editor's queue. 'isbn', as a potential URN namespace (or URI scheme), in particular has been a source of much speculation and confusion over several years. It would be helpful if there were some formal means to track the status of NID requests such as 'isbn'.
In the "unregistered" category (besides the experimental case, not described in this paper) there are bonafide NIDs that just haven't bothered to even explore the process of registration.The most prominent that comes to mind is 'hdl'. In the case of 'hdl', it has been speculated that this scheme has not been registered because it is not clear to the owners whether it should be registered as a URI scheme or as a URN namespace.
[RFC 2611] describes the mechanism to obtain an NID for a URN namespace, which is registered with IANA.
A request for an NID should describe features including: structural characteristic of identifiers (for example, features relevant to caching/shortcuts approaches); specific character encoding rules (e.g., which character should be used for single-quotes); RFCs, standards, etc, that explains the namespace structure; identifier uniqueness considerations; delegation of assignment authority, including how to become an assigner of identifiers; identifier persistence considerations; quality of service considerations; process for identifier resolution; rules for lexical equivalence; any special considerations required for conforming with the URN syntax (particularly applicable in the case of legacy naming systems); validation mechanisms (determining whether a given string is currently a validly-assigned URN; and scope (for example,"United States social security numbers").
There are additional unresolved URI issues, not considered by this paper, which we hope will be addressed by a follow-on effort. We have not attempted to completely enumerate these issues, however, they include (but are not limited to) the following:
The use of URIs as identifiers that don't actually identify network resources (for example they identify an abstract object such as an XML schema, or a physical object such as a book or even a person).
IRIs (International Resource Identifiers): the extension of URI syntax to non-ASCII.
We recommend the following:
The W3C and IETF should jointly develop and endorse a model for URIs, URLs and URNs consistent with the '"Contemporary View" described in section 1, and which considers the additional URI issues listed or alluded to in section 3.
RFCs such as 2717 ("Registration Procedures for URL Scheme Names") and 2718 ("Guidelines for new URL Schemes") should both be generalized to refer to "URI schemes" rather that "URL schemes" and, after refinement, moved forward as Best Current Practice in IETF.
The registration procedures for alternative trees should be clarified in RFC 2717.
Public but unregistered schemes should become registered, where possible. Obsolete schemes should be purged or clearly marked as obsolete.
IANA registration information should be updated:
Add 'urn' to the list of registered URI schemes with a pointer to the URN namespace registry.
Maintain status information about pending registrations (URI schemes and URN NID requests ).
Insure that it is clear that the page is the official registry, e.g., by adding a heading to the effect "This is the Official IANA Registry of URI Schemes".
The participants in the URI Planning Interest Group are:


Usage
Make sure you're using jQuery 1.8+
, then simply link to the appropriate javascript and stylesheets
<script src="/javascripts/jquery.ya-fixed-table-header.js"></script>
<link rel="stylesheet" href="/stylesheets/ya-fixed-table-header.css">
From there, just call it against a table as you would any other jQuery plugin:
$(document).ready(function(){
$("#some-table").yaFixedHeader();
});
Options
There are a few options which can be called on the plugin.
-
width
- defaults toauto
(which is 100%), but can be set to anything you'd like. -
height
- defaults toauto
(which is 100%), but can be set to anything you'd like. -
wrapClasses
- optional classes to be applied to the outer wrapper. -
headerClasses
- optional classes to be applied to the fixed header element. -
cellClasses
- optional classes to be applied to the header "cells". -
paddedTable
- adds "padding" to the left and right of the table, but keeps the header full-width.
Examples
The basic example.
| Column 1 | Column 2 | Column 3 | Column 4 | Column 5 |
|---|---|---|---|---|
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
$(document).ready(function(){
$("#example1").yaFixedHeader();
});
Adding custom classes
| Column 1 | Column 2 | Column 3 | Column 4 | Column 5 |
|---|---|---|---|---|
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
| Data 1 | Data 2 | Data 3 | Data 4 | Data 5 |
$(document).ready(function(){
$("#example2").yaFixedHeader({
wrapClasses: "custom-wrap",
headerClasses: "custom-header",
cellClasses: "custom-cell"
});
});
How it's different
I wrote this plugin because I had a very specific set of requirements for a project, and because
none of the other plugins I found worked in a way that was useful to me. Most of them duplicated
the thead
with another one, which was just bizarre, in my opinion.
This plugin instead creates an HTML5 header
element, which duplicates the html and spacing of the
th
elements contained within the thead
of a table. This makes more sense to me,
since it allows you to use border-collapsing on your tables with ease (one of my requirements).
License (MIT)
Copyright (c) 2013 Kevin Whitaker
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


Index
A B C D E F G H I J L M N O P R S T U V W X Y
All Classes|All Packages
All Classes|All Packages
All Classes|All Packages
D
- decreaseLevel() - Method in class it.polimi.ingsw.model.board.SpaceTest
- decreaseLevel(int) - Method in class it.polimi.ingsw.model.board.Space
-
Decreases the level of the space by the specified argument.
- decreaseLevel_MinLevelLimit() - Method in class it.polimi.ingsw.model.board.SpaceTest
- decreaseLevel_NegativeInput() - Method in class it.polimi.ingsw.model.board.SpaceTest
- delete() - Method in class it.polimi.ingsw.utils.StorageData
-
Delete Saved Game.
- DESCRIPTION - it.polimi.ingsw.model.enumerations.XMLName
- disconnect() - Method in class it.polimi.ingsw.network.client.Client
-
Disconnects from the server.
- disconnect() - Method in class it.polimi.ingsw.network.client.SocketClient
-
Disconnect the socket from the server.
- disconnect() - Method in interface it.polimi.ingsw.network.server.ClientHandler
-
Disconnects from the client.
- disconnect() - Method in class it.polimi.ingsw.network.server.SocketClientHandler
-
Disconnect the socket.
- DISCONNECTION - it.polimi.ingsw.network.message.MessageType
- DisconnectionMessage - Class in it.polimi.ingsw.network.message
-
Message to notify a disconnection to the other players.
- DisconnectionMessage(String, String) - Constructor for class it.polimi.ingsw.network.message.DisconnectionMessage
- displayAlert() - Method in class it.polimi.ingsw.view.gui.scene.AlertSceneController
-
Displays Alert Message Pop-Up
- displayGodInfo() - Method in class it.polimi.ingsw.view.gui.scene.GodInfoSceneController
-
Display the god's info.
- displayWinScene() - Method in class it.polimi.ingsw.view.gui.scene.WinSceneController
-
Displays the victory scene.
- DOME - it.polimi.ingsw.model.enumerations.XMLName
- DOWN - it.polimi.ingsw.model.enumerations.MoveType
All Classes|All Packages


You read the text and it says something that makes a knot in your stomach. You are almost sure it isn’t rage, but it's something that none-the-less indicates to you that the information here is an incomplete illustration of reality as you see it and you want to offer what you consider to be missing. So you do.  It is a courageous act for sure, or at least you think it is.
Once you have it out, you think you have done your part. Yet, almost instantly, a wave of insecurity washes over you. You know this is in anticipation of the responses you are likely going to receive. Sure enough, they begin to appear. You hope that perhaps someone is thanking you for clarifying their understanding. After all, you approached the topic in question clearly and in the spirit of persuing what is right.
When you read the top comment, however, you can taste the venom.  You don't understand. You took every care to say it correctly, so why the attack? You read your statement again, searching for the corner you must have turned leading to this miscommunication on your behalf, but you can't find it.
From what you can tell, this person is upset at you for challenging their firmly held beliefs on the matter. You can't really blame them, because now you feel it too. It's coiling around you like the grip of a constrictor. You feel your chest getting tighter and you begin to labour for air. You punch out a response.
Each key you press brings new thoughts about how to approach the situation. Finding the right angle is one of the harder things to do but you are careful to be respectful yet firm on your point.  Convincing this unwanted passenger to fade into the background so you can properly respond to this without insiting provocation is no easy task, but you feel you manage it to some degree. Perhaps a passive agressive phrase or two made its way into the words, but you're only human.
Time elapses after your first response. Then your companion provides one of their own. There is a back and forth for sometime before you realise two things. The first being that this person is clearly becoming more distressed as you see the words go from meerly forceful to offensive. The second thing you realise, which leaves you at even greater odds with this person, is that you were wrong.
How could you be wrong? You had spent countless hours googling everything there was to know about this subject. You had presented this idea to your friends and family in a kind of trial-by-fire and crafted it to withstand any angle that came at it. Up until this point, it had remained unbroken. Yet here you are, in your kitchen at 10pm on a Friday inspecting a clear fracture in the logic that makes up your belief system.
Begrudgingly, you accept that they actually know something that you do not. Your ego is now yelling in the backseat, urging you to retaliate. You take a moment to recompose yourself and have another beer outside with the dog. The dog does not participate in the drinking of the beer, but he is more than happy to watch. You must remember you are not here to be correct. You are here to make things better; an easy thing to forget. You are here to at least try to make things better. You sit with yourself and calm the beast.
You then return to your screen with a revised version of your argument. You feel you have repaired the damage to the idea with this strangers point. It is early days, but you think it is solid. You are careful to apologise where you knew you were wrong and to continue to push forward what you still consider to be relevant that this personality is still not understanding correctly. You are almost sure this will get through to them.
Then they call you a ‘fuckwit’ and you never hear from them again.
The internet is in some ways a repository of all the repressed thoughts of not only one generation, but anyone who is capable of learning how to use a smartphone. Some of those among us have a great deal to say and others just like to stir the pot and see what kind of reactions they will get if they say something completely outrageous. Like any useful tool created by our species, whatever fascets of ourselves we apply to it, it will amplify. Good or bad.
It can be intimidating putting your foot into the global arena. Hell, it's intimidating putting your foot into a local one. I am of the belief that even if it is unpleasant, it is important that we have the courage to say what we are thinking. The internet is one such arena where it seems incresingly the case that the forces of propaganda, fear mongering, trolling and utter misinformation are running rampant and radicalising otherwise decent people.
With all of that deception out there in the world, it is now more important than it has ever been for the common person to speak their mind, even if they are wrong because that is how you become right. You cannot consider your initial thoughts about a problem to be accurate necessarily simply based on the fact they are yours. What is more important is that you have something to contribute to the discussion that everyone involved would probably be better off if you said it. Regardless of if they agree or not. You must approach these conversations with as much humility as you can.
You know how they say sometimes short-term pain leads to long-term benefit? That's a fairly universal rule. Saving money now means more money in the future. Not murdering your boss now means less jail in the future. Saying or hearing something difficult now means more understanding and therefore better action in the future. You are doing everyone involved a favour by speaking your mind in the long run. It is probably one of the most important things any single person can do in their lives.
Don't get me wrong, this is extremely difficult. I am not very good at it myself. To be exceptional, however, is not necessarily about your success in relation to your aims, but about your efforts towards achieving those aims. If you have something to say, you should say it. But you are going to have to be prepared to fight. The reason for this is the same reason you feel the need to say it in the first place. It is because people are all just as sure of themselves as you are. It may be the case that one of you is wrong. It is more likely the case though that both of you are partially right. So add two partially right answers together and potentially learn something.
It takes a great deal of effort to convince another polarised person that there is some validity in what you think, no matter how obvious it seems to you. Of course, you may be wrong which is something else you must consider as a possibility. But until you have been offered a counter point that does make you question what you think, hold your ground.
The crew drowns if they boat is sinking but everyone is too meek to raise the alarm.


The main objective of the package is to enter a word of at least two letters based on which an Iterated Function System with Probabilities is constructed, and a two-dimensional fractal containing the chosen word infinitely often is generated via the Chaos Game. Additionally, the package allows to project the two-dimensional fractal on several three-dimensional surfaces and to transform the fractal into another fractal with uniform marginals.
| Version: | 0.3 |
| Depends: | rgl, RColorBrewer, colorRamps |
| Imports: | ggplot2, gridExtra, sphereplot, plot3D |
| Published: | 2017-07-20 |
| Author: | Manuela Schreyer, Wolfgang Trutschnig |
| Maintainer: | Manuela Schreyer <manuelalarissa.schreyer at sbg.ac.at> |
| License: | GPL-2 |
| NeedsCompilation: | no |
| CRAN checks: | ChaosGame results |
| Reference manual: | ChaosGame.pdf |
| Package source: | ChaosGame_0.3.tar.gz |
| Windows binaries: | r-devel: ChaosGame_0.3.zip, r-release: ChaosGame_0.3.zip, r-oldrel: ChaosGame_0.3.zip |
| OS X binaries: | r-release: ChaosGame_0.3.tgz, r-oldrel: ChaosGame_0.3.tgz |
| Old sources: | ChaosGame archive |
Please use the canonical form https://CRAN.R-project.org/package=ChaosGame to link to this page.


Your Origami Build Service URL includes outdated components, some are one or more major versions behind the latest release:
To upgrade, start by using the below Origami Build Service URL which requests the same components but with updated version numbers:
{{updatedBuildServiceUrl}}
Next, verify your Origami Build Service request returns component code sucessfully (try putting it in your browser's URL bar for example). See the Origami Build Service API documentation if you have any issues, for example a missing query parameter.
Then follow the migration guide for each component which has had a major release. Make the required code changes to your project, if any:


Property Type : Flat
Price : £299,995
Location : Crofton Road Orpington BR6
Presented in excellent decorative order throughout is this two double bedroom, two bathroom, garden flat.The modern fitted kitchen is open plan to the living room which boasts solid wooden floors and includes integrated appliances including a dishwasher & a washing machine. This large open plan benefits from bi folding doors onto a secluded private courtyard garden. Both bedrooms are double sized, and the family bathroom boasts a matching three piece suite a shower attachment over the bath. There is also a separate wet room. There are walnut doors throughout and wiring for Sky TV/aerial points in the living room/kitchen and both bedrooms. This apartment being only five years old, is still under a 10 year building guarantee...


public class View extends WLCHandle
| Modifier and Type | Field and Description |
|---|---|
static View |
INVALID_VIEW |
ViewPositioner |
positioner
Holds positioner information.
|
| Modifier and Type | Method and Description |
|---|---|
void |
bringAbove(View other)
Brings this view above other view.
|
void |
bringBelow(View other)
Brings this view below other view.
|
void |
bringToFront()
Brings view to the front.
|
void |
close()
Closes this view.
|
void |
focus()
Focuses this view.
|
static View |
from(com.sun.jna.Pointer handle)
Creates view from provided pointer.
|
String |
getAppId() |
WaylandClient |
getClient() |
WaylandClient |
getClient(WaylandClientFactory factory)
Gets the wayland client for this view.
|
Geometry |
getGeometry() |
long |
getMask() |
Output |
getOutput() |
View |
getParent() |
long |
getPid() |
Resource |
getResource() |
Resource |
getRole() |
String |
getShellClass() |
String |
getShellInstance() |
long |
getState() |
String |
getTitle() |
long |
getType() |
Geometry |
getVisibleGeometry() |
void |
sendToBack()
Sends this view to back.
|
static void |
setCreatedCallback(ViewCreatedCallback cb)
Sets callback to be called when view is created.
|
static void |
setDestroyedCallback(ViewDestroyedCallback cb)
Sets callback to be called when view is destroyed.
|
static void |
setFocusCallback(ViewFocusCallback cb)
Sets callback to be called when focus changes for view.
|
void |
setGeometry(long edges,
Geometry geo)
Sets geometry.
|
void |
setMask(long mask)
Sets mask.
|
static void |
setMoveToOutputCallback(ViewMoveToOutputCallback cb)
Sets callback to be called when view is moved to the output.
|
void |
setOutput(Output output)
Assign output to this view.
|
void |
setParent(View parent)
Parent this view to the parent view.
|
static void |
setPostRenderCallback(ViewPostRenderCallback cb)
Sets callback to be called when view was just rendered.
|
static void |
setPreRenderCallback(ViewPreRenderCallback cb)
Sets callback to be called before view is rendered.
|
static void |
setPropertiesUpdatedCallback(ViewPropertiesUpdatedCallback cb)
Sets callback to be called when properties of this view were changed.
|
static void |
setRequestGeometry(ViewRequestGeometryCallback cb)
Sets callback to be called when view wants to change it's geometry.
|
static void |
setRequestMoveCallback(ViewRequestMoveCallback cb)
Sets callback to be called when view requests to be moved.
|
static void |
setRequestResizeCallback(ViewRequestResizeCallback cb)
Sets callback to be called when view requests to be resized.
|
void |
setState(int state,
boolean toggle)
Sets state.
|
static void |
setStateRequestCallback(ViewStateRequestCallback cb)
Sets callback to be called when view wants to change it's state.
|
void |
setType(long type,
boolean toggle)
Set type of the view.
|
String |
toString() |
static void |
unfocus()
Unfocus all views (equivalent to
INVALID_VIEW .focus() ). |
equals, getCustomData, getHandle, hashCode, setCustomData, to
public static final View INVALID_VIEW
public final ViewPositioner positioner
public static View from(com.sun.jna.Pointer handle)
handle
- public static void setCreatedCallback(ViewCreatedCallback cb)
cb
- public static void setDestroyedCallback(ViewDestroyedCallback cb)
cb
- public static void setFocusCallback(ViewFocusCallback cb)
cb
- public static void setRequestMoveCallback(ViewRequestMoveCallback cb)
cb
- public static void setRequestResizeCallback(ViewRequestResizeCallback cb)
cb
- public static void setRequestGeometry(ViewRequestGeometryCallback cb)
setGeometry(long, Geometry)
to agree.
WARNING: Use empty callback to prevent windows to automatically change without you
agreeing to it!cb
- public static void setMoveToOutputCallback(ViewMoveToOutputCallback cb)
cb
- public static void setStateRequestCallback(ViewStateRequestCallback cb)
setState(int, boolean)
to agree.cb
- public static void setPreRenderCallback(ViewPreRenderCallback cb)
cb
- public static void setPostRenderCallback(ViewPostRenderCallback cb)
cb
- public static void setPropertiesUpdatedCallback(ViewPropertiesUpdatedCallback cb)
cb
- public Geometry getGeometry()
public View getParent()
public Output getOutput()
public long getState()
public String getTitle()
public String getShellInstance()
public String getShellClass()
public String getAppId()
public long getPid()
public long getType()
ViewType}
public Geometry getVisibleGeometry()
public long getMask()
public Resource getResource()
public WaylandClient getClient()
public WaylandClient getClient(WaylandClientFactory factory)
factory
- to create wrapper class.public Resource getRole()
public void setMask(long mask)
mask
- public void setState(int state, boolean toggle)
state
- toggle
- public void setGeometry(long edges, Geometry geo)
edges
- geo
- public void setParent(View parent)
parent
- public void setType(long type, boolean toggle)
type
- toggle
- public void setOutput(Output output)
output
- public void bringToFront()
public void focus()
public void close()
public void sendToBack()
public static void unfocus()
INVALID_VIEW
.focus()
).public void bringAbove(View other)
other
- public void bringBelow(View other)
other
-


Watch Kanye West perform for prison inmates as he brings Sunday Service to Houston jail
He's set to perform at Lakewood Church tomorrow
Kanye West performed for prison inmates as he brought his Sunday Service show to a Houston jail yesterday. Check out the footage below.
The rap star visited the Harris County Jail in Houston, Texas ahead of his appearance at televangelist Joel Osteen’s church in the city tomorrow (November 17).
According to TMZ, West and his choir turned up to the prison by surprise yesterday morning (November 15). The outlet claims that the rapper stayed for a couple of hours to play to a select group of inmates and staff members.
A professionally-shot clip shows West shaking hands with inmates as his choir sings behind. Later, he performs his 2004 hit ‘Jesus Walks’ up close and personal with the prisoners.
It’s reported that ‘Ye performed two separate sets, one for male inmates and one for female inmates. A few hundred attendees are said to have witnessed each show.
Harris County Sheriff Ed Gonzalez later posted an image of himself with West, along with the caption: “Kanye West visited us today. I know he has a busy weekend in H-Town surrounding his visit to Lakewood Church, so appreciate him and his choir spending time with us.”
See that post below.
Ahead of tomorrow’s show at Lakewood Church, West is expected to speak to Joel Osteen about his “journey to faith”. According to church spokesperson Donald Iloff Jr, up to 45,000 members could be in attendance at the event.
Earlier this week, it was revealed that West’s support for Donald Trump had been criticised by a preacher who held the rapper’s Sunday Service at his Atlantan megachurch.


I was asked to think of the user experience and design on some of my favorite sites. I definitely consider whether a site is easily-usable and easy to figure out. I don't want to have to search hard for things if there is an alternative site that is easy to figure out. I like sites that are clean, easy to understand, and not cluttered.


| Architecture | Hybrid Application |
| Application domain type | m-Health |
| Authentication | Username and Password |
| Has DB | Yes |
| Type of data storage | SQL |
| Which DB | MySQL |
| Type of data stored | Personal Information ; Confidential Data ; Critical Data |
| User Registration | Yes |
| Type of Registration | The users will register themselves |
| Programming Languages | HTML5 ; Javascript ; PHP |
| Input Forms | Yes |
| Upload Files | Yes |
| The system has logs | Yes |
| The system has regular updates | Yes |
| The system has third-party | Yes |
| System Cloud Environments | Public Cloud |
| Hardware Specification | Yes |
| HW Authentication | Basic Authentication (user/pass) |
| HW Wireless Tech | 3G ; 4G/LTE ; 5G ; Bluetooth ; Wi-Fi ; GPS ; NFC |
| Data Center Phisical Access | Yes |
Input validation is performed to ensure only properly formed data is entering the workflow in an information system, preventing malformed data from persisting in the database and triggering malfunction of various downstream components.
Implementing input validation
If it's well structured data, like dates, social security numbers, zip codes, e-mail addresses, etc. then the developer should be able to define a very strong validation pattern, usually based on regular expressions, for validating such input. If the input field comes from a fixed set of options, like a drop down list or radio buttons, then the input needs to match exactly one of the values offered to the user in the first place. Free-form text, especially with Unicode characters, is perceived as difficult to validate due to a relatively large space of characters that need to be whitelisted. The primary means of input validation for free-form text input should be:
Client Side vs Server Side Validation
Be aware that any JavaScript input validation performed on the client can be bypassed by an attacker that disables
JavaScript or uses a Web Proxy. Ensure that any input validation performed on the client is also performed on the server.
Email Validation Basics
Many web applications do not treat email addresses correctly due to common misconceptions about what constitutes
a valid address. Specifically, it is completely valid to have an mailbox address which:
Following RFC 5321, best practice for validating an email address would be to:
https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Input_Validation_Cheat_Sheet.md
An architectural decision must be made to determine the appropriate method to protect data at rest. There are such wide varieties of products, methods and mechanisms for cryptographic storage.The general practices and required minimum key length depending on the scenario listed below:
Good practices:
Recommended Algorithms: * Confidentiality algorithms: AES-GCM-256 or ChaCha20-Poly1305; * Integrity algorithms: SHA-256, SHA-384, SHA-512, Blake2; * Digital signature algorithms: RSA (3072 bits and higher), ECDSA with NIST P-384; * Key establishment algorithms: RSA (3072 bits and higher), DH (3072 bits or higher), ECDH with NIST P-384; * Application must be capable of using end-to-end encryption via SSL / TLS in relation to sensitive data in transit and at rest.
Additionally, you should always rely on secure hardware (if available) for storing encryption keys, performing cryptographic operations, etc.
Secure Cryptographic Storage Design:
Use strong approved Authenticated Encryption
CCM or GCM are approved Authenticated Encryption modes based on AES algorithm.
Use strong approved cryptographic algorithms
Use strong random numbers
The following libraries are considered weak random numbers generators and should not be used:
C library: random(), rand(), use getrandom(2) instead
Java library: java.util.Random() instead use java.security.SecureRandom instead
For secure random number generation, refer to NIST SP 800-90A. CTR-DRBG, HASH-DRBG, HMAC-DRBG are recommended
Introduction
This cheat sheet provides a simple model to follow when implementing transport layer protection for an application. Although the concept of SSL is known to many, the actual details and security specific decisions of implementation are often poorly understood and frequently result in insecure deployments. This article establishes clear rules which provide guidance on securely designing and configuring transport layer security for an application. This article is focused on the use of SSL/TLS between a web application and a web browser, but we also encourage the use of SSL/TLS or other network encryption technologies, such as VPN, on back end and other non-browser based connections.
Architectural Decision
An architectural decision must be made to determine the appropriate method to protect data when it is being transmitted. The most common options available to corporations are Virtual Private Networks (VPN) or a SSL/TLS model commonly used by web applications. The selected model is determined by the business needs of the particular organization. For example, a VPN connection may be the best design for a partnership between two companies that includes mutual access to a shared server over a variety of protocols. Conversely, an Internet facing enterprise web application would likely be best served by a SSL/TLS model.
TLS is mainly a defence against man-in-the-middle attacks. An TLS Threat Model is one that starts with the question "What is the business impact of an attacker's ability to observe, intercept and manipulate the traffic between the client and the server".
This cheat sheet will focus on security considerations when the SSL/TLS model is selected. This is a frequently used model for publicly accessible web applications.
Providing Transport Layer Protection with SSL/TLS
Benefits *
The primary benefit of transport layer security is the protection of web application data from unauthorized disclosure and modification when it is transmitted between clients (web browsers) and the web application server, and between the web application server and back end and other non-browser based enterprise components.
The server validation component of TLS provides authentication of the server to the client. If configured to require client side certificates, TLS can also play a role in client authentication to the server. However, in practice client side certificates are not often used in lieu of username and password based authentication models for clients.
TLS also provides two additional benefits that are commonly overlooked; integrity guarantees and replay prevention. A TLS stream of communication contains built-in controls to prevent tampering with any portion of the encrypted data. In addition, controls are also built-in to prevent a captured stream of TLS data from being replayed at a later time.
It should be noted that TLS provides the above guarantees to data during transmission. TLS does not offer any of these security benefits to data that is at rest. Therefore appropriate security controls must be added to protect data while at rest within the application or within data stores.
Good Practices *
Use TLS, as SSL is no longer considered usable for security;
The HTTP Strict Transport Security Header must be used and pre loaded into browsers. This will instruct compatible browsers to only use HTTPS, even if requested to use HTTP. Cookies must be marked as Secure.
Basic Requirements *
Access to a Public Key Infrastructure (PKI) in order to obtain certificates;
[https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Transport_Layer_Protection_Cheat_Sheet.md]
Authorization is the process where requests to access a particular resource should be granted or denied. It should be noted that authorization is not equivalent to authentication - as these terms and their definitions are frequently confused. Authentication is providing and validating identity. Authorization includes the execution rules that determines what functionality and data the user (or Principal) may access, ensuring the proper allocation of access rights after authentication is successful.
Web applications need access controls to allow users (with varying privileges) to use the application. They also need administrators to manage the applications access control rules and the granting of permissions or entitlements to users and other entities.
Role Based Access Control (RBAC)
Access decisions are based on an individual's roles and responsibilities within the organization or user base. An RBAC access control framework should provide web application security administrators with the ability to determine who can perform what actions, when, from where, in what order, and in some cases under what relational circumstances.
Advantages:
Problems:
Areas of caution:
Discretionary Access Control (DAC) is a means of restricting access to information based on the identity of users and/or membership in certain groups. Access decisions are typically based on the authorizations granted to a user based on the credentials he presented at the time of authentication. The owner of information or any resource is able to change its permissions at his discretion.
Advantages:
Problems:
Areas of caution:
Mandatory Access Control (MAC) Ensures that the enforcement of organizational security policy does not rely on voluntary web application user compliance. MAC secures information by assigning sensitivity labels on information and comparing this to the level of sensitivity a user is operating at.MAC is usually appropriate for extremely secure systems including multilevel secure military applications or mission critical data applications.
Advantages :
Problems :
Areas of caution :
Permission Based Access Control Is the abstraction of application actions into a set of permissions. A permission may be represented simply as a string based name, for example "READ". Access decisions are made by checking if the current user has the permission associated with the requested application action.
The has relationship between the user and permission may be satisfied by creating a direct relationship between the user and permission (called a grant), or an indirect one. In the indirect model the permission grant is to an intermediate entity such as user group.
A user is considered a member of a user group if and only if the user inherits permissions from the user group. Systems that provide fine-grained domain object level access control, permissions may be grouped into classes. The system can be associated with a class which determines the permissions applicable to the respective domain object.
In such a system a "DOCUMENT" class may be defined with the permissions "READ", "WRITE" and "DELETE"; a "SERVER" class may be defined with the permissions "START", "STOP", and "REBOOT".
Into web applications, when we expect upload of working documents from users, we can expose the application to submission of documents that we can categorize as malicious.
We use the term "malicious" here to refer to documents that embed malicious code that will be executed when another user (admin, back office operator...) will open the document with the associated application reader.
Usually, when an application expect his user to upload a document, the application expect to receive a document for which the intended use will be for reading/printing/archiving. The document should not alter is content at opening time and should be in a final rendered state.
The most common file types used to transmit malicious code into file upload feature are the following:
For Word/Excel/Powerpoint/Pdf documents:
Detect when a document contains "code"/OLE package, if it's the case then block the upload process. For Images document: Sanitize incoming image using re-writing approach and then disable/remove any "code" present (this approach also handle case in which the file sent is not an image).
Upload Verification
Upload Storage
Public Serving of Uploaded Content
Beware of "special" files
The upload feature should be using a whitelist approach to only allow specific file types and extensions. However, it is important to be aware of the following file types that, if allowed, could result in security vulnerabilities.
"crossdomain.xml" allows cross-domain data loading in Flash, Java and Silverlight. If permitted on sites with authentication this can permit cross-domain data theft and CSRF attacks. Note this can get pretty complicated depending on the specific plugin version in question, so its best to just prohibit files named "crossdomain.xml" or "clientaccesspolicy.xml".
".htaccess" and ".htpasswd" provides server configuration options on a per-directory basis, and should not be permitted.
Purpose of logging Application logging should be always be included for security events. Application logs are invaluable data for:
Identifying security incidents
Monitoring policy violations
Establishing baselines
Assisting non-repudiation controls
Providing information about problems and unusual conditions
Contributing additional application-specific data for incident investigation which is lacking in other log sources
Helping defend against vulnerability identification and exploitation through attack detection
Each log entry needs to include sufficient information for the intended subsequent monitoring and analysis. It could be full content data, but is more likely to be an extract or just summary properties.
The application logs must record "when, where, who and what" for each event.
Where to record event data
For file-based logs, apply strict permissions concerning which users can access the directories, and the permissions of files within the directories In web applications, the logs should not be exposed in web-accessible locations, and if done so, should have restricted access and be configured with a plain text MIME type (not HTML)
Which events to log
Data to exclude
User Facing Error Messages
Error messages displayed to the user should not contain system, diagnostic or debug information.
Formatting Error Messages
Error messages are often logged to text files or files viewed within a web browser.
Recommended Error Handling Design
https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Logging_Cheat_Sheet.md
Mobile devices and platforms, such as, for example, smartphones, typically provide the capability for operating system (OS), firmware (FW) and applications updates or re-installations with reduced user involvement. The user involvement may often be limited to clicking an icon or accepting an agreement. While this reduced level of involvement may provide convenience and an improved user experience, it fails to address the issue of secure user authentication.
Mobile devices and platforms, such as smartphones, typically provide features for operating system (OS), firmware (FW) upgrades, and applications or reinstallations with reduced user engagement. User engagement may be limited to clicking an icon or accepting a contract. While this reduced level of engagement can provide convenience and enhance the user experience, it does not address the issue of secure user authentication. Thus, it is necessary to create a secure channel that provides confidentiality, integrity, authentication and data updating.
Requirements for a secure software update:
Data Confidentiality: the contents of transmitted data should be kept confidential. This also includes software updates. Thus, secure channels between the mobile device and the network manager must be set up. The standard approach to keep sensitive data secret is to encrypt the data with a key that is shared only between the intended receivers;
Data integrity: it must be possible to ensure that data packets have not been modified in transit. For mobile devices, control requests, and software updates it is critically important to verify that the contents in the packets have not been tampered with;
Data Authentication: To prevent an attacker from injecting packets it is important to make sure that the receiver can verify the sender of the packets. Data authentication ensures this property such that the re- ceiver can verify that the received packets really are from the claimed sender. For example, for software updates, data authentication is needed such that the device can verify that the received software comes from a trusted source. Data authentication can be achieved using a MAC or Digital Signature;
Data Freshness: to protect against replay attacks, e.g., during the key establishment phase, the proto- col must ensure that the messages are fresh. Data freshness ensures the security property that the data is recent and that an attacker is not replaying old data.
Many social networks also offer the possibility to create additional applications that extend the functionality of the network. The two major platforms for such applications are the Facebook Platform and Open Social. While applications designed for the Facebook Platform can only be executed in Facebook, Open Social is a combined effort to allow developers to run their applications on any social network that supports the Open Social platform (e.g., MySpace and Orkut).
Requirements for a secure third-party applications:
Data Privacy;
Data Authentication;
Data Authorization.
Apps that process or query sensitive information should run in a trusted and secure environment. To create this environment, the app can check the device for the following:


[gecode-users] Adding IntActivity to space
Christian Schulte
cschulte at kth.se
Mon Feb 23 15:05:39 CET 2015
Hi Kish,
The activity value can be accessed by position. Suppose that you have
created
IntActivity a(home, x);
Then a[i] is the activity of the variable x[i].
When you display a class in the reference documentation then there is a link
named "View all members" which then displays all members including those
which are inherited.
Cheers
Christian
--
Christian Schulte, www.gecode.org/~schulte
Professor of Computer Science, KTH, cschulte at kth.se
Expert Researcher, SICS, cschulte at sics.se
-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of Kish Shen
Sent: Saturday, February 21, 2015 6:04 AM
To: cschulte at kth.se; users at gecode.org
Subject: Re: [gecode-users] Adding IntActivity to space
Hi Christian,
I began implementing support for IntActivity outside of search engine, but I
am unable to find from the documentation how to obtain the activity value
for the variables in a IntActivity object. Is it possible to get these
values?
I am not able to find this information from the MPG, and the IntActivity
class reference documentation it points to, which seems to mainly describe
how to use IntActivity with a search engine and the reference documentation
describes only the init and = member functions.
A more general question: I seem to remember I ran into a similar problem
before, where not all the member functions for a class is described in one
place in the reference documentation. Is there anyway to find all the member
functions available for a class?
Thanks and Cheers,
Kish
_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
More information about the users
mailing list


 If you don't want to receive these emails from Spotify in the future, you can edit your profileor unsubscribe. | ||
| Terms of Use Privacy Policy Contact Us | ||
| Spotify USA Inc, 45 W. 18th Street, 7th Floor, New York, NY 10011, USA | ||


ODIN Library
My Books
Add a Book
Add a New Book
Book Name
Author Name
# of Pages
Finished Book
Submmit


Assignment ID
{{ assignment.assignment_id }}
Team
{{ assignment.team }}
PKA (Pembantu Kesihatan Am)
{{ assignment.pka_full_name }}
PA (Pembantu Am)
{{ assignment.pa_full_name }}
Date
{{ assignment.date }}
Created by
{{ assignment.createdBy }}
Address
{{ assignment.address }}
Remark
{{ assignment.remark }}


Note:
-
Since CAS does not support Single Sign-Out as of now, please make sure you logout from all the applications and close the browser window when you have finished using the system.
-
IT Support will NEVER ask for your password and/or any other personal information. Please do not reply to any such mail and report them immediately to IT support
-
It is recommended you choose a strong password since this single password is your gateway to all the computing resources at IIIT-H


Home
Drill-down Report
{%if rpt_type %}
You are reviewing dogs adopted in {{year}}(year) {{month}}(month) that have been in the rescue for 60 days or more.
{%else%}
You are reviewing dogs surrendered by Animal Control Department in {{year}}(year) {{month}}(month).
{%endif%}
Dog ID
Breed
Sex
Alteration Status
Microchip ID
Surrender Date
{% if rpt_type %}
Days in the Rescue
{% endif %}
{% for row in Drill_down %}
{{row[0]}}
{{row[1]}}
{{row[2]}}
{{row[3]}}
{{row[4]}}
{{row[5]}}
{% if rpt_type %}
{{row[6]}}
{% endif %}
{% endfor %}


Tournament manager for Overwatch that seeds individual players in to evenly matched teams. TourneyWatch also allows all users, including spectators, to follow along through tournament brackets, and team roster listings. Users can also view live games via Twitch integrations, and watch highlights uploaded by the manager.
Check it outChatty is a client-side SPA (single-page app) built with ReactJS. It allows users to communicate with each other without having to register accounts.
Check it out


Article: Advective mixing in groundwater
22 Dec 2022Did you learn that streamlines in groundwater flows never intersect? This is absolutely true for two-dimensional divergence-free flows (no source, no sink). In two-dimensional, divergence-free flows the streamline geometry is deformed only locally: at a large distance upstream and downstream from subsurface heterogeneity the streamline arrangement remains exactly the same.
How do streamlines behave in three-dimensional divergence-free flows? In three-dimensional, non-axisymetric flows the streamlines are permanently rearranged by the redistribution of the fluid within the subsurface.
The intersections of stream tubes and control planes for 3-D flow past isolated inclusions: (top left) infinitely conductive sphere, (top right) prolate ellipsoid, (bottom left) oblate ellipsoid, and (bottom right) impermeable oblate ellipsoid (from Jankovic et al., 2009).
What kind of permanent rearrangement can happen?
- streamline focusing/defocusing
- depth-dependent streamline meandering (i.e. streamline deviation),
- secondary motion consisting in persistent twisting, folding, and intertwining of streamlines.
This is called advective mixing and it plays a non-negligible role in enhancing diffusion/dispersion. Modeling subsurface flow transport without accounting for three-dimensional flow and/or small scale heterogeneity will clearly underestimate the subsurface mixing processes.
For example, delineating a well capture zone based on a 2D groundwater flow model with particle tracking will result in a too narrow and unrealistic capture zone: in this capture zone a drop of water has a 100% chance to be extracted by the well and the capture zone extends up to the model boundary. In reality the capture chance is decreasing with increasing distance between the drop of water and the well: due to the 3D subsurface flow mixing a drop of water far away from the well has a low chance to reach the well.
Literature about advective mixing:
-
Hemker, K., van den Berg, E., and Bakker, M.: Ground Water Whirls, Ground Water, 42, 234?242, DOI: 10.1111/j.1745-6584.2004.tb02670.x, 2004.
-
Huber, E. and Huggenberger, P.: Subsurface flow mixing in coarse, braided river deposits, Hydrol. Earth Syst. Sci., 20, 2035?2046, DOI: 10.5194/hess-20-2035-2016, 2016.
-
Jankovic, I., Steward, D. R., Barnes, R. J., and Dagan, G.: Is transverse macrodispersivity in three-dimensional groundwater transport equal to zero? A counterexample, Water Resour. Res., 45, W08415, DOI: 10.1029/2009WR007741, 2009.
-
Steward, D. R.: Stream surfaces in two-dimensional and three-dimensional divergence-free flows, Water Resour. Res., 34, 1345?1350, DOI: 10.1029/98WR00215, 1998.