us-patent-grant
BIBLIOGRAPHIC
US
08979045
B2
20150317
:::
document-id::
US
08979045
B2
20150317
US
13573417
20120914
:::
document-id::
US
13573417
20120914
13
us-term-of-grant::
30
Classifications IPCR
-
Classification:
ipc-version-indicator::
20060101
A
A
47
B
96
06
F
I
action-date:
20150317
generating-office::
US
B
H
-
Classification:
ipc-version-indicator::
20060101
A
A
47
B
83
04
L
I
action-date:
20150317
generating-office::
US
B
H
-
Classification:
ipc-version-indicator::
20060101
A
A
47
B
37
04
L
I
action-date:
20150317
generating-office::
US
B
H
classifications-cpc
main-cpc
classification-cpc
cpc-version-indicator::
20130101
A
47
B
83
04
F
I
action-date:
20150317
generating-office::
US
B
H
C
Further CPC
-
Classification:
cpc-version-indicator::
20130101
A
47
B
37
04
L
I
action-date:
20150317
generating-office::
US
B
H
C
classification-national::
US
2482051
248250
2482402
Invention Title:: Railing extension device and method therefore
US Citations
-
US citation:
[patcit]:
document-id::
US
596427
A
Richey
18971200
cited by examiner
classification-national::
US
182106
-
US citation:
[patcit]:
document-id::
US
1531159
A
Timmons
19250300
cited by examiner
classification-national::
US
248236
-
US citation:
[patcit]:
document-id::
US
1733485
A
Desrosiers
19291000
cited by examiner
classification-national::
US
211 9403
-
US citation:
[patcit]:
document-id::
US
2889764
A
McGrath et al.
19590600
cited by examiner
classification-national::
US
454204
-
US citation:
[patcit]:
document-id::
US
2935284
A
Reeves
19600500
cited by examiner
classification-national::
US
248208
-
US citation:
[patcit]:
document-id::
US
3390477
A
Galbraith
19680700
cited by examiner
classification-national::
US
42 94
-
US citation:
[patcit]:
document-id::
US
3559941
A
Holzman
19710200
cited by applicant
-
US citation:
[patcit]:
document-id::
US
4848610
A
Lai
19890700
cited by examiner
classification-national::
US
211 9001
-
US citation:
[patcit]:
document-id::
US
4996977
A
Tiedeken
19910300
cited by examiner
classification-national::
US
128878
-
US citation:
[patcit]:
document-id::
US
5033448
A
Sandweg
19910700
cited by examiner
classification-national::
US
126 25 R
-
US citation:
[patcit]:
document-id::
US
5042767
A
Yunker et al.
19910800
cited by examiner
classification-national::
US
248201
-
US citation:
[patcit]:
document-id::
US
RE33842
E
Ebentheuer
19920300
cited by examiner
classification-national::
US
248 97
-
US citation:
[patcit]:
document-id::
US
5282595
A
Conforti
19940200
cited by applicant
-
US citation:
[patcit]:
document-id::
US
5755411
A
Strong et al.
19980500
cited by examiner
classification-national::
US
248118
-
US citation:
[patcit]:
document-id::
US
6263867
B1
Skelton
20010700
cited by examiner
classification-national::
US
126 37 B
-
US citation:
[patcit]:
document-id::
US
6398174
B1
Emalfarb
20020600
cited by examiner
classification-national::
US
248214
-
US citation:
[patcit]:
document-id::
US
6829856
B1
Moorman
20041200
cited by examiner
classification-national::
US
42 94
-
US citation:
[patcit]:
document-id::
US
8091844
B1
Bragg
20120100
cited by examiner
classification-national::
US
248208
32
1
us-field-of-classification-search
figures::
17
17
US Related Documents
us-provisional-application
document-id::
US
61573145
20110914
Related Publication
document-id::
US
20130062481
A1
20130314
us-parties
US Applicants
-
Applicant:
[addressbook]:
Petrakis
John Christopher
Ashburn
VA
US
US
Inventors
-
Inventor:
[addressbook]:
Petrakis
John Christopher
Ashburn
VA
US
Agents
-
Agent:
[addressbook]:
Rosenberg, Klein & Lee
unknown
Assignees
-
Assignee:
[addressbook]:
RLP Management Holdings, LLC
02
Franklin Lakes
NJ
US
Examiners
-
primary-examiner:
Wood
Kimberly
3631
abstract"
A railing mounting system for use on decks, balconies, fences or patios to provide
additional surface space. In addition, the frame can be used to contain plantings,
herb gardens, coolers, grills or other outdoor items. The mounting system is quickly
and easily installed for use and just as easily removed and stored for subsequent
use.
DRAWINGS
DESCRIPTION
This application claims priority to U.S. provisional patent application 61/573,145
filed Sep. 14, 2011.
BACKGROUND
1. Technical Field
The present disclosure relates generally to a railing extension device for supporting
various articles, and more specifically to a device that mounts to a railing and can
support various items, including but not limited to a beverage cooler, trash can,
a cooler, an electric grill, a glass surface for containing serving dishes and glasses,
plants and/or an herb garden.
2. Description of Related Art
Decks, balconies and patios are prevalent in homes and restaurants and often contain
a railing system of sorts to assist in providing a safety measure and barrier for
occupants as decks, balconies and patios are often above ground level and/or may be
near hazards such as water. Most decks, balconies and patios contain tables and chairs
in order to provide places for people to eat and put their beverage glasses. The addition
of tables and chairs often limits the amount of space available for people to stand
and/or walk around on. Due to this, occupants often place plates and glasses on railings.
These can easily be knocked off or slide off as the surface of the railing is not
even due to warping or in the case of balconies the railing may only be one inch wide
and therefore not useable for holding items.
To meet the problem of providing additional surface space for decks and patios, a
frame and strap system has been developed which can quickly attach to any shape or
size railing and may extend outward away from and/or inward on the deck, balcony or
patio. The frame can be made of various durable materials, including but not limited
to wood (including teak), aluminum, wrought iron, stainless steel, titanium, or a
polymer/plastic material. The device has a rectangular frame shape, but could be square,
circular, triangular or any polygonal shape if desired. In addition, the device can
have one or more points of contact between the railing and the proximal portion of
the frame for attachment of the device. One benefit of the device is its ability to
adjust and attach to various shaped railings and various sized railings. The device
also contains another member which is an additional point of contact from the frame
to the floor/base of the deck, balcony or patio. This member is angled from the most
external/distal portion of the frame to the base/floor. This member can be telescoping
and can be attached to the frame via a hinge in order to allow for it to fold up and
minimize space of the device when not in use. This member or leg could also occur
on both sides of the device, with the second member/leg contacting the bottom horizontal
brace of the railing or balcony.
Therefore, a need exists for a lightweight device that can quickly, easily and releasably
attach to a railing, fence or the like, to provide additional surface area and/or
additional display area for occupants to place various items including but not limited
to food items or glasses.
SUMMARY
The present disclosure is directed to a railing extension device which provides a
support frame that releasably attaches to a railing. The device can quickly and easily
be attached to a railing or fence and then when it is no longer in use it can just
as quickly and easily be removed and stored. The preferred embodiment of the device
contains two brackets that mount to the proximal portion of the support frame (hereinafter
frame). These brackets are permanently attached to the frame and contain an L shaped
protrusion which accommodates a strap or cable member. The L shaped bracket could
be replaced with various other well known means for holding the strap or cable in
place and work just as efficiently. The strap or cable can be made from a variety
of materials, including but not limited to nylon, rubber (synthetic or natural) or
stainless steel. The strap member continues through a cinching buckle and can be tightened
accordingly to maintain the position of the frame. The cinching buckle could also
be replaced with other well known means for holding tension on a cable or strap and
work just as well. Other types of tightening mechanisms can be used to tighten and
secure the strap to the desired tension, including but not limited to a wench type
mechanism, a rack and pinion type mechanism, or a spring loaded clamp mechanism. The
strap from the buckle is attached at its other end to a U-shaped bracket. The U shaped
bracket is moveable and can be of various lengths, widths and sizes and resides sandwiched
between the frame and the railing. This allows the weight of whatever is put on top
of the frame to further anchor the device to the railing.  The pin
resides in the slots and keeps the U shaped bracket locked in place. Lastly, the distal
portion of the frame has a telescoping member or leg that is pivotally attached to
the frame. Once extended, the leg contacts the surface of the deck, balcony or patio
to provide additional support for the frame.
In another embodiment the device could contain drop in compartments for various items,
including but not limited to a cutting board and utensils. It is also contemplated
that the device could be adapted for marine applications as well as tailgating applications
or with fences that have a horizontal cross member.
Description of drawings
BRIEF DESCRIPTION OF THE DRAWINGS
The above and other aspects and features of the present disclosure will become more
apparent in light of the following detailed description when taken in conjunction
with the accompanying drawings in which:
figref[FIG. 1]
is an exploded assembly view of the Deckmate device
figref[FIG. 2]
is an isometric view of the Deckmate device
figref[FIG. 3]
is an exploded view of the telescoping leg assembly
figref[FIG. 4]
is a close up view of the strap and buckle assembly
figref[FIG. 5A]
is a close up view of the L bracket assembly, the Deckmate device facing outward
from the railing
figref[FIG. 5B]
is a close up view of the Deckmate device attached to the railing and facing inward
from the railing
figref[FIG. 6]
is a close up view of the Deckmate in use holding a cooler
figref[FIG. 7]
is a second close up view of the Deckmate in use holding a cooler
figref[FIG. 8]
is a close up view of the Deckmate spanning space inside and outside the railing
figref[FIG. 9]
is an isometric view of the frame
figref[FIG. 10]
is an isometric view of the glass insert for the frame
figref[FIG. 11]
is a bottom view of the frame with a mesh top insert
figref[FIG. 12]
is an isometric view of the L bracket
figref[FIG. 13]
is an isometric view of the U bracket
figref[FIG. 14]
is an isometric view of the tabs that support the glass insert with the frame
figref[FIG. 15]
is an isometric view of the top portion of the telescoping leg
figref[FIG. 16]
is an isometric view of the bottom portion of the telescoping leg
DETAILED DESCRIPTION OF THE EMBODIMENTS
Particular embodiments of the present disclosure will be described herein with reference
to the accompanying drawings. As shown in the drawings and as described throughout
the following description, and as is traditional when referring to relative positioning
on an object, the terms “proximal” and “trailing” may be employed interchangeably,
and should be understood as referring to the portion of a structure that is closer
to a user during proper use. The terms “distal” and “leading” may also be employed
interchangeably, and should be understood as referring to the portion of a structure
that is farther from the user during proper use.
Referring initially to figref[FIGS. 1 and 2]
, the rail mounting system
10 consists of a frame
20. The frame
20 can be various shapes, but is D-shaped in the preferred embodiment. In the preferred
embodiment there are two first strap brackets with an L shaped feature, herein after
called the L brackets
30 which are permanently mounted to the proximal portion of the frame
20 with the use of Phillips head screws, but could also be mounted with various well
known techniques including but not limited to riveting and welding. Referring additionally
to figref[FIGS. 4]
,
5A,
5B,
12 and
13, the L brackets
30 utilize this L shaped member to contain the strapping
70 and use the vertical portion
74 of the L shape to prevent it from sliding off the L bracket
30. The strapping
70, defining a first strap member, continues and connects to a cinching type buckle
72 which connects to a second strap member, the second piece of strapping
75, that together form a first adjustable strap assembly
71. From the buckle
72 the second piece of strapping
75 connects to a second strap bracket
30
a of a U shaped bracket
40 so that the buckle
72 can be tightened accordingly to maintain the position of the frame. Preferably, two
U shaped brackets
40 are used and they are placed between the railing
80 and the frame
20, thus looping the strapping
70 and
75 around the railing
80. The U shaped bracket
40 contains a slot
46 on either side to accommodate detent pin
42 which is used to attach the U shaped bracket
40 to the frame
20. As noted in figref[FIG. 2]
, the frame
20 has adjustment holes
24 to accommodate various placement locations of the U shaped bracket
40. Once the U shaped bracket
40 is in place, the strapping
70,
75 can be tightened to secure the frame
20 to the railing
80. The placement of the U shaped bracket
40 under the frame
20 and on top of the railing
80 serves a unique purpose in that it allows for the weight that is placed on the frame
20 to further secure the frame
20 in place.
The frame
20 also contains a post feature
25 on its distal side. The post feature
25 comprises two upright members
26 which have a through hole
27 for detent pin
28 to reside. The post
25 mates with a telescoping leg
50, whereby its proximal end also contains a through hole
53 to mate with detent pin
28. The telescoping leg
50 contains adjustment holes
56 along its length to accommodate various heights between railing
80 and floor
90. The adjustment holes
56 utilize detent pin
57 and through hole
54 on the upper leg portion to lock the telescoping leg
50 into place. The telescoping leg
50 also has a foot
52 which rests on the floor surface
90. The foot
52 consists of an L shape rigid member that rests on both the top and side surface of
the floor
90. The foot
52 may also be screwed into place into the floor surface to prevent any movement of
the telescoping leg
50. It is also contemplated that this foot
52 could be angularly adjustable to accommodate various unevenness that may occur with
floor surfaces
90. The telescoping leg
50 provides additional support for the railing mounting system
10, much like a tripod would by providing a third support point. It is also contemplated
that there could be more than one telescoping leg to support the frame. The legs may
be all on the same side of the frame or on both the proximal and distal ends of the
frame.
Lastly, the frame
20 contains securing tabs
62 that are mounted to the frame
20 by screws
63. A piece of glass
60 or metal mesh
61 is fitted to match the shape of the frame
20 is placed into the top of the frame
20 and the securing tabs
62 are placed over the glass
60 and alongside the side of the frame
20 and are screwed into place to prevent the glass
60 from moving.
The rail mounting system
10 can be utilized for supporting various items including glassware, plates, centerpieces,
candles etc. The rail mounting system
10 is designed to be easily removed from the railing
80 and stored for future use. The various detent pins
28,
42 and
57 need just be removed and the telescoping leg
50 retracted, and the frame
20 with the glass
60 secured in place can be lifted off the railing
80 and the unit stored for later use.
In another embodiment, see figref[FIGS. 6 and 7]
, the third strap member
70
a and fourth strap member
75
a of each of a pair of second adjustable strap assemblies
71
a span from the proximal part of the frame
20 to the distal part of the frame
20 and hangs loosely between the two ends of the frame
20. The third strap member
70
a and fourth strap member
75
a each being coupled to a respective fixed strap bracket with an L shaped feature
30
b. Next a cooler can be placed through the frame
20 and into contact with the third strap member
70
a and fourth strap member
75
a such that the bottom surface of the cooler touches the top surface of the strapping
third strap member
70
a and fourth strap member
75
a and holds the cooler upright with the additional support of the frame
20.
In another embodiment, the frame and brackets could be formed monolithically.
In yet another embodiment, the frame
20 may span both inside and outside the deck, balcony or patio perimeter as noted in
figref[FIG. 8]
. As shown, the frame
20 is secured to the railing
80 with a pair of adjustable strap assemblies
71, each adjustable strap assembly
71 connects between a first U shaped bracket
40 and second U shaped bracket
40
a that are each coupled to the frame
20 by respective detent pins
42 to oppose one another. This provides more surface area for containing various items
including but not limited to a drop in tray that may contain recesses for holding
utensils or for various herbs. This embodiment contains two telescoping arms
50 to provide support on both sides of the railing
80 since the frame
20 spans across both sides of the railing
80. The telescoping arm
50 that resides inside the railing rests on the bottom horizontal cross member of the
railing, as depicted in figref[FIGS. 5B and 8]
.
In yet another embodiment, the device may be installed such that it is extending inward
from the railing as depicted in figref[FIG. 5B]
, to serve as a table or countertop for instance.
What is claimed is:
CLAIMS
claim
CLAIM-TEXT
1. A railing extension device, comprising:
CLAIM-TEXT:a frame member having a closed contour;
CLAIM-TEXT:at least a first pair of U shaped brackets secured to the frame member, each of the
first pair of U shaped brackets being adjustably and releasably coupled to the frame
member in a selected one of a plurality of positions;
CLAIM-TEXT:a pair of first adjustable strap assemblies for securing the frame member to a railing
structure, each of the first adjustable strap assemblies having at least one portion
thereof coupled to a respective one of the first pair of U shaped brackets; and
CLAIM-TEXT:at least one telescoping leg member pivotally coupled to the frame and extending therefrom
to a supporting surface.
claim
CLAIM-TEXT:2. The railing extension device of claim-ref[claim 1]
, where each of the pair of first adjustable strap assemblies includes a first strap
member having one end thereof coupled to the frame, a second strap member having one
end thereof coupled to a corresponding one of the first pair of U shaped brackets,
and a first fastening device for releasably securing another end of the first strap
member to another end of the second strap member.
claim
CLAIM-TEXT:3. The railing extension device of claim-ref[claim 1]
, where at least a portion of the frame overlays the railing structure and each of
the first pair of U shaped brackets is located with a portion thereof disposed between
the railing structure and the frame and thereby weight on the railing extension device
further secures the first pair of U shaped brackets in position.
claim
CLAIM-TEXT:4. The railing extension device of claim-ref[claim 2]
, where the frame includes at least a pair of first strap brackets affixed thereto,
the one end of the first strap member of each of the pair of first adjustable strap
assemblies is connected to a corresponding one of the first strap brackets.
claim
CLAIM-TEXT
5. A method for securing a railing extension device to a railing, comprising the steps
of:
CLAIM-TEXT:providing a frame member having a pair of U shaped brackets where each is adjustably
and releasably coupled to the frame member in a selected one of a plurality of positions,
and at least a pair of adjustable strap assemblies having an end portion thereof coupled
to a respective one of the first pair of U shaped brackets and an opposing end portion
coupled to the frame;
CLAIM-TEXT:positioning the frame to extend horizontally across an upper portion of the railing;
CLAIM-TEXT:adjusting a position of each of the pair of U shaped brackets to overlay the upper
portion of the railing;
CLAIM-TEXT:extending each of the pair of adjustable strap assemblies around the upper portion
of the railing to capture the upper portion of the railing between each of the pair
of U shaped brackets and a corresponding adjustable strap assembly;
CLAIM-TEXT:securing the frame member to the railing by tightening each of the pair of strap assemblies;
and
CLAIM-TEXT:extending at least one telescoping leg member to extend from the frame to a supporting
surface.
claim
CLAIM-TEXT:6. The railing extension device of claim-ref[claim 4]
, where each of the first strap brackets includes an L shaped tab having (a) a longitudinally
extended portion for receiving a portion of the one end of a corresponding one of
the first strap members thereon, and (b) a portion disposed at a distal end of the
longitudinally extended portion extending transverse thereto for retaining the one
end of the first strap member on the L shaped tab.
claim
CLAIM-TEXT:7. The railing extension device of claim-ref[claim 4]
, where each of the first pair of U shaped brackets includes a second strap bracket
extending therefrom, the second strap bracket including an L shaped tab having (a)
a longitudinally extended portion for receiving a portion of the one end of a corresponding
one of the second strap members thereon, and (b) a portion disposed at a distal end
of the longitudinally extended portion extending transverse thereto for retaining
the one end of the second strap member on the L shaped tab.
claim
CLAIM-TEXT:8. The railing extension device of claim-ref[claim 1]
, further comprising a second pair of U shaped brackets secured to the frame member,
each of the second pair of U shaped brackets being adjustably and releasably coupled
to the frame member in a selected one of a plurality of positions, each of the first
adjustable strap assemblies being coupled between corresponding ones of the first
and second pairs of U shaped brackets.
claim
CLAIM-TEXT:9. The railing extension device of claim-ref[claim 8]
, where each of the pair of first adjustable strap assemblies includes a first strap
member having one end thereof coupled to a respective one of the U shaped brackets
of one of the pairs of the first and second pairs of U shaped brackets, a second strap
member having one end thereof coupled to a corresponding one of the U shaped brackets
of the other of the pairs of the second and first pairs of U shaped brackets, and
a first fastening device for releasably securing another end of the first strap member
to another end of the second strap member.
claim
CLAIM-TEXT:10. The railing extension device of claim-ref[claim 9]
, where each of the first and second pairs of U shaped brackets includes a strap bracket
extending therefrom, the strap bracket including an L shaped tab having (a) a longitudinally
extended portion for receiving a portion of the one end of a corresponding one of
the first and second strap members thereon, and (b) a portion disposed at a distal
end of the longitudinally extended portion extending transverse thereto for retaining
the one end of the corresponding one of the first and second strap members on the
L shaped tab.
claim
CLAIM-TEXT:11. The railing extension device of claim-ref[claim 1]
, where a pair of telescoping leg members are each pivotally coupled to the frame
and extend therefrom to a supporting surface, a first of the pair of telescoping leg
members being pivotally coupled to one side of the frame and a second of the pair
of telescoping leg members being pivotally coupled to an opposing side of the frame.
claim
CLAIM-TEXT
12. The railing extension device of claim-ref[claim 1]
, further comprising:
CLAIM-TEXT:a panel member overlaying the frame; and
CLAIM-TEXT:a plurality of securing tab members secured to the frame and clampingly engaging the
panel member.
claim
CLAIM-TEXT:13. The railing extension device of claim-ref[claim 12]
, where the panel member is formed of one of a transparent or mesh material.
claim
CLAIM-TEXT:14. The railing extension device of claim-ref[claim 12]
, where each of the securing tab members have an inverted L shaped contour.
claim
CLAIM-TEXT
15. The railing extension device of claim-ref[claim 10]
, further comprising:
CLAIM-TEXT:at least a pair of fixed strap brackets respectively coupled to opposing sides of
the frame;
CLAIM-TEXT:at least a second adjustable strap assembly coupled between the pair of fixed strap
brackets for supporting an article thereon to be accessible through an open area circumscribed
by the frame.
claim
CLAIM-TEXT:16. The railing extension device of claim-ref[claim 15]
, where the second adjustable strap assembly includes a third strap member having
one end thereof coupled to a respective one of the pair of fixed strap brackets, a
fourth strap member having one end thereof coupled to the other of the pair of fixed
strap brackets, and a second fastening device for releasably securing another end
of the third strap member to another end of the fourth strap member.
claim
CLAIM-TEXT:17. The railing extension device of claim-ref[claim 16]
, where each of the fixed strap brackets includes an L shaped tab having (a) a longitudinally
extended portion for receiving a portion of the one end of a corresponding one of
the third and fourth strap members thereon, and (b) a portion disposed at a distal
end of the longitudinally extended portion extending transverse thereto for retaining
the one end of the corresponding one of the third and fourth strap members on the
L shaped tab.
claim
CLAIM-TEXT:18. The railing extension device of claim-ref[claim 15]
, where a plurality of pairs of fixed strap brackets are coupled to the frame and
a corresponding number of second adjustable strap assemblies extend between a corresponding
pair of fixed strap brackets to span between opposing sides of the frame for supporting
an article thereon to be accessible through an open area circumscribed by the frame.
claim
CLAIM-TEXT:19. The method of claim-ref[claim 5]
, where the step of providing a frame member includes the step of providing at least
a pair of strap brackets coupled to the frame, each strap bracket having an L shaped
tab for retaining the opposing end portion of a corresponding one of the pair of adjustable
strap assemblies thereon.
claim
CLAIM-TEXT:20. The method of claim-ref[claim 5]
, further comprising the step of securing a panel member to the frame member.
claim
CLAIM-TEXT:21. The method of claim-ref[claim 20]
, where the step of securing a panel member includes the steps of overlaying the panel
member on the frame and using a plurality of securing tab members to clampingly couple
the panel member to the frame.
claim
CLAIM-TEXT
22. A method for securing a railing extension device to a railing, comprising the
steps of:
CLAIM-TEXT:providing a frame member having a first pair of U shaped brackets and a second pair
of U shaped brackets where each U shaped bracket is adjustably and releasably coupled
to the frame member in a selected one of a plurality of positions, and at least a
pair of adjustable strap assemblies each having an end portion thereof coupled to
a respective one the U shaped brackets of the first pair of U shaped brackets and
an opposing end portion coupled to a corresponding one of the U shaped brackets of
the second pair of U shaped brackets;
CLAIM-TEXT:positioning the frame to extend horizontally across an upper portion of the railing;
CLAIM-TEXT:adjusting a position of each of the U shaped brackets of the first and second pairs
of U shaped brackets to overlay the upper portion of the railing;
CLAIM-TEXT:extending each of the pair of adjustable strap assemblies around the upper portion
of the railing to capture the upper portion of the railing between the U shaped brackets
of the first and second pairs of U shaped brackets and a corresponding one of the
adjustable strap assemblies;
CLAIM-TEXT:securing the frame member to the railing by tightening a respective buckle of each
of the pair of strap assemblies; and
CLAIM-TEXT:extending at least one telescoping leg member to extend from the frame to a supporting
surface.
claim
CLAIM-TEXT:23. The method of claim-ref[claim 22]
, further comprising the step of securing a panel member to the frame member.
claim
CLAIM-TEXT:24. The method of claim-ref[claim 23]
, where the step of securing a panel member includes the steps of overlaying the panel
member on the frame and using a plurality of securing tab members to clampingly couple
the panel member to the frame.
claim
CLAIM-TEXT
25. A railing extension device, comprising:
CLAIM-TEXT:a frame member having a closed contour with at least a portion thereof being disposed
in overlaying relationship with an upper portion of a railing structure;
CLAIM-TEXT:at least a first pair of U shaped brackets secured to the frame member, each of the
first pair of U shaped brackets having a portion thereof disposed between the upper
portion of the railing structure and the frame so that weight on the railing extension
device further secures the first pair of U shaped brackets in position;
CLAIM-TEXT:at least a pair of adjustable strap assemblies for securing the frame member to the
upper portion of the railing structure, each of the adjustable strap assemblies extending
around a lower portion of the upper portion of the railing structure and having at
least one portion thereof coupled to a respective one of the first pair of U shaped
brackets; and
CLAIM-TEXT:at least one telescoping leg member pivotally coupled to the frame and extending therefrom
to a supporting surface.
claim
CLAIM-TEXT:26. The railing extension device of claim-ref[claim 25]
, where each of the first pair of U shaped brackets is adjustably and releasably coupled
to the frame member in a selected one of a plurality of positions.
claim
CLAIM-TEXT:27. The railing extension device of claim-ref[claim 25]
, where the frame includes at least a pair of first strap brackets affixed thereto,
a first end portion of each of the pair of adjustable strap assemblies being connected
to a corresponding one of the strap brackets.
claim
CLAIM-TEXT:28. The railing extension device of claim-ref[claim 26]
, where each of the first pair of U shaped brackets has a second strap bracket extending
therefrom, a second end portion of each of the pair of adjustable strap assemblies
being connected to a corresponding one of the second strap brackets.
claim
CLAIM-TEXT:29. The railing extension device of claim-ref[claim 25]
, further comprising a second pair of U shaped brackets secured to the frame member,
each of the adjustable strap assemblies being coupled between corresponding ones of
the first and second pairs of U shaped brackets.
claim
CLAIM-TEXT:30. The railing extension device of claim-ref[claim 29]
, where each of the second pair of U shaped brackets has a portion thereof disposed
between the upper portion of the railing structure and the frame.
claim
CLAIM-TEXT:31. The railing extension device of claim-ref[claim 29]
, where each of the second pair of U shaped brackets is adjustably and releasably
coupled to the frame member in a selected one of a plurality of positions.
claim
CLAIM-TEXT:32. The railing extension device of claim-ref[claim 29]
, where each of the first and second pair of U shaped brackets has a strap bracket
extending therefrom, each of the pair of adjustable strap assemblies being connected
between the strap brackets of corresponding ones of the first and second pairs of
U shaped brackets.


| Interface | Description |
|---|---|
| ProgressListener |
This interface establishes a protocol to observe a given process.
|
| Class | Description |
|---|---|
| CounterClock |
This class shows a time counter (counter clock) in text form "hours: minutes: seconds".
|
| DraggableTabbedPane |
This class represents a graphic user interface (GUI) component as a
JTabbedPane whose tabs can be dragged. |
| HelpContent |
This is the dialog showing help content of Hudup framework.
|
| JCheckList<E> |
This class creates a graphic user interface (GUI) component as a
JList (list box) whose items are check boxes. |
| JRadioList<E> |
This class creates a graphic user interface (GUI) component as a list of radio buttons.
|
| ProgressDlg |
This graphic user interface (GUI) component shows a progress dialog.
|
| ProgressEvent |
For example, there is an application
A whose process is to copy file. |
| SortableTable |
JCommon : a free general purpose class library for the Java(tm) platform.
(C) Copyright 2000-2005, by Object Refinery Limited and Contributors. Project Info: http://www.jfree.org/jcommon/index.html This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
| SortableTableModel |
JCommon : a free general purpose class library for the Java(tm) platform
(C) Copyright 2000-2005, by Object Refinery Limited and Contributors. Project Info: http://www.jfree.org/jcommon/index.html This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
| TooltipTextArea |
The graphic user interface (GUI) component as a text area shows a tool-tip.
|
| UIUtil |
This utility class provides utility methods relevant to user interface (UI) such as getting image from URI, creating button, and creating menu item.
|
| UriChooser |
This graphic user interface (GUI) component shows a dialog for users to choose URI (s) of units.
|


At least five Yemeni soldiers killed by Houthi missile in Marib military base
ADEN (Reuters) - Houthi militants fired a missile at the Saudi-led military coalition’s heaquarters in the city of Marib on Wednesday during a visit by the Yemeni defence minister, killing at least five soldiers, local officials said.
The base is the main military facility overseeing a ground offensive aimed at recapturing the capital Sanaa, controlled by the Iran-aligned Houthis since 2014, which lies 120 km (75 miles) to the west of Marib.
There was no immediate confirmation from the Saudi-led coalition, which has been has been battling the Houthis in Yemen for more than four years.
But Saudi-owned news channel Al-Arabiya said seven soldiers were killed in the attack. Local officials said five Yemeni soldiers were killed.
Mohammed al-Maqdishi, the defence minister of Yemen’s internationally recognised government, and Saudi military officers were in the compound at the time, the officials said.
The coalition spokesman did not respond to a request for comment.
The war has killed tens of thousands of people and pushed millions to the brink of famine.
The Saudi-led coalition intervened in 2015 to restore the government of President Abd-Rabbu Mansour Hadi, which the Houthis ousted from power in the capital Sanaa and is now based in the southern port city of Aden. It has carried out thousands of air strikes in Houthi areas.
Last week, Houthi forces fired missiles and drones at the Red Sea port city of al-Mokha, causing deaths and injuries and damaging a hospital.
The group, which holds Sanaa and most of Yemen’s big urban centres, denies being puppets of Iran and says it is fighting a corrupt system.


public class CustomObject
extends java.lang.Object
| Modifier and Type | Field and Description |
|---|---|
private Position |
acc
The acceleration of the object in x,y,z per second (not per update)
|
private java.util.ArrayList<Vertex> |
actualLPVertices
List of the actual LP Vertices (not relative to position/rotation)
|
private boolean |
actualLPVertsUpdated
Has the actual vertex position of the low poly vertices been updated since the last movement
|
private java.util.ArrayList<Vertex> |
actualVertices
List of the actual vertices (not relative to position/rotation)
|
private boolean |
actualVertsUpdated
Has the actual vertex position of the vertices been updated since the last movement
|
private boolean |
canMove
Can the object move?
|
private Position |
centerOfMass
The center of mass of the object assuming each vertex has mass 1 and only vertices have mass
|
private java.util.ArrayList<TriangularFace> |
faces
The faces of the object
|
private boolean |
gravity
Is the object effected by gravity
|
private boolean |
hasTexture
Does the object have a texture
|
private double |
inverseMass
The inverse mass (1/mass) of the object
|
private Position |
lastCol
The location of the last collision
|
private java.util.ArrayList<TriangularFace> |
lpFaces
The faces of the object
|
private java.lang.String |
LPName
The name of the low poly object (filename without extension)
|
private java.util.ArrayList<Vertex> |
lpVertices
The vertices of the object
|
private Material |
material
The material of this object
|
private java.lang.String |
name
The name of the object (filename without extension)
|
private java.util.ArrayList<Vertex> |
oldActualLPVertices
The list of actual vertex positions of the low poly part of the object from last update (not relative to object position/rotation)
|
private java.util.ArrayList<Vertex> |
oldActualVertices
The list of actual vertex positions of the object from last update (not relative to object position/rotation)
|
private Vertex |
outputVertex
Used in "getActualVertex()" just here for garbage collection reduction
|
private Position |
position
The position of the object in 3d space
|
private Position |
prevPosition
The position of the object after the last physics update
|
private Rotation |
prevRotation
The rotation of the object after the last physics update
|
private org.ejml.data.DenseMatrix64F |
prevRotationMatrix
The rotation matrix from the last update
|
private org.ejml.data.DenseMatrix64F |
prevTranslationMatrix
The translation matrix from the last update
|
private Position |
prevVel
The velocity of the object last update
|
private Position |
relativeCenterOfMass
The center of mass of the object relative to its position
|
private Rotation |
rotation
The rotation of the object about x,y,z axis
|
private org.ejml.data.DenseMatrix64F |
rotationMatrix
The matrix representing rotation of the object around x,y,z axis (4x4 matrix)
|
private org.ejml.data.DenseMatrix64F |
tempMatrix
Used in "getActualVertex()" just here for garbage collection reduction
|
private java.util.ArrayList<Vertex> |
tempVertexList
Here for gc reduction, used in getting actual vertices for efficiency
|
private static java.util.ArrayList<java.lang.String> |
textureNames
The names of the textures used across all objects, in the same order as the textures list
|
private int |
textureNo
The position of this objects texture in the texture list
|
private static java.util.ArrayList<com.jogamp.opengl.util.texture.Texture> |
textures
The list of textures used across all objects
|
private org.ejml.data.DenseMatrix64F |
translationMatrix
The matrix representing translation (position) of the object from the origin (4x4 matrix)
|
private Position |
vel
The velocity of the object in x,y,z per second (not per update)
|
private Vertex |
vertex
Used in "getActualVertex()" just here for garbage collection reduction
|
private org.ejml.data.DenseMatrix64F |
vertexMatrix
Used in "getActualVertex()" just here for garbage collection reduction
|
private static java.util.ArrayList<java.lang.String> |
vertexNames
The name of the objects which have each position in the vertices list
|
private int |
vertexNo
The position of the objects vertices in the vertex list
|
private static java.util.ArrayList<java.util.ArrayList<Vertex>> |
vertices
Vertices of the objects, static to reduce memory for objects with identical vertices
|
| Constructor and Description |
|---|
CustomObject()
Creates an object with variables initialised to null
|
CustomObject(java.util.ArrayList<Vertex> inpVertices,
java.util.ArrayList<TriangularFace> inpFaces,
java.lang.String name)
Creates an object with the input face and vertices
|
CustomObject(CustomObject inpObj)
Creates a custom object as a copy of an existing one
|
| Modifier and Type | Method and Description |
|---|---|
void |
accelerate(double time)
Accelerate the object by a certain time peroid
|
void |
acceleratePosition(double time)
Accelerate just the position of the object by a certain time
|
void |
accelerateRotation(double time)
Accelerate just the rotation of the object by a certain time
|
boolean |
canMove()
Can the object move true or false
|
static void |
clearTextures()
Clears the static texture list and texture names list.
|
Position |
getAcc()
gets the acceleration of the object
|
Vertex |
getActualLPVertex(int vertexNumber)
Gets the actual position (not relative to the position/rotation of the object) of a low poly vertex
|
java.util.ArrayList<Vertex> |
getActualLPVertices()
Gets the list of low poly vertices of the object at their actual position, not relative to the position/rotation of the object
|
Vertex |
getActualVertex(int vertexNumber)
Gets the actual position (not relative to the position/rotation of the object) of a vertex
|
java.util.ArrayList<Vertex> |
getActualVertices()
Gets the list of vertices of the object at their actual position, not relative to the position/rotation of the object
|
Position |
getCenterOfMass()
Gets the center of mass of the object in actual space, not relative to the object.
|
java.util.ArrayList<TriangularFace> |
getFaces()
Gets the faces of the object
|
boolean |
getGravity()
Gets if the object is effected by gravity
|
double |
getInverseMass()
Gets the inverse mass (1/mass) of the object
|
Position |
getLastCol()
Gets the position of the last collision
|
java.util.ArrayList<TriangularFace> |
getLPFaces()
Gets the low poly faces of the object
|
java.lang.String |
getLPName()
Gets the name of the low poly part of the object for use in the config creator
|
java.util.ArrayList<Vertex> |
getLPVertices()
Gets the low poly vertices of the object
|
Material |
getMaterial()
Gets the material associated with the object
|
java.lang.String |
getName()
Gets the name of the object for use in the config creator
|
private Vertex |
getNewActualLPVertex(int vertexNumber)
Gets the actual position (not relative to the position/rotation of the object) of a low poly vertex.
|
private Vertex |
getNewActualVertex(int vertexNumber)
Gets the actual position (not relative to the position/rotation of the object) of a vertex.
|
Position |
getPosition()
Gets the position of the object
|
Vertex |
getPrevActualLPVertex(int vertexNumber)
Gets the actual position of a low poly vertex (not relative) from the previous update
|
Vertex |
getPrevActualVertex(int vertexNumber)
Gets the actual position of a vertex (not relative) from the previous update
|
Rotation |
getRotation()
Gets the rotation of the object
|
com.jogamp.opengl.util.texture.Texture |
getTexture()
Gets the texture of the object
|
Position |
getVel()
Gets the velocity of the object
|
java.util.ArrayList<Vertex> |
getVertices()
Gets the vertices of the object
|
boolean |
hasTexture()
Gets if the object has a texture or not
|
private static int |
isInTextureNames(java.lang.String inpName)
Checks if a filename is in the list of existing texture filenames
|
private static int |
isInVertexNames(java.lang.String inpName)
Checks if an object name is in the list of objects with vertices stored
|
void |
move(double time)
Moves the object according to its velocity
|
void |
postCollisionMove(double time)
Moves the object according to its velocity.
|
private Position |
relativeCenterOfMass()
Calculates the relative center of mass of the object assuming mass only comes from vertices
and each vertex has equal mass
|
void |
rotateAboutPoint(Position relativePoint,
double xRot,
double yRot,
double zRot)
Rotates the object about a point given an x axis rotation, y axis rotation, z axis rotation
and the position of the point relative to the object.
|
void |
setAcc(Position inpAcc)
Sets the acceleration of the object
|
void |
setCanMove(boolean inpMove)
Sets if the object can move or not.
|
void |
setFaces(java.util.ArrayList<TriangularFace> inpFaces)
Sets the faces of the object
|
void |
setGravity(boolean inpGrav)
Sets if the object is effected by gravity
|
void |
setHasTexture(boolean inpHasTexture)
Sets the value that says if the object has a texture.
|
void |
setInverseMass(double inpIMass)
Sets the inverse mass of the object.
|
void |
setLastCol(Position inpCol)
Sets the position of the last collision
|
void |
setLPFaces(java.util.ArrayList<TriangularFace> inpFaces)
Sets the low poly faces of the objects
|
void |
setLPName(java.lang.String inpName)
Sets the name of the low poly part of the object, this is used in the config creator
|
void |
setLPVertices(java.util.ArrayList<Vertex> inpVertices)
Sets the vertices of the low poly part of the object to the input ones
|
void |
setMaterial(Material inpMaterial)
Sets the objects material to the one input
|
void |
setName(java.lang.String inpName)
Sets the name of the object, this is used in the config creator
|
void |
setPosition(Position inpPosition)
Sets the objects position to the one input
|
void |
setRotation(Rotation inpRotation)
Sets the objects rotation to the one input
|
void |
setTexture(com.jogamp.opengl.util.texture.Texture inpTexture)
Sets the objects texture to the one input
|
void |
setVel(Position inpVel)
Sets the velocity of the object
|
void |
setVertices(java.util.ArrayList<Vertex> inpVertices)
Sets the vertices of the object to the input ones
|
void |
undoPosRot()
Reverts the position and rotation of the object to its last update
|
void |
undoVel()
Reverts the velocity of the object to its last update
|
private void |
updateActualLPVertex(int vertexNumber)
Updates the actual position (not relative to the position/rotation of the object) of a low poly vertex
|
private void |
updateActualLPVertices()
Updates the list of actual low poly vertices or creates a new one is the current one is empty
|
private void |
updateActualVertex(int vertexNumber)
Updates the actual position (not relative to the position/rotation of the object) of a vertex
|
private void |
updateActualVertices()
Updates the list of actual vertices or creates a new one if the current one is empty
|
private void |
updateMatrices()
Updates the transformation matrices.
|
private java.lang.String name
private java.lang.String LPName
private java.util.ArrayList<TriangularFace> faces
private static java.util.ArrayList<java.util.ArrayList<Vertex>> vertices
private int vertexNo
private static java.util.ArrayList<java.lang.String> vertexNames
private static java.util.ArrayList<com.jogamp.opengl.util.texture.Texture> textures
private static java.util.ArrayList<java.lang.String> textureNames
private int textureNo
private Material material
private boolean hasTexture
private java.util.ArrayList<TriangularFace> lpFaces
private java.util.ArrayList<Vertex> lpVertices
private java.util.ArrayList<Vertex> actualLPVertices
private boolean actualLPVertsUpdated
private Position position
private Rotation rotation
private Position prevPosition
private Rotation prevRotation
private org.ejml.data.DenseMatrix64F translationMatrix
private org.ejml.data.DenseMatrix64F rotationMatrix
private org.ejml.data.DenseMatrix64F prevTranslationMatrix
private org.ejml.data.DenseMatrix64F prevRotationMatrix
private Position acc
private Position vel
private Position prevVel
private boolean canMove
private double inverseMass
private java.util.ArrayList<Vertex> oldActualVertices
private java.util.ArrayList<Vertex> oldActualLPVertices
private boolean gravity
private Position centerOfMass
private Position relativeCenterOfMass
private Position lastCol
private boolean actualVertsUpdated
private java.util.ArrayList<Vertex> actualVertices
private org.ejml.data.DenseMatrix64F vertexMatrix
private org.ejml.data.DenseMatrix64F tempMatrix
private Vertex vertex
private Vertex outputVertex
private java.util.ArrayList<Vertex> tempVertexList
CustomObject()
CustomObject(java.util.ArrayList<Vertex> inpVertices, java.util.ArrayList<TriangularFace> inpFaces, java.lang.String name)
inpVertices
- The vertices of the objectinpFaces
- The faces of the objectname
- The name of the objectCustomObject(CustomObject inpObj)
inpObj
- The object to copypublic void setLastCol(Position inpCol)
inpCol
- The position to set topublic Position getLastCol()
public void setGravity(boolean inpGrav)
inpGrav
- Object effected by gravity? True or falsepublic boolean getGravity()
public void setName(java.lang.String inpName)
inpName
- The name to give the objectpublic void setLPName(java.lang.String inpName)
inpName
- The name to give the objectpublic java.lang.String getName()
public java.lang.String getLPName()
public void setInverseMass(double inpIMass)
inpIMass
- The inverse mass to set topublic double getInverseMass()
public void setMaterial(Material inpMaterial)
inpMaterial
- The material to set topublic void setPosition(Position inpPosition)
inpPosition
- The position to set topublic Material getMaterial()
public Position getPosition()
public void setFaces(java.util.ArrayList<TriangularFace> inpFaces)
inpFaces
- The faces to set topublic void setLPFaces(java.util.ArrayList<TriangularFace> inpFaces)
inpFaces
- The faces to set topublic java.util.ArrayList<TriangularFace> getFaces()
public java.util.ArrayList<Vertex> getVertices()
public java.util.ArrayList<TriangularFace> getLPFaces()
public java.util.ArrayList<Vertex> getLPVertices()
public void setTexture(com.jogamp.opengl.util.texture.Texture inpTexture)
inpTexture
- The texture to set topublic com.jogamp.opengl.util.texture.Texture getTexture()
public void setHasTexture(boolean inpHasTexture)
inpHasTexture
- The value to set to, true for has a texture, false for no texturepublic boolean hasTexture()
public void setRotation(Rotation inpRotation)
inpRotation
- The rotation to set topublic Rotation getRotation()
public static void clearTextures()
private static int isInVertexNames(java.lang.String inpName)
inpName
- The name to checkprivate static int isInTextureNames(java.lang.String inpName)
inpName
- The name to checkpublic void setVertices(java.util.ArrayList<Vertex> inpVertices)
inpVertices
- The vertices to set topublic void setLPVertices(java.util.ArrayList<Vertex> inpVertices)
inpVertices
- The vertices to set topublic java.util.ArrayList<Vertex> getActualVertices()
public java.util.ArrayList<Vertex> getActualLPVertices()
private void updateActualLPVertices()
private void updateActualVertices()
public Vertex getActualVertex(int vertexNumber)
vertexNumber
- The vertex to get the position ofpublic Vertex getActualLPVertex(int vertexNumber)
vertexNumber
- The vertex to get the position ofprivate void updateActualLPVertex(int vertexNumber)
vertexNumber
- The vertex to update the position ofprivate void updateActualVertex(int vertexNumber)
vertexNumber
- The vertex to update the position ofprivate Vertex getNewActualLPVertex(int vertexNumber)
vertexNumber
- The vertex to get the position ofprivate Vertex getNewActualVertex(int vertexNumber)
vertexNumber
- The vertex to get the position ofpublic Vertex getPrevActualVertex(int vertexNumber)
vertexNumber
- The vertex to get position ofpublic Vertex getPrevActualLPVertex(int vertexNumber)
vertexNumber
- The vertex to get position ofpublic void rotateAboutPoint(Position relativePoint, double xRot, double yRot, double zRot)
relativePoint
- The point to rotate around relative to the objectxRot
- The x axis rotationyRot
- The y axis rotationzRot
- The z axis rotationprivate void updateMatrices()
public Position getCenterOfMass()
public void setAcc(Position inpAcc)
inpAcc
- The acceleration to set topublic void setVel(Position inpVel)
inpVel
- The velocity to set topublic Position getAcc()
public Position getVel()
public void setCanMove(boolean inpMove)
inpMove
- True or falsepublic boolean canMove()
public void move(double time)
time
- How much time to advance the object bypublic void postCollisionMove(double time)
time
- How much time to advance the object bypublic void accelerate(double time)
time
- The amount of time to accelerate the object forpublic void acceleratePosition(double time)
time
- The time to accelerate forpublic void accelerateRotation(double time)
time
- The time to accelerate forpublic void undoPosRot()
public void undoVel()
private Position relativeCenterOfMass()


We’re experimenting with a new form of release notes, so that it’s easier to get context on what’s going on in Finagle-land, especially with an eye to letting consumers see what the latest and greatest features are, and providing a little more context around what’s going on.
If you have questions about something you see in the changelogs that we didn’t mention in the expanded release notes, please feel free to email me and ask for a clarification.
At a broader level, we’d also like to mention that we’re interested in improving Java compatibility, so if you’re having trouble using one of our APIs from Java, please let us know.
util
: 6.19.0finagle
: 6.20.0scrooge
: 3.16.3twitter-server
: 1.7.3We made a couple of big changes to Buf
, our byte array abstraction, and
Reader
, our byte streaming abstraction. Previously, we had a special Buf
called Buf.Eof
to denote the end of a byte Stream, but it occurred to us that
it didn’t make sense to have this in the byte array abstraction—it made more
sense to model it in the byte stream abstraction, so now the semantic lies in
the Reader
. Reader
is experimental, and not used widely, so we didn’t bump
the major version. We apologize if this causes you problems.
At long last, we’ve deprecated com.twitter.util.Bijection
. This has been a
long time coming, since there’s now a fully-fledged open source
project built
around Bijection
that does everything that c.t.u.Bijection
did, and a whole
lot more!
We’ve added several new features to Buf, our byte array abstraction. In part,
this is to prepare to start exposing Netty-free interfaces,
so that we can swap Netty 3 out for other backends. Some of those features are
that we now have a Buf.ByteBuffer
to wrap java.nio.ByteBuffer
, Buf
s now
support reading and writing U(32|64)(BE|LE)
integers with Buf
s, and we’ve
significantly improved the performance of concatenating Buf
s, with
ConcatBuf
.
There are two new features on spools as we think more about object streaming.
Spool
now has take, useful for batching, and mapFuture, useful when you want
to apply a function which returns an asynchronous result to every item in your
spool.
We’ve modified the Logging
trait so that it’s more extensible, making it
easier to change the handlers for your logger. We hope that this will simplify
having a unified way of logging across a project or organization.
LoggerFactory
has been hard to use from Java for a long time. We just created
a LoggerFactoryBuilder
, which should be much easier to use from Java. There’s
an example in the LoggerFactoryBuilder
compilation
test.
We’re excited about making Finagle easier to use from Java, so please let us
know if you continue to run into trouble consuming Finagle from Java, so we can
work with you to make Finagle more Java-friendly.
The Scaladocs for Flag
and friends
have been significantly improved. If you ever wondered how util-flags
worked,
the Scaladocs are now an even better place to learn the nitty gritty details.
George Leontiev singlehandedly replaced all of our old specs tests with ScalaTest ones, paving the way for Util to be published against Scala 2.11. We weren’t able to publish util against 2.11 in this most recent release, but watch this space! We’re also making big strides in 2.11-ification for Finagle, in large part inspired by George’s work.
6.19.0 2014-08-05
util
: smattering of minor cleanups in util and finagleutil-core
: Reader and getContent symmetry6.18.4 2014-07-31
util-core
: Remove confusing NOOP 0.until(5) in Future.collect().util-app
: Fix a bug in global flag parsing6.18.2 2014-07-23
util-core
: Fixes a broken sbt testutil-core
: Log exceptions caught by ChannelStatsHandlerutil-core
: Satisfy promise on fatal exception in FuturePool taskutil-core
: small perf improvements to Future.collect, Throw, Flagutil-logging
: Java-friendly LoggerFactory API6.18.1 2014-07-08
util
: Update README to reflect correct storage units.util-*
: Convert all tests in util to ScalaTestutil-app
: Simplifies the logic to get the appnameutil-io
: Buf, Reader: remove Buf.Eof; end-of-stream is Noneutil-io
: Create Buf.ByteBuffer to wrap java.nio.ByteBuffer6.18.0 2014-06-23
util-app
: Don’t kill the JVM on flag-parsing failureutil-app
: Improve the Scaladocs for com.twitter.app.Flag and friendsutil-core
: Add U(32|64)(BE|LE) to Bufutil-core
: Add com.twitter.util.NilStopwatchutil-core
: Add src/main/java dependency on src/main/scalautil-core
: Catch InterruptedException in Closable collector threadutil-core
: Fix MockTimer#schedule(Duration)(=> Unit)‘s cancelutil-core
: Fix update-after-interrupt race condition in AsyncSemaphoreutil-core
: Signal the deprecation of com.twitter.util.Bijection.util-logging
: Add additional handlers to Logging trait6.17.0 2014-06-04
util
: Upgrade dependency versionsutil-core
: Scheduler productivity = cpuTime/wallTimeutil-core
: Add a take
method to Spool
util-core
: Introduce ConcatBuf
util-core
: add Spool.collectFuture
We’ve renamed Finagle threads, so that they are now called “finagle/netty3”. This should make it easier to figure out what is going on in your stack traces.
finagle-http
now supports streaming the request body. This is not yet
documented, but there is a pull request
to add documentation to the Finagle user guide. We’d love to hear what you
think.
getContent
and Reader
are two ways to retrieve the body of the HTTP message.
The previous behavior was that when the message was chunked, calling
reader.read(n)
retrieved n bytes of the message body, and getContent
returned an empty ChannelBuffer
. When the message was not chunked,
getContent
returned a ChannelBuffer
filled with the message body, and
calling reader.read(n)
was a future that never resolved. The new behavior is
that when the message is chunked, the behavior remains the same, but when not
chunked, calling reader.read(n)
retrieves n
bytes of the message body. We
think this is behavior is much more aligned with expectations.
The previous default for inet! resolution in Finagle was to never refresh the
DNS lookup, so people had to do terrible hacks to get it to work properly. Part
of the problem was that Twitter doesn’t change DNS entries frequently, so we
don’t rely on DNS for service discovery often. However, the new Finagle
supports timer-based DNS resolution as default in InetResolver
. Thanks a ton
to Alex Gleyzer, who came up with the original
implementation, and Cobb, who got it ready to merge
into Finagle.
Per-host stats can be too noisy to turn on in production, and will entail
significant GC pressure if you have many downstream hosts. We’ve added a new
flag that you can enable to turn on per host stats,
com.twitter.finagle.loadbalancer.perHostStats
, since they are often useful for
debugging problems locally, or in staging environments.
finagle-thriftmux
now supports the experimental feature GC Avoidance if you
turn on the right flags. We’re beginning to load test it now, but it’s not
ready for prime time yet. If you’re trying to use GC Avoidance outside of
Twitter, you might have a hard time. In some parts it depends upon having a JDK
which supports System.minorGc
, an extra call on System
which will only
trigger a minor GC. We’ve discussed other ways of forcing a minor GC, like
allocating a lot of big arrays very quickly, but haven’t implemented them yet.
Please get in contact if you’re interested in working on this.
We’ve significantly improved the documentation around HTTP streaming, and also added a bunch of examples. This hasn’t been merged yet, but can be found at the pull request to add documentation to the Finagle user guide. We’d love to hear what you think.
We’ve added several new stats to Finagle, to generally improve insight into
Finagle. We’ve added a marked_dead
counter to the FailFastFactory
, so that
you can see when your client perceives that downstream endpoints are flapping.
We’ve also added a couple of counters in WatermarkPool
, to make it easier to
see when you’re having queueing problems, and are asked to wait in line for a
connection, namedly pool_num_waited
, and pool_num_too_many_waiters
.
We’ve added a service acquisition latency stat to StatsFactoryWrapper
, which
gives insight into how long it takes to acquire a service. Since TCP
connections are usually quite fast, and should mostly be cached, this usually
measures how long you spend queueing for a connection.
Inspired in large part by the great work in Util to get ready for Scala 2.11,
we’ve started making Finagle ready for Scala 2.11. A large part of this is
paying down technical debt that we’ve accrued, like having half of our tests
still be on specs, which is super deprecated. Because of this, we’re trying to
move as much as possible onto ScalaTest, which is what we use now.
Pierre-Antoine Ganaye, the author of the very
cool finagle-zookeeper project,
stepped up and migrated the finagle-core
tests over, while getting up to speed
on Finagle, and the Finagle community took on the mantle for the rest of the
tests. We’re over halfway
there, and we’re beginning to think about how to switch over our other projects,
like Scrooge and Twitter-server.
In order to make it easier to get new contributors started with Finagle, we’ve added sections about review process and starter issues. Also, so that open source users can see how many other open source users there are and have more confidence in our commitment to open source, we’ve started an adopters list.
6.20.0
finagle
: Smattering of minor cleanups in util and finaglefinagle
: Upgrade sbt to 0.13finagle
: Upgrade to Netty <IP_ADDRESS>.Finalfinagle-core
: Add NameTree.Fail to permit failing a name without fallbackfinagle-core
: Add a generic DtabStatsFilterfinagle-core
: Add a singleton exception and a counter in WatermarkPoolfinagle-core
: DefaultClient in terms of StackClientfinagle-core
: Disable Netty’s thread renamingfinagle-core
: Fix CumulativeGauge memory leakfinagle-core
: Fix negative resolution in Namer.globalfinagle-core
: Fixed ChannelStatsHandler to properly filter exceptionsfinagle-core
: Forces finagle-core to use ipv4 network stackfinagle-core
: Improve Failure.toString
finagle-core
: Include path and Dtab.local in NoBrokersAvailableExceptionfinagle-core
: Log exceptions caught by ChannelStatsHandlerfinagle-core
: Make timer-based DNS resolution as default of InetResolverfinagle-core
: Reader and getContent symmetryfinagle-core
: Reduces log level for common exceptionsfinagle-core
: Register clients centrallyfinagle-doc
: Add fintop to companion projects list on Finagle websitefinagle-http
: Don’t emit (illegal) newlines in lengthy dtab header valuesfinagle-http
: Fix code style from an open-source contributionfinagle-http
: Migrate from specs to ScalaTestfinagle-kestrel
: Make transaction abort timeout configurable in MultiReaderfinagle-mux
: Added extra client loggingfinagle-mux
: Fix broken draining behaviorfinagle-mux
: Improve granularity of rate to bytes/millisecondfinagle-serversets
: Handle errors that occur when fetching endpointsfinagle-serversets
: Increase ZK session timeout to 10 secondsfinagle-serversets
: Merge WeightedSocketAddresses with same host:port but different weight in Stabilizerfinagle-serversets
: Synchronize bug fixes & test coverage across ZK facadesfinagle-swift
: Fixes pants build warningfinagle-thrift
: Add explicit dependency on libthriftfinagle-thrift
: Remove usage of java_sources, should be able to depend on it normally6.19.0
finagle-core
: Allow trailing semicolons in dtabsfinagle-core
: Rescue exceptions thrown by filter in Filter.andthen(Filter)
finagle-core
: StackClient, StackClientLike don’t leak underlying In, Out typesfinagle-doc
: Clarify cancellationfinagle-doc
: Fix broken link in documentfinagle-doc
: Fix name footnote in finagle Names docsfinagle-http
: Buf, Reader remove Buf.Eof; end-of-stream is Nonefinagle-http
: Prepend comment to JSONP callbacksfinagle-http
: Removing specs from the CookieMapSpec test.finagle-kestrel
: Make failFast configurable in Kestrel codecfinagle-mysql
: Ensure mysql specific tracing is composed.finagle-mysql
: Finagle MySQL PreparedStatement accepts Value types as params.finagle-serversets
: Identity Providers for Serverset2finagle-thriftmux
: Add withProtocolFactory API endpointfinagle-thriftmux
: Don’t reuse InMemoryStatsReceiver in the same test6.18.0
finagle-*
: release scrooge v3.16.0finagle-*
: release util v6.18.0finagle-core
: Add description
field to com.twitter.finagle.Stackable traitfinagle-core
: Add a Flag to turn on per-host statsfinagle-core
: Add a service acquisition latency stat to StatsFactoryWrapperfinagle-core
: Don’t support empty path elements in com.twitter.finagle.Pathfinagle-core
: Improves FailFastFactory documentationfinagle-core
: Make c.t.f.Failure a direct subclass of Exceptionfinagle-core
: Skip SOCKS proxy when connecting to loopback addressfinagle-core
: Use Monitor from caller’s context in DefaultTimerfinagle-http
: Add “Enhance Your Calm” and “Too Many Requests” HTTP status codesfinagle-http
: Add exp.HttpServer, which allows request limits to be configuredfinagle-http
: Change Request#params to a memoized deffinagle-http
: Stream request bodyfinagle-kestrel
: Add Name-based methods for MultiReader constructionfinagle-memcached
: Expose the client type KetamaClient
in the build()
APIfinagle-mux
: GC Avoidance Algorithmfinagle-mux
: Hook up GC avoidance to serversfinagle-mux
: Move UseMux.java to the correct directoryfinagle-serversets
: Randomizes backoff interval in ZK2finagle-serversets
: Start resolution eagerly in ZK2finagle-stats
: Add a stat-filtration GlobalFlagfinagle-*
: release ostrich v9.5.2user guide
: Add Google Analytics tracking codeuser guide
: Add sections about review process and starter issuesuser guide
: Update Finagle adopter list on user guide websitewily
: Add Dtab expansion6.17.0
finagle
: Add list of Finagle adoptersfinagle
: Upgrade third-party dependenciesfinagle-core
: Add Addr.Neg
to the user guide’s list of Addr typesfinagle-core
: Added Failure support for sourcing to finaglefinagle-core
: ClientBuilder should turn per-host stats off by default (matching new Client building API).finagle-core
: Implement DefaultServer in terms of StackServerfinagle-core
: Improve the Dtab APIfinagle-core
: Prevent scoping stats with the empty-stringfinagle-core
: Rolls up the /tries scope properlyfinagle-core
: ServerStatsReceiver and ClientStatsReceiver can now update their root scopefinagle-core
: fix race case in DelayedFactoryfinagle-core
: introduce AbstractResolverfinagle-core
: remove need for hostConnectionLimit when using ClientBuilder#stackfinagle-core
: widen to type for ServerBuilder#stackfinagle-core
: widen type of ClientBuilder#stackfinagle-doc
: Removed a line from conf.pyfinagle-http
: DtabFilter should always clear dtab headersfinagle-http
: add HOST header for CONNECT methodfinagle-http
: scala 2.10 compatible testsfinagle-memcached
: filter out one more cancelling request exception in failure accrualfinagle-memcached
: remove empty testfinagle-mux
: Improve Mux server close behavior, control messages to non-Mux clientsfinagle-mux
: Marked a gc test as flakyfinagle-mux
: Modifies MuxService to essentially be a Service[Spool[Buf], Spool[Buf]] Problemfinagle-mux
: Rm ClientHangupException in favor of CancelledRequestExceptionfinagle-mysql
: Retrieving a timestamp from the DB nw creates a timestamp in UTCfinagle-mysql
: fix for issue where time was not being returned in UTC for binary protocolfinagle-serversets
: Prevent gauges from being garbage collectedfinagle-thrift
: Blackhole control messages sent to non-mux Thrift clientsfinagle-thriftmux
: Add per-connection protocol-usage statsfinagle-thriftmux
: Add stats to identify ThriftMux clients and serversfinagle-thriftmux
: Propagate Contexts from non-ThriftMux clientsfinagle-thriftmux
: add ClientBuilder#stack compatibility and make APIs symmetricfinagle-thriftmux
: pass along ClientId with ClientBuilder APIWe wrote a scrooge-linter,
which we’re really excited about. If you’re at a company that has a lot of
Thrift IDL files, you know the pain of trying to get everyone to write them in a
standard way, especially since the tooling is so anemic. scrooge-linter
begins to fix that problem, by linting your IDL files so you can catch
non-conforming thrift quickly and systematically.
The docs on how to use the scrooge tool from the command line have long been out of date. We just did a big refresher of them, and it’s much easier to get up and running with a new Scrooge project now.
3.16.3
scrooge-core
: Add union metadata for reflectionscrooge-doc
: Clarify docs on CLI usagescrooge-generator
: Fix error message for missing required fieldscrooge-generator
: Modify compiler to accept a Scaladoc comment at the end of Thrift filescrooge-generator
: Normalize scalatest versions between poms and 3rdpartyscrooge-generator
: Stricter checks for invalid Thrift filenamesscrooge-ostrich
: Default to using Protocols.binaryFactory
3.16.1
scrooge-*
: release finagle 6.18.0scrooge-*
: release util 6.18.0scrooge-linter
: Fix multiple arguments to linter + pants/mvn fixesscrooge
: Separate flow for linterscrooge
: Skip includes when linting3.16.0
scrooge-*
: Upgrade dependencies to latest versionsscrooge
: Move scrooge-linter into scroogescrooge
: Add SimpleID.originalName for enum fieldsIt has historically been difficult to understand how your client is configured, even though all clients are configured very similarly, usually with only small changes in parameters. However, when debugging, users sometimes need to know how long timeouts have been set to, what kind of load balancer is being used, and other configuration parameters, so that we can debug problems more quickly. Now, we have a neat admin endpoint where users can gain insight into each client individually.
Having logging at multiple granularities is a real luxury, but sometimes you realize that you’ve set the log level incorrectly, and you need to be able to see more granular logs on a box that’s already in an interesting state, in production. To that end, we’ve added a logging handler to the Twitter-server admin service, which can both tell you about the current log levels, but can also be used to change logging granularities on the fly.
We added a new admin handler to display the base dtab, so that it’s easier to reason about what will happen to a service when it receives a new dtab. Instead of having to guess based on its behavior, or try to figure it out through inspecting the code, you can just query now, and know the right answer immediately.
Built-in metrics are one of the coolest features of Finagle, but there are
really a ton of them, especially if you have many downstreams, or you use per
host stats. In order to make this problem easier to deal with, we added a flag,
com.twitter.finagle.stats.statsFilter
, which you can pass in to filter out
some stats that you know you will never use.
1.7.3
1.7.2
1.7.1


Guidance
Types of apprenticeships that you can apply for in the furniture, furnishing and interiors sector.
This apprenticeship covers a range of occupations involved with the manufacture and production of furniture.
As an intermediate level apprentice you could work as a cabinet or furniture maker, where you would produce and assemble component pieces of furniture items including:
Or you could work as a soft furnisher, measuring, cutting, and sewing of fabrics to customer or company requirements usually in a workshop.
On the advanced level apprenticeship you could work as an experienced furniture restorer repairing furniture, from simple things like re-gluing broken parts, through to completely rebuilding an item including making missing components and re-polishing.
Alternatively you could work as an experienced upholsterer adding padding and soft covers to furniture, working with designs, textures and colours to cover or re-cover items with fabric or other materials.
There are 2 types of apprenticeships in this sector.
You can train in roles like:
You can train in roles like:
You can become an apprentice in England if you’re:
Published: 12 April 2012


Calling refresh
allows you to re-build the wselect menu from your original select. This is useful
when the contents of the select box changes dynamically (through either AJAX, DOM manipulation, etc.) and you want the
wselect widget to reflect the changes.
// once the "add" button is clicked below: $("select").wselect('refresh');
Type in the text of a new option tag to add dynamically.


The Graduate (1967)
Grade: 71
"The Graduate" is a good comedy that has generally been over-rated over the years. While the film launched Dustin Hoffman's career, it is by no means his best film (my bets are on "Little Big Man"). Most of the humor works, which admittedly is the point, but the characters of Hoffman and Ross lack consistency and motivation.
Perhaps "The Graduate" should have been called "The Three Faces of Dustin" instead. Benjamin (Hoffman) has just graduated from college, but continues to live at home. He is polite and earnest. He is seduced by his father's partner's wife, middle-aged Mrs. Robinson (Anne Bancroft). As the furtive affair continues, Benjamin becomes secretive and dissipated. Mrs. Robinson's daughter, Elaine (Katherine Ross) returns home from college. Under pressure from his parents, Benjamin dates Elaine but soon falls for her. This leads to The Third Face of Dustin, the obsessed Stalker, as he tries to get her to marry him.
Benjamin is extremely naive for a college graduate with his golden resume, which includes captain of the track team and editor of the college newspaper. It doesn't help that Hoffman was thirty years old in 1967, nearly ten years older than his character. His first encounter with Bancroft at a swank hotel is endearingly clumsy, but not completely credible. After several such encounters, he still refers to her as "Mrs. Robinson". You think they'd be on a first name basis by then.
Katherine Ross is lovely, but her character seems to just go with the flow. When Benjamin is cruel to her, she cries. When he wants to make up, she agrees.  So, why does she show up at his apartment. And agree to marry him against her parent's wishes and her better judgment? And whatever happened to the beautiful brand new Alfa Romeo? If he doesn't want it, I'll take it!
Look fast for Richard Dreyfuss. He's the guy who wants to call the police. Buck Henry, who also co-wrote the screenplay, has a small part, as does Norman Fell. All three are funny.
The soundtrack is full of Simon & Garfunkel tunes. The soundtrack had as much success as the film, topping the charts. The tunes are wimpy but still very good.
"The Graduate" won the Oscar for Best Director (Mike Nichols). The film was nominated for many other Academy Awards, including Best Picture, Best Actor (Hoffman), Best Actress (Bancroft), Best Adapted Screenplay, Best Cinematography (Robert Surtees), and Best Supporting Actress (Ross).
<EMAIL_ADDRESS>http://members.tripod.com/~Brian_Koller/movies.html
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


First Auth App
Home
login
Signup
All Users
User
Profile
Users Feed
Logout
Welcome,
Username
Information
Username
First Name:
Last Name:
Date Of Birth:
Bio:
Create post
Post Body
Create
Edit Profile Information
Edit Profile Info
Password:
First Name:
Last Name:
Date Of Birth:
Bio
Submit


Pocoo Styleguide¶
The Pocoo styleguide is the styleguide for all Pocoo Projects, including Flask. This styleguide is a requirement for Patches to Flask and a recommendation for Flask extensions.
In general the Pocoo Styleguide closely follows PEP 8 with some small differences and extensions.
General Layout¶
- Indentation:
- 4 real spaces. No tabs, no exceptions.
- Maximum line length:
- 79 characters with a soft limit for 84 if absolutely necessary. Try to avoid too nested code by cleverly placing break, continue and return statements.
- Continuing long statements:
To continue a statement you can use backslashes in which case you should align the next line with the last dot or equal sign, or indent four spaces:
this_is_a_very_long(function_call, 'with many parameters') \ .that_returns_an_object_with_an_attribute MyModel.query.filter(MyModel.scalar > 120) \ .order_by(MyModel.name.desc()) \ .limit(10)
If you break in a statement with parentheses or braces, align to the braces:
this_is_a_very_long(function_call, 'with many parameters', 23, 42, 'and even more')
For lists or tuples with many items, break immediately after the opening brace:
items = [ 'this is the first', 'set of items', 'with more items', 'to come in this line', 'like this' ]
- Blank lines:
Top level functions and classes are separated by two lines, everything else by one. Do not use too many blank lines to separate logical segments in code. Example:
def hello(name): print 'Hello %s!' % name def goodbye(name): print 'See you %s.' % name class MyClass(object): """This is a simple docstring""" def __init__(self, name): self.name = name def get_annoying_name(self): return self.name.upper() + '!!!!111'
Expressions and Statements¶
- General whitespace rules:
- No whitespace for unary operators that are not words
(e.g.:
-
,~
etc.) as well on the inner side of parentheses. - Whitespace is placed between binary operators.
Good:
exp = -1.05 value = (item_value / item_count) * offset / exp value = my_list[index] value = my_dict['key']
Bad:
exp = - 1.05 value = ( item_value / item_count ) * offset / exp value = (item_value/item_count)*offset/exp value=( item_value/item_count ) * offset/exp value = my_list[ index ] value = my_dict ['key']
- No whitespace for unary operators that are not words
(e.g.:
- Yoda statements are a no-go:
Never compare constant with variable, always variable with constant:
Good:
if method == 'md5': pass
Bad:
if 'md5' == method: pass
- Comparisons:
- against arbitrary types:
==
and!=
- against singletons with
is
andis not
(eg:foo is not None
) - never compare something with True or False (for example never
do
foo == False
, donot foo
instead)
- against arbitrary types:
- Negated containment checks:
- use
foo not in bar
instead ofnot foo in bar
- Instance checks:
isinstance(a, C)
instead oftype(A) is C
, but try to avoid instance checks in general. Check for features.
Naming Conventions¶
- Class names:
CamelCase
, with acronyms kept uppercase (HTTPWriter
and notHttpWriter
) - Variable names:
lowercase_with_underscores
- Method and function names:
lowercase_with_underscores
- Constants:
UPPERCASE_WITH_UNDERSCORES
- precompiled regular expressions:
name_re
Protected members are prefixed with a single underscore. Double underscores are reserved for mixin classes.
On classes with keywords, trailing underscores are appended. Clashes with builtins are allowed and must not be resolved by appending an underline to the variable name. If the function needs to access a shadowed builtin, rebind the builtin to a different name instead.
- Function and method arguments:
- class methods:
cls
as first parameter - instance methods:
self
as first parameter - lambdas for properties might have the first parameter replaced
with
x
like indisplay_name = property(lambda x: x.real_name or x.username)
- class methods:
Docstrings¶
- Docstring conventions:
All docstrings are formatted with reStructuredText as understood by Sphinx. Depending on the number of lines in the docstring, they are laid out differently. If it’s just one line, the closing triple quote is on the same line as the opening, otherwise the text is on the same line as the opening quote and the triple quote that closes the string on its own line:
def foo(): """This is a simple docstring""" def bar(): """This is a longer docstring with so much information in there that it spans three lines. In this case the closing triple quote is on its own line. """
- Module header:
The module header consists of an utf-8 encoding declaration (if non ASCII letters are used, but it is recommended all the time) and a standard docstring:
# -*- coding: utf-8 -*- """ package.module ~~~~~~~~~~~~~~ A brief description goes here. :copyright: (c) YEAR by AUTHOR. :license: LICENSE_NAME, see LICENSE_FILE for more details. """
Please keep in mind that proper copyrights and license files are a requirement for approved Flask extensions.
Comments¶
Rules for comments are similar to docstrings. Both are formatted with
reStructuredText. If a comment is used to document an attribute, put a
colon after the opening pound sign (#
):
class User(object):
#: the name of the user as unicode string
name = Column(String)
#: the sha1 hash of the password + inline salt
pw_hash = Column(String)


Atomic Tests
Test 1
Test Procedure
- Turn on the closed caption feature of the media player
- View the synchronized media content
- Check that caption is positioned (of all dialogue and important sounds) in the same location as the sound source that it is representing
Expected Results
#3 is true.
Holistic Tests
- Still to be developed. We will include this in a future working draft.


This subpart establishes policies and procedures for the reporting, reutilization, and disposal of contractor inventory excess to contracts and of property that forms the basis of a claim against the Government (e.g., termination inventory under fixed-price contracts). This subpart does not apply to the disposal of real property or to property for which the Government has a lien or title solely as a result of advance, progress, or performance-based payments that have been liquidated.
This section is applicable to the reutilization, including transfer and donation, of Government property that is not required for continued performance of a Government contract. Except for 45.602-1, this section does not apply to scrap other than scrap aircraft parts.
(a) Plant clearance officers should review and accept, or return for correction, inventory disposal schedules within 10 days following receipt from a contractor. Schedules that are completed in accordance with the instructions for Standard Form 1428 should be accepted.
(b) Plant clearance officers shall—
(1) Use Standard Form 1423 to verify, in accordance with agency procedures, accepted schedules within 20 days following acceptance;
(2) Require the contractor to correct any discrepancies found during verification;
(3) Require the contractor to correct any failure to complete predisposal requirements of the contract; and
(4) Provide the contractor disposition instructions for property identified on an acceptable inventory disposal schedule within 120 days. A failure to provide timely disposition instructions may entitle the contractor to an equitable adjustment.
(c) The contractor may request the plant clearance officer’s approval to remove the Government property from an inventory schedule.
(1) Plant clearance officers should approve removal of Government property from an inventory schedule when—
(i) The contractor wishes to purchase a contractor-acquired or contractor-produced item at unit acquisition cost and credit the contract;
(ii) The contractor is able to return unused property to the supplier at fair market value and credit the contract (less, if applicable, a reasonable restocking fee that is consistent with the supplier’s customary practices);
(iii) The Government has authorized the contractor to use the property on another Government contract; or
(iv) The contractor has requested continued use of the Government property, and the contracting officer has authorized its retention and further use.
(2) If the screening process (see 45.602-3) has not begun, the plant clearance officer shall adjust the schedule or return the schedule to the contractor for correction. If screening has begun, the plant clearance officer shall promptly notify the activity performing the screening that the items should be removed from the screening process.
Plant clearance officers shall initiate reutilization actions for all property not meeting the abandonment or destruction criteria of 45.603(b). Authorized methods, listed in descending order from highest to lowest priority, are—
(a) Reuse within the owning agency;
(b) Transfer of educationally useful equipment to schools and nonprofit organizations (see Executive Order 12999, Educational Technology: Ensuring Opportunity For All Children In The Next Century, April 17, 1996, and 15 U.S.C. 3710(i));
(c) Report to GSA for reuse within the Federal Government or donation as surplus property;
(d) Dispose of the following property in accordance with agency procedures without reporting to GSA:
(1) Property determined appropriate for abandonment or destruction (see Federal Management Regulation (FMR) 102-36.305, 41 CFR 102-36.305).
(2) Property furnished to nonappropriated fund activities (see FMR 102-36.165, 41 CFR 102-36.165).
(3) Foreign excess personal property (see FMR 102-36.380, 41 CFR 102-36.380).
(4) Scrap, except aircraft in scrap condition.
(5) Perishables, defined for the purposes of this section as any personal property subject to spoilage or decay.
(6) Trading stamps and bonus goods.
(7) Hazardous waste or toxic and hazardous materials.
(8) Controlled substances.
(9) Property dangerous to public health and safety.
(10) Classified items or property determined to be sensitive for reasons of national security; and
(e) Dispose of nuclear materials (see 45.603-3(b)(5)) in accordance with the Nuclear Regulatory Commission, applicable state licenses, applicable Federal regulations, and agency regulations.
The screening period begins upon the plant clearance officer’s acceptance of an inventory disposal schedule. The plant clearance officer shall determine whether standard or special screening is appropriate and initiate screening actions.
(a) Standard screening. The standard screening period is 46 days.
(1) First through twentieth day—Screening by the contracting agency. The contracting agency has 20 days to screen property reported on the inventory disposal schedule for: other use within the agency; transfer of educationally useful equipment to other Federal agencies that have expressed a need for the property; and transfer of educationally useful equipment to schools and nonprofit organizations if a Federal agency has not expressed a need for the property. Excess personal property, meeting the conditions of 45.603, may be abandoned, destroyed, or donated to public bodies. No later than the 21st day, the plant clearance officer shall submit four copies of the revised schedules and Standard Form (SF) 120, Report of Excess Personal Property, or an electronic equivalent to GSA (see 41 CFR 102-36.215).
(2) Twenty-first through forty-sixth day (21 days concurrent screening plus 5 days donation processing).—
(i) Screening by other Federal agencies. GSA will normally honor requests for transfers of property on a first-come-first-served basis through the 41st day. When a request is honored, the GSA regional office shall promptly transmit to the plant clearance officer an approved transfer order that includes shipping instructions.
(ii) Screening for possible donation. Screening for donation is also completed during days 21 through 41. Property is not available for allocation to donees until after the completion of screening. Days 42 through 46 are reserved for GSA to make such allocation.
(3) Screening period transfer request. If an agency receives an intra-agency transfer request during the screening periods described in paragraph (a)(2) of this subsection, the plant clearance officer shall request GSA approval to withdraw the item from the inventory disposal schedule.
(b) Special screening requirements.—
(1) Special tooling and special test equipment without commercial components. Agencies shall follow the procedures in paragraph (a) of this subsection. This property owned by the Department of Defense (DoD) or the National Aeronautics and Space Administration (NASA) may be screened for reutilization only within these agencies.
(2) Special test equipment with commercial components.—
(i) Agencies shall complete the screening required by paragraph (a) of this subsection. If an agency has no further need for the property and the contractor has not expressed an interest in using or acquiring the property by annotating the inventory disposal schedule, the plant clearance officer shall forward the inventory disposal schedule to the GSA regional office that serves the region in which the property is located.
(ii) If the contractor has expressed an interest in using the property on another Government contract, the plant clearance officer shall contact the contracting officer for that contract. If the contracting officer concurs with the proposed use, the contracting officer for the contract under which the property is accountable shall transfer the property’s accountability to that contract. If the contracting officer does not concur with the proposed use, the plant clearance officer shall deny the contractor’s request and shall continue the screening process.
(iii) If the property is contractor-acquired or produced, and the contractor or subcontractor has expressed an interest in acquiring the property, and no other party expresses an interest during agency or GSA screening, the property may be sold to the contractor or subcontractor at acquisition cost.
(3) Printing equipment. Agencies shall report all excess printing equipment to the Public Printer, Government Printing Office, 732 North Capitol Street, NW, Washington, DC 20401, after screening within the agency (see 44 U.S.C. 312). If the Public Printer does not express a need for the equipment within 21 days, the agency shall submit the report to GSA for further use and donation screening as described in paragraph (a) of this subsection.
(4) Non-nuclear hazardous materials, hazardous wastes, and classified items. These items shall be screened in accordance with agency procedures. Report non-nuclear hazardous materials to GSA if the agency has no requirement for them.
(5) Nuclear materials. The possession, use, and transfer of certain nuclear materials are subject to the regulatory controls of the Nuclear Regulatory Commission (NRC). Contracting activities shall screen excess nuclear materials in the following categories:
(i) By-product material. Any radioactive material (except special nuclear material) yielded in or made radioactive by exposure to the radiation incident to producing or using special nuclear material.
(ii) Source material. Uranium or thorium, or any combination thereof, in any physical or chemical form; or ores that contain by weight one-twentieth of 1 percent (0.05 percent) or more of uranium, thorium, or any combination thereof. Source material does not include special nuclear material.
(iii) Special nuclear material. Plutonium, Uranium 233, Uranium enriched in the isotope 233 or in the isotope 235, any other material that the NRC determines to be special nuclear material (but not including source material); or any material artificially enriched by any nuclear material.
Agencies whose property is transferred to other agencies shall not be reimbursed for the property in any manner unless the circumstances of FMR 102-36.285 (41 CFR 102-36.285) apply. The agency receiving the property shall pay any transportation costs that are not the contractor’s responsibility and any costs to pack, crate, or otherwise prepare the property for shipment. The contract administration office shall process appropriate contract modifications. To accelerate plant clearance, the receiving agency shall promptly furnish funding data, and transfer or shipping documents to the contract administration office.
(a) When contractor inventory is processed through the reutilization screening process prescribed in 45.602-2 without success, and provided the property has no commercial value, does not require demilitarization, and does not constitute a danger to public health or welfare, plant clearance officers or other authorized officials may without further approval—
(1) Direct the contractor to destroy the property;
(2) Abandon non-sensitive property at the contractor’s or subcontractor’s premises; or
(3) Abandon sensitive property at the contractor’s or subcontractor’s premises, with contractor consent.
(b) Provided a Government reviewing official at least one level higher than the plant clearance officer or other agency authorized official approves, plant clearance officers or other agency authorized officials may authorize the abandonment, or order the destruction of other contractor inventory at the contractor’s or subcontractor’s premises, in accordance with FMR 102-36.305 through 325 (41 CFR 102-36.305-325) and consistent with the following:
(1) The property is not considered sensitive, does not require demilitarization, has no commercial value or reutilization, transfer or donation potential, and does not constitute a danger to public health or welfare.
(2) The estimated cost of continued care and handling of the property (including advertising, storage and other costs associated with making the sale), exceed the estimated proceeds from its sale.
(c) In lieu of abandonment or its authorized destruction, the plant clearance officer or authorized official may authorize the donation of property including unsold surplus property to public bodies, provided that the property is not sensitive property, does not require demilitarization, and it does not constitute a danger to public health or welfare. The Government will not bear any of the costs incident to such donations.
(d) Unless the property qualifies for one of the exceptions under FMR 102-36.330 (41 CFR 102-36.330), the plant clearance officer or requesting official will ensure prior public notice of such actions of abandonment or destruction consistent with FMR 102-36.325 (41 CFR 102-36.325).
Surplus personal property that has completed screening in accordance with 45.602-3(a) shall be sold in accordance with the policy for the sale of surplus personal property contained in the Federal Management Regulation, at part 102-38 (41 CFR part 102-38). Agencies may specify implementing procedures.
Agencies may use sales center services. Use of such centers for sale of surplus property is authorized when in the best interest of the Government, consistent with contract terms and conditions.
Proceeds of any sale are to be credited to the Treasury of the United States as miscellaneous receipts, unless otherwise authorized by statute or the contract or any subcontract thereunder authorizes the proceeds to be credited to the price or cost of the work (40 U.S.C. 571 and 574).
Agencies should consider the sale of property pursuant to the exchange/sale authority in FMR 102-39 (41 CFR part 102-39) when agencies are acquiring or plan to acquire similar products and other requirements of the authority are satisfied.
The plant clearance officer shall promptly prepare an SF 1424, Inventory Disposal Report, following disposition of the property identified on an inventory disposal schedule and the crediting of any related proceeds. The report shall identify any lost or otherwise unaccounted for property and any changes in quantity or value of the property made by the contractor after submission of the initial inventory disposal schedule. The report shall be provided to the administrative contracting officer or, for termination inventory, to the termination contracting officer, with a copy to the property administrator.
(a) The property administrator should, in coordination with the plant clearance officer, ensure that contractor scrap disposal processes, methods, and practices allow for effective, efficient, and proper disposition and are properly documented in the contractor’s property management procedures.
(b) The property administrator should determine the extent to which separate disposal processing or physical segregation for different scrap types is or may be required. Such scrap may require physical segregation, unique disposal processing, or separate plant clearance reporting. For example, the scope of work may create scrap—
(1) Consisting of sensitive items;
(2) Containing hazardous materials or wastes;
(3) Contaminated with hazardous materials or wastes;
(4) That is classified or otherwise controlled;
(5) Containing precious or strategic metals; or
(6) That is dangerous to public health or safety.
(c) Absent contract terms and conditions to the contrary, the Government may abandon parts removed and replaced from property as a result of normal maintenance actions or removed from property as a result of the repair, maintenance, overhaul, or modification process.


Danny Goulter
Learning to Code
Core Concepts
Identity and Values
September 12, 2021
Learning Plan
September 12, 2021
Emotional Intelligence
September 13, 2021
Exploring Neuroplasticity through having a Growth Mindset
September 21, 2021
Reflecting on My Learning Journey
October 5, 2021
Home
Technical Posts


can you guys pelase test the transition as well? just start a new chain with the following params changed in ~/komodo/src/komodo_defs.h file
#define KOMODO_SAPLING_ACTIVATION<PHONE_NUMBER> // Sat, 24 Nov 2018 15:24:14 GMT
#define KOMODO_SAPLING_DEADLINE<PHONE_NUMBER> // Fri, 30 Nov 2018 16:00:00 GMT
change the activation time 12-24 hours in the future in a new chain.