Introduction
LLADD is an extensible implementation of the ARIES algorithm, a write-ahead-logging system that provides reliable transactional storage.
Traditionally, write-ahead-logging schemes have been closely coupled to a relational database or other high-level system, making if difficult to make full use of their functionality without making significant changes to complex and tightly coupled code.
LLADD allows application developers to make such changes easily, by providing clean interfaces between its subsystems and by exporting enough of its functionality to application developers to allow custom, application-specific transactional storage mechanisms to be developed easily.
Features
LLADD is still under heavy development, and we anticipate changes to a number of the API's that it exports. Here is a list of some of the features that we would like to include in the future.
Implemented and in-progress features are marked with a "*":
- Extensibility
- Custom log entries*
- Buffer manager API*
- Page layout customization*
- Collections of records*
- Application specific locking policies
- Crash Recovery
- ARIES style Analysis/Full Redo/Partial Undo*
- Fuzzy Checkpointing (for online backups)
- Log Truncation
- Storage features
- Storage of variable length records*
- Expandable, on-disk arrays of records*
- Linear Hash Table *
- B-Tree indices
- Simple interface for definition of new storage mechanisms*
- Concurrency
- Multi-Threaded*
- Lock manager to allow transactions to run at varying degrees of consistency
- Networking support (for clusters of computers)
- Transactions
- Abort / Commit*
- Prepare (for two phase commit implementations)*
- Savepoints (To allow applications to partially rollback transactions)
A design goal of our library is to avoid imposing any unnecessary structure upon the applications that make use of it. Therefore, the storage structures listed above can be used as starting points for application specific storage mechanisms, although they are also designed to be useful "out of the box".


Pdf Details
Success!
pdf saved successfully
Id:
Name:
File:
Notes:
<%= description %>
Save
Update
View/Download
Delete


{% extends 'base.html' %} {% block page_title %}Unsubscribe from our mailing list{% endblock %} {% block page_headline %}Unsubscribe from our mailing list{% endblock %} {% block page_content %}
To stop receiving email notifications from DVO Alerts, please enter your email address below. We'll send you an unsubscribe link via email.


Home
Angry Cats
Cats in Random Places
Cats with Friends
Cottagecore Cats
Fat Cats
Fluffy Cats
Cats in Hats
Sad Cats
Sleepy Cats
Small Cats
Stylish Cats
Cats in Glasses
Submit your picture!
⤷COTTAGECORE CATS
Have any cat pictures you want to share?
Submit your picture!


ModelSEED is a resource for the reconstruction, exploration, comparison, and analysis of metabolic models.
This site and the tools and data hosted by it were developed and are maintained with support from the U.S. Department of Energy, Office of Biological and Environmental Research; under contract DE-AC02-06CH11357 (KBase project) and by the National Science Foundation under grant numbers PGRP-1025398 (for PlantSEED), MCB-1153357 (for ModelSEED modeling), PGRP-1444202 (for ModelSEED biochemistry), and MCB-1611952 (for ModelSEED modeling).
The ModelSEED resource is based upon work supported by the U.S. Department of Energy, Office of Biological and Environmental Research; under contract DE-AC02-06CH11357 and by the National Science Foundation grant number MCB-1153357.
The PlantSEED resource was created with support by the National Science Foundation Grant IOS-1025398, by an endowment from the C. V. Griffin Sr. Foundation, and by the Office of Science, Office of Biological and Environmental Research, of the US Department of Energy (DOE) under Contract DE-ACO2-06CH11357, as part of the DOE Systems Biology Knowledgebase.
The National Science Foundation Grant IOS-1444202 has provided support for both the improvement of the PlantSEED resource and the production of new modeling tools within ModelSEED to be able to annotate plant genomes using the PlantSEED platform and develop plant metabolism models. This grant also supports the implementation of four PlantSEED metabolic modeling workshops to train faculty, post-doctoral fellows and graduate students of American universities (with an emphasis on recruitment of faculty from minority serving institutions) in the use of these novel computational tools.


--- layout: post title: cocoakuler date: '2008-01-23T08:04:42+00:00' tags: [] tumblr_url: http://backlog.robbevan.com/post/24430420/cocoakuler ---
CocoaKuler


JEFFSON'S FOUNDATION
Everyone deserves to be happy
MENU
Home
About Us
Jeffson's Foundation
The Founder
Our Team
Patrons
Gallery
Contact Us
Facebook
Twitter
Linkdln
Whatsapp
© jeffsonsfoundation.org 2016


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
32
33 /*!
34 * ======== IUIATransfer ========
35 */
36 interface IUIATransfer inherits xdc.runtime.IFilterLogger {
37
38 enum TransferType {
39 TransferType_RELIABLE = 0,
40 TransferType_LOSSY = 1
41 }
42
43 /*! @_nodoc
44 * ======== Logger Priority enumeration ========
45 */
46 enum Priority {
47 Priority_LOW = 0, /*! low priority */
48 Priority_STANDARD = 1, /*! default priority */
49 Priority_HIGH = 2, /*! use for critical errors, etc. */
50 Priority_SYNC = 3 /*! used only by LogSync's logger */
51 };
52
53 /*!
54 * ======== getPtrToQueueDescriptorMeta ========
55 * Each logger instance has a unique queue descriptor address that is
56 * stored in the Event Record header to identify itself to the host.
57 * This metaonly configuration parameter allows the UIA Metadata to
58 * determine what the address is for each statically created logger instance
59 * in order to emit XML code to allow the host to look up information about
60 * the logger instance (such as its name) based on the queue descriptor
61 * address that is stored in the event record header.
62 *
63 * The pointer is returned per instance of the logger module. The
64 * instance object is passed to the function as the first argument.
65 */
66 metaonly function getPtrToQueueDescriptorMeta(inst);
67 /*!
68 * ======== setPtrToQueueDescriptorMeta ========
69 * Sets the queue descriptor address in the logger's object instance data.
70 */
71 metaonly function setPtrToQueueDescriptorMeta(inst,queueDescriptorAdrs);
72 /*!
73 * ======== getLoggerInstanceId ========
74 * returns the id of this logger instance.
75 */
76 metaonly function getLoggerInstanceId(inst);
77
78 /*! @_nodoc
79 * ======== getLoggerPriority ========
80 * returns the priority of this logger instance.
81 */
82 metaonly function getLoggerPriority(inst);
83
84 /*! @_nodoc
85 * ======== setLoggerPriority ========
86 * sets the priority of this logger instance.
87 */
88 metaonly function setLoggerPriority(inst, priority);
89
90 /*!
91 * ======== MetaData ========
92 * This data is added to the RTA MetaData file to support stop mode RTA.
93 */
94 @XmlDtd metaonly struct MetaData {
95 Int instanceId;
96 Int priority;
97 }
98
99 instance:
100 config TransferType transferType = TransferType_LOSSY;
101 TransferType getTransferType();
102
103 /*!
104 * ======== getContents =========
105 * Fills buffer that is passed in with unread data, up to size bytes
106 * in length.
107 *
108 * The logger is responsible for ensuring that no partial event records
109 * are stored in the buffer. Bytes are in target endianness.
110 *
111 * @param(hdrBuf) Ptr to a buffer that is at least <size> bytes in length
112 * @param(size) The max number of bytes to be read into the buffer
113 * @param(cpSize) The number of bytes actually copied
114 *
115 * @a(return) returns false if logger has no more records to read
116 */
117 @DirectCall
118 Bool getContents(Ptr hdrBuf, SizeT size, SizeT *cpSize);
119
120 /*!
121 * ======== isEmpty =========
122 * Returns true if the transfer buffer has no unread data
123 *
124 * @a(return) true if no unread data
125 */
126 @DirectCall
127 Bool isEmpty();
128
129 /*!
130 * ======== getMaxLength =========
131 */
132 @DirectCall
133 SizeT getMaxLength();
134
135 /*!
136 * ======== getInstanceId ========
137 * Returns an ID value that uniquely identifies this instance of the logger.
138 *
139 * Note that a value of 0 is reserved to indicate that the instance ID has
140 * not been initialized yet and a unique value needs to be generated.
141 */
142 @DirectCall
143 UInt16 getInstanceId();
144
145 /*! @_nodoc
146 * ======== priority ========
147 * The priority of the logger is used to detrmine which event packets to
148 * transfer to the host first.
149 *
150 * A value of Priority_STANDARD (default) indicates normal priority.
151 * Higher values indicate higher priority.
152 * @see #Priority
153 */
154 config IUIATransfer.Priority priority = Priority_STANDARD;
155
156 /*! @_nodoc
157 * ======== getPriority ========
158 * Returns a 2b value that identifies the relative priority of the event
159 * log.
160 *
161 * A value of 1 (default) indicates normal priority. Higher values indicate
162 * higher priority.
163 * @see #Priority
164 */
165 @DirectCall
166 Priority getPriority();
167
168
169 /*! @_nodoc
170 * ======== setPriority ========
171 * Sets a 2b value that identifies the relative priority of the event
172 * log.
173 *
174 * A value of 1 (default) indicates normal priority. Higher values indicate
175 * higher priority.
176 * @see #Priority
177 */
178 @DirectCall
179 Void setPriority(Priority priority);
180
181 /*!
182 * ======== reset ========
183 * Reset a log to empty state and enable it
184 *
185 * @a(WARNING) This method is not synchronized with other instance
186 * methods and, as a result, it must never be called when there is a
187 * chance that another instance method is currently in operation or
188 * when another method on this instance may preempt this call.
189 */
190 Void reset();
191
192 metaonly config Ptr ptrToQueueDescriptorMeta = null;
193 }


air pollution awareness residents health Ningbo haze knowledge quality ambient face {border-style rate study Health masks px;} #ffffff;} level <. .-. Environ Public practices related attitudes measures China analysis protection protective studies No age environmental px; residents’ respondents taken {font-family Yes Table data factors font-size levels pollution. significant survey (/) Int Program Technology [], adverse age, associated believed demographic double; elderly government high information lower manuscript participants used years Control Disease KAP attention border-color border-width cities concern effects exposure final haze. important improve index logistic make primary public p < .). questionnaire reduce regression relatively risk satisfied selected shown solid; study, type using {font-style {font-weight Ningbo, Perspect Res Science Tianfeng aggravation bold community cotton courier; designed education educational em; gauze group groups health. internet knowledge, occupation outdoor particulate people pollution, possible problem provide pt;} research revised rural sample showed significantly unconditional understanding urban van -()


DataColumnDouble Undocumented init(_:) Undocumented © 2016 . All rights reserved. (Last updated: 2016-12-14) Generated by jazzy ♪♫ v0.7.2, a Realm project.


Constraint vs Other Layouts- A Battle towards performance Part-3
Blog by theDroidLady
Introduction
Now we already know various tools that can be used for measuring the performance of layouts with different ViewGroups we have in Android.
Here, we are sharing the result for different layouts testing performed on Coolpad and Android 6.0 Marshmallow.
I also created a Github project for your reference. You can check out the code for various layouts there.
Disclaimer:
These results may vary device to device and OEMs as well because optimizations vary from device to device and OS level too. You can check with your device.
Here are the results -
1) View inside another View in the centre-
2) RecyclerView with 100 Items
3) Simple UI with TextViews and Images
4) Complex UI with Images, Text, ScrollView, Buttons etc.
Note*: Now there are lot enhancements with various viewgroups, so these results may vary for you.
Please Note:- Always measure your layout performance through systrace and GPU overdraw before finalizing any layout. These results can vary from device to device and with respect to the OS version too. On average, however, the results will remain the same.
Conclusion -
The complete analysis of the various layouts tells us -
1) With Complex UI where we can have more hierarchies, it is wise to use constraint layouts.
2) If you are using LinearLayout with weights/RelativeLayout with hierarchies, replace them with Constraint layout.
3) For simple layouts with just one view centred on the screen, go for Frame layouts.
4) For simple screens, where you have to place views just horizontally and vertically, go for LinearLayout.
References -
1) Three-key-lessons-when-migrating-to-constraintlayout
2) Android-constraint-layout-performance
3) Systrace


pacat
Section: User Commands (1)Updated: User
Index Return to Main Contents
NAME
pacat - Play back or record raw or encoded audio streams on a PulseAudio sound serverSYNOPSIS
paplay [options] [FILE]parecord [options] [FILE]
pacat [options] [FILE]
parec [options] [FILE]
pamon [options] [FILE]
pacat --help
DESCRIPTION
pacat is a simple tool for playing back or capturing raw or encoded audio files on a PulseAudio sound server.OPTIONS
- -h | --help
- Show help.
- --version
- Show version information.
- -r | --record
- Capture audio data and write it to the specified file or to STDOUT if none is specified. If the tool is called under the name parec this is the default.
- -p | --playback
- Read audio data from the specified file or STDIN if none is specified, and play it back. If the tool is called under the name pacat this is the default.
- -v | --verbose
- Enable verbose operation. Dumps the current playback time to STDERR during playback/capturing.
- -s | --server=SERVER
- Choose the server to connect to.
- -d | --device=SINKORSOURCE
- Specify the symbolic name of the sink/source to play/record this stream on/from.
- -n | --client-name=NAME
- Specify the client name paplay shall pass to the server when connecting.
- --stream-name=NAME
- Specify the stream name paplay shall pass to the server when creating the stream.
- --volume=VOLUME
- Specify the initial playback volume to use. Choose a value between 0 (silent) and 65536 (100% volume).
- --rate=SAMPLERATE
- Capture or play back audio with the specified sample rate. Defaults to 44100 Hz.
- --format=FORMAT
- Capture or play back audio with the specified sample format. Specify one of u8, s16le, s16be, s32le, s32be, float32le, float32be, ulaw, alaw, s32le, s32be, s24le, s24be, s24-32le, s24-32be. Depending on the endianess of the CPU the formats s16ne, s16re, s32ne, s32re, float32ne, float32re, s32ne, s32re, s24ne, s24re, s24-32ne, s24-32re (for native, resp. reverse endian) are available as aliases. Defaults to s16ne.
- --channels=CHANNELS
- Capture or play back audio with the specified number of channels. If more than two channels are used it is recommended to use the --channel-map option below. Defaults to 2.
- --channel-map=CHANNELMAP
- Explicitly choose a channel map when playing back this stream. The argument should be a comma separated list of channel names: front-left, front-right, mono, front-center, rear-left, rear-right, rear-center, lfe, front-left-of-center, front-right-of-center, side-left, side-right, top-center, top-front-center, top-front-left, top-front-right, top-rear-left, top-rear-right, top-rear-center, or any of the 32 auxiliary channel names aux0 to aux31.
- --fix-format
- If passed, the sample format of the stream is changed to the native format of the sink the stream is connected to.
- --fix-rate
- If passed, the sampling rate of the stream is changed to the native rate of the sink the stream is connected to.
- --fix-channels
- If passed, the number of channels and the channel map of the stream is changed to the native number of channels and the native channel map of the sink the stream is connected to.
- --no-remix
- Never upmix or downmix channels.
- --no-remap
- Never remap channels. Instead of mapping channels by their name this will match them solely by their index/order.
- --latency=BYTES
- Explicitly configure the latency, with a time specified in bytes in the selected sample format. If left out the server will pick the latency, usually relatively high for power saving reasons. Use either this option or --latency-msec, but not both.
- --latency-msec=MSEC
- Explicitly configure the latency, with a time specified in miliseconds. If left out the server will pick the latency, usually relatively high for power saving reasons. Use either this option or --latency, but not both.
- --process-time=BYTES
- Explicitly configure the process time, with a time specified in bytes in the selected sample format. If left out the server will pick the process time. Use either this option or --process-time-msec, but not both.
- --process-time-msec=MSEC
- Explicitly configure the process time, with a time specified in miliseconds. If left out the server will pick the process time. Use either this option or --process-time, but not both.
- --property=PROPERTY=VALUE
- Attach a property to the client and stream. May be used multiple times
- --raw
- Play/record raw audio data. This is the default if this program is invoked as pacat , parec or pamon
- --file-format[=FFORMAT]
- Play/record encoded audio data in the file format specified. This is the default if this program is invoked as paplay and parecord
- --list-file-formats
- List supported file formats.
AUTHORS
The PulseAudio Developers <mzchyfrnhqvb (at) 0pointer (dot) net>; PulseAudio is available from http://pulseaudio.org/SEE ALSO
pulseaudio(1), pactl(1)
Index
This document was created by man2html, using the manual pages.
Time: 05:29:07 GMT, December 24, 2015


Network interfaces for receiving mail
inet_interfaces
This parameter specifies the network interface addresses that this mail system
receives mail on.
By default, the software claims all active interfaces on the machine. The
parameter also controls delivery of mail to<EMAIL_ADDRESS>Typical configurations are:
- all
- $myhostname
- $myhostname, localhost


How Would You Like to Pay?
Note: don't enter any actual credit card info!
Note: don't enter any actual credit card info!


ACLOCAL(1) User Commands ACLOCAL(1) NAME aclocal - manual page for aclocal 1.11.6 SYNOPSIS aclocal [OPTIONS] ... DESCRIPTION Generate `aclocal.m4' by scanning `configure.ac' or `configure.in' OPTIONS --automake-acdir=DIR directory holding automake-provided m4 files --system-acdir=DIR directory holding third-party system-wide files --diff[=COMMAND] run COMMAND [diff -u] on M4 files that would be changed (implies --install and --dry-run) --dry-run pretend to, but do not actually update any file --force always update output file --help print this help, then exit -I DIR add directory to search list for .m4 files --install copy third-party files to the first -I directory --output=FILE put output in FILE (default aclocal.m4) --print-ac-dir print name of directory holding system-wide third-party m4 files, then exit --verbose don't be silent --version print version number, then exit -W, --warnings=CATEGORY report the warnings falling in CATEGORY Warning categories include: `syntax' dubious syntactic constructs (default) `unsupported' unknown macros (default) `all' all the warnings (default) `no-CATEGORY' turn off warnings in CATEGORY `none' turn off all the warnings `error' treat warnings as errors AUTHOR Written by Tom Tromey<EMAIL_ADDRESS>and Alexandre Duret-Lutz<EMAIL_ADDRESS>REPORTING BUGS Report bugs to<EMAIL_ADDRESS>GNU Automake home page: <http://www.gnu.org/software/automake/>. General help using GNU software: <http://www.gnu.org/gethelp/>. COPYRIGHT Copyright © 2011 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO The full documentation for aclocal is maintained as a Texinfo manual. If the info and aclocal programs are properly installed at your site, the command info aclocal should give you access to the complete manual. aclocal 1.11.6 July 2012 ACLOCAL(1)


The accommodation for the retreat is yet to be finalized. The price of the retreat will depend
entirely on the location selected, please Apply for the retreat and
you will be updated when more information is available. The price will include all costs during
the retreat, excluding the transportation to and from the location. All meals and stay will be
included in the price.
The location is guaranteed to be an eco-resort in the midst of a beautiful natural setting.
All amenities will be modern and up to a good standard, to facilitate a comfortable and safe
environment for your adventure.


%= processTemplate('_head') %>
Established in 1899
The Pat Murphy Electric, Inc. team is extensively trained in the latest electrical and data technologies, attention to detail, and listening to the needs and concerns of our customers.
Pat Murphy Electric, Inc. is a member of the Independent Electrical Contractors Association which provides a four year apprenticeship program and advanced courses for the electrical technician. Most of our employees have attended, and some are currently attending, this program to keep current with the changing technology in the electrical industry.
Pat Murphy Electric, Inc. is a member of the Independent Electrical Contractors Association which provides a four year apprenticeship program and advanced courses for the electrical technician. Most of our employees have attended, and some are currently attending, this program to keep current with the changing technology in the electrical industry.


--- layout: default title: Colors - Text ---
When referencing color in your stylesheet overrides, please ensure you're using one of the following variables. These values provide the core color palette for Crossroads' brand identity and have been used to override the Bootstrap defaults, where noted below.
Here you'll find additional text utility classes, altering the color of any given text. These classes can be used similarly to the contextual color classes found in Bootstrap's documentation.
A dark background has been applied to the .text-white
code
example so you can see the text and the class' impact on said text.
Lorem ipsum dolor sit amet, consectetur ...
Lorem ipsum dolor sit amet, consectetur ...
Lorem ipsum dolor sit amet, consectetur ...
Lorem ipsum dolor sit amet, consectetur ...
Lorem ipsum dolor sit amet, consectetur ...
{% endexample %}


Everything you need to know about me...
I like Hiking, Movies, Learning, Sandwiches, Boating, Android, Fishing, Roadtrips, Cooking, Fitness, Camping, Industrial Settings, Adventures, Grey, Biking, Craft Beer, Coffee, People, National Parks, New Technology, and Netflix
I'm currently working on
JMU.IO
I'm currently reading
The Martian
I'm currently watching
The Flash (Netflix)
I'm currently playing
Destiny (PS4)
I'm currently listening to
Indie Chillout. (Spotify Playlist)
JMU.io
James Madison University campus information available via public APIs so that students, faculty, really anyone can easily develop university related apps without having to worry about maintaing the data.
American Road Trip
This was one of the greatest adventures of my life. Along the way I built a quick website to document my travels. Only regret was that I didn't take enough pictures along the way! Hope I can do it again some day.


Voy a Tener Suerte! | Fortnite Versus - get to know your friends and enemies 😎💪🕹
{% include 'includes/_imports.html' %}
{% include 'includes/_googleadsense.html' %}
{% include 'includes/_navbar.html' %}
¿Dónde Aterrizamos?
siento que esta vez sí que vamos a tener suerte...
{% include 'includes/_cookiealert.html' %}
{% include 'includes/_googleanalytics.html' %}
{% include 'includes/_googleadsense.html' %}


The Surface Pro is a first generation 2-in-1 detachable of the Microsoft Surface series, designed and manufactured by Microsoft. The device ran a 64-bit version of Windows 8 Pro operating system with a free upgrade possibility to Windows 8.1 Pro, and eventually also Windows 10. Initially announced as Surface for Windows 8 Pro on June 18, 2012, at a Los Angeles event.
Microsoft later renamed the device to Surface Pro, and launched it on February 9, 2013.
The Surface Pro shares a lot of its design traits with its lower cost counterpart, the original Surface hybrid tablet, announced on the same day. Both have the dark VaporMg[11] coating over the same magnesium body and a 10-point multi-touch enabled 10.6 inches (27 cm) screen with crack resistant Gorilla Glass. The Wifi is 802.11 a/b/g/n.
However, the resolution on the Surface Pro is higher and is 1920x1080, and the screen has a Wacom digitizer for pen input. Surface Pro runs a dual-core 1.7 GHz Intel Core i5-3317U CPU, with a Turbo Boost frequency of up to 2.6 GHz with a built-in Intel HD Graphics 4000. It has 4 GB of memory and a 64 or 128 GB solid-state drive. Unique to the Surface and Surface Pro is the kickstand which can be flipped out from the back, propping the device up. The kickstand comes out of the devices at a 22 degree angle, the same angle the edges of the device are angled at.
If you want to buy, interested or have a question, you can reach to Microsoft team from Here.


Hi Everyone! My name is Marcus Jensen, thank you for visiting my Webpage. I am a born and raised Oregonian (my mom always jokes that we are 2 of the 5 people living in Oregon who were actually born here). I came to the program having done some pre-work surrounding HTML, CSS and Computer Programing in general. With Epicodus, I’m hoping to: strengthen my coding skills, meet an awesome network of people, and be the best developer I can possibly be. Please scroll down to learn a bit more about me, and my previous experiences!
At Zapproved, I began as a Sales Development Representative. In this position, it was my responsibility to follow up on inbound leads that had been generated by marketing efforts. I was quickly promoted out of that role to an Enterprise Business Representative. In this position I outbound prospected key decision makers within our strategic account territory, and set meetings for the Account Executive Team. My next role, Inside Sales Representative is responsible for fielding these meetings for further qualification.
At AskNicely, I was responsible for running the full sales cycle from initial meeting through closed deal. In this position I learned all about: the full sales funnel, framing our product as the obvious choice over our competition, and engaging the appropriate parties on the buyer side to get the deal closed.
I decided to participate in a summer course during my time at UO in Copenhagen. This summer’s curriculum was heavily focused on entrepreneurship. It was a lot of fun to study business in a different part of the world and meet new friends from different countries!
At the U of O, my studies were heavily focused in the area of Business. Mid-way through my junior year, I discovered my passion for coding and the infinite potential it held, so I decided to pick up that minor. I was also heavily involved in student life and extracurricular activities outside of my classwork.
I’m a big believer that the most successful people in the world are interdisciplinary. My ultimate goal is to start a SAAS business. In my opinion, to be an excellent founder you need to bring some key skills to the table. The two most important skills when starting a software company are: knowing how to sell, and knowing how to code. I’ve spent the last five years learning how SAAS software is bought and sold, and in my free time have tinkered with building it. I look forward to buckling down and getting good at writing software!
Here is my first project - Utilized HTML to build
Here is my second project - Utilized HTML and CSS to build
Here is a third project - Utilized HTML and CSS to build


Henry Cavill auditioned for Bond but was told he was a 'little chubby'
Former Superman said comment led to better health
by Lisa Respers France, CNNLONDON - He may have been the "Man of Steel," but Henry Cavill says he hasn't always been in the best shape.
In a recent interview with Men's Health, the actor revealed that in the mid-'00s he tried out for the role of James Bond.
The screen test involved Cavill walking out of a bathroom wrapped in a towel.
It didn't go well, he said.
"I probably could have prepared better," he said. "I remember the director, Martin Campbell, saying, 'Looking a little chubby there, Henry.' I didn't know how to train or diet. And I'm glad Martin said something, because I respond well to truth. It helps me get better."
The role instead went to Daniel Craig and Cavill became one of the stars the Showtime historical series "The Tudors."
He later became Superman in the DC films, but before that he had to show off his physique in the 2011 film "Immortals."
"It was my first experience working on a movie and having my shirt off for most of the damn time," Cavill said.
The actor went on a strict six-month diet and did extensive martial-arts training.
"It's very emotionally taxing," he said. "When you add the lack of food and the pressure on top of that, it's tough."
He also kicked things up a notch for his starring role as Superman in "Man of Steel."
Cavill said he takes seriously playing such physical characters.
"I know what it feels like to go from out of shape to in shape [afterward] I'll look at myself like, 'Man, well done,'" he said. "It's not like I'm a golden god — I'm just proud of what I achieved."


MY.EARTH is a community and environmental app. It creates a visualization of pollution levels changing over time. It aims at raising awareness regarding pollution issues around the globe, both locally and internationaly.
It shows how space data can help on earth, looking at pollution levels from a global point of view. It gathers satellite pictures and environmental datas from NASA, elected organisations internationally, as well as city admninistrators, national organisation and individual data collectors locally. The visualization enhances pollution issues and improvement over time as it spans from 1970 to nowadays. Beginners and specialists can use this app to get accurate data or as an educational tool on environmental matters.


{%extends 'base.html' %} {% block title %}
Address either are not inputed or the same to the old one.
Price either not inputed or not a number.


001/* 002 * Licensed to the Apache Software Foundation (ASF) under one 003 * or more contributor license agreements. See the NOTICE file 004 * distributed with this work for additional information 005 * regarding copyright ownership. The ASF licenses this file 006 * to you under the Apache License, Version 2.0 (the 007 * "License"); you may not use this file except in compliance 008 * with the License. You may obtain a copy of the License at 009 * 010 * http://www.apache.org/licenses/LICENSE-2.0 011 * 012 * Unless required by applicable law or agreed to in writing, 013 * software distributed under the License is distributed on an 014 * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 015 * KIND, either express or implied. See the License for the 016 * specific language governing permissions and limitations 017 * under the License. 018 */ 019package org.apache.shiro.realm; 020 021import org.apache.shiro.authc.AuthenticationException; 022import org.apache.shiro.authc.AuthenticationInfo; 023import org.apache.shiro.authc.AuthenticationToken; 024import org.apache.shiro.authc.IncorrectCredentialsException; 025import org.apache.shiro.authc.UsernamePasswordToken; 026import org.apache.shiro.authc.credential.AllowAllCredentialsMatcher; 027import org.apache.shiro.authc.credential.CredentialsMatcher; 028import org.apache.shiro.authc.credential.SimpleCredentialsMatcher; 029import org.apache.shiro.cache.Cache; 030import org.apache.shiro.cache.CacheManager; 031import org.apache.shiro.subject.PrincipalCollection; 032import org.apache.shiro.util.Initializable; 033import org.slf4j.Logger; 034import org.slf4j.LoggerFactory; 035 036import java.util.concurrent.atomic.AtomicInteger; 037 038 039/** 040 * A top-level abstract implementation of the <tt>Realm</tt> interface that only implements authentication support 041 * (log-in) operations and leaves authorization (access control) behavior to subclasses. 042 *
Authentication Caching
 043 * For applications that perform frequent repeated authentication of the same accounts (e.g. as is often done in 044 * REST or Soap applications that authenticate on every request), it might be prudent to enable authentication 045 * caching to alleviate constant load on any back-end data sources. 046 *
 047 * This feature is disabled by default to retain backwards-compatibility with Shiro 1.1 and earlier. It may be 048 * enabled by setting {@link #setAuthenticationCachingEnabled(boolean) authenticationCachingEnabled} = {@code true} 049 * (and configuring Shiro with a {@link CacheManager} of course), but NOTE: 050 *
 051 * ONLY enable authentication caching if either of the following is true for your realm implementation: 052 *
 053 *
The {@link #doGetAuthenticationInfo(org.apache.shiro.authc.AuthenticationToken) doGetAuthenticationInfo} 054 * implementation returns {@code AuthenticationInfo} instances where the 055 * {@link org.apache.shiro.authc.AuthenticationInfo#getCredentials() credentials} are securely obfuscated and NOT 056 * plaintext (raw) credentials. For example, 057 * if your realm references accounts with passwords, that the {@code AuthenticationInfo}'s 058 * {@link org.apache.shiro.authc.AuthenticationInfo#getCredentials() credentials} are safely hashed and salted or otherwise 059 * fully encrypted.

 060 *
The {@link #doGetAuthenticationInfo(org.apache.shiro.authc.AuthenticationToken) doGetAuthenticationInfo} 061 * implementation returns {@code AuthenticationInfo} instances where the 062 * {@link org.apache.shiro.authc.AuthenticationInfo#getCredentials() credentials} are plaintext (raw) AND the 063 * cache region storing the {@code AuthenticationInfo} instances WILL NOT overflow to disk and WILL NOT transmit cache 064 * entries over an unprotected (non TLS/SSL) network (as might be the case with a networked/distributed enterprise cache). 065 * This should be the case even in private/trusted/corporate networks.
 066 *
 067 *
 068 * These points are very important because if authentication caching is enabled, this abstract class implementation 069 * will place AuthenticationInfo instances returned from the subclass implementations directly into the cache, for 070 * example: 071 *
 072 * cache.put(cacheKey, subclassAuthenticationInfoInstance); 073 *
 074 *
 075 * Enabling authentication caching is ONLY safe to do if the above two scenarios apply. It is NOT safe to enable under 076 * any other scenario. 077 *
 078 * When possible, always represent and store credentials in a safe form (hash+salt or encrypted) to eliminate plaintext 079 * visibility. 080 *
Authentication Cache Invalidation on Logout
 081 * If authentication caching is enabled, this implementation will attempt to evict (remove) cached authentication data 082 * for an account during logout. This can only occur if the 083 * {@link #getAuthenticationCacheKey(org.apache.shiro.authc.AuthenticationToken)} and 084 * {@link #getAuthenticationCacheKey(org.apache.shiro.subject.PrincipalCollection)} methods return the exact same value. 085 *
 086 * The default implementations of these methods expect that the 087 * {@link org.apache.shiro.authc.AuthenticationToken#getPrincipal()} (what the user submits during login) and 088 * {@link #getAvailablePrincipal(org.apache.shiro.subject.PrincipalCollection) getAvailablePrincipal} (what is returned 089 * by the realm after account lookup) return 090 * the same exact value. For example, the user submitted username is also the primary account identifier. 091 *
 092 * However, if your application uses, say, a username for end-user login, but returns a primary key ID as the 093 * primary principal after authentication, then you will need to override either 094 * {@link #getAuthenticationCacheKey(org.apache.shiro.authc.AuthenticationToken) getAuthenticationCacheKey(token)} or 095 * {@link #getAuthenticationCacheKey(org.apache.shiro.subject.PrincipalCollection) getAuthenticationCacheKey(principals)} 096 * (or both) to ensure that the same cache key can be used for either object. 097 *
 098 * This guarantees that the same cache key used to cache the data during authentication (derived from the 099 * {@code AuthenticationToken}) will be used to remove the cached data during logout (derived from the 100 * {@code PrincipalCollection}). 101 *
Unmatching Cache Key Values
 102 * If the return values from {@link #getAuthenticationCacheKey(org.apache.shiro.authc.AuthenticationToken)} and 103 * {@link #getAuthenticationCacheKey(org.apache.shiro.subject.PrincipalCollection)} are not identical, cached 104 * authentication data removal is at the mercy of your cache provider settings. For example, often cache 105 * implementations will evict cache entries based on a timeToIdle or timeToLive (TTL) value. 106 *
 107 * If this lazy eviction capability of the cache product is not sufficient and you want discrete behavior 108 * (highly recommended for authentication data), ensure that the return values from those two methods are identical in 109 * the subclass implementation. 110 * 111 * @since 0.2 112 */ 113public abstract class AuthenticatingRealm extends CachingRealm implements Initializable { 114 115 //TODO - complete JavaDoc 116 117 private static final Logger log = LoggerFactory.getLogger(AuthenticatingRealm.class); 118 119 private static final AtomicInteger INSTANCE_COUNT = new AtomicInteger(); 120 121 /** 122 * The default suffix appended to the realm name used for caching authentication data. 123 * 124 * @since 1.2 125 */ 126 private static final String DEFAULT_AUTHENTICATION_CACHE_SUFFIX = ".authenticationCache"; 127 128 /** 129 * Credentials matcher used to determine if the provided credentials match the credentials stored in the data store. 130 */ 131 private CredentialsMatcher credentialsMatcher; 132 133 134 private Cache<Object, AuthenticationInfo> authenticationCache; 135 136 private boolean authenticationCachingEnabled; 137 private String authenticationCacheName; 138 139 /** 140 * The class that this realm supports for authentication tokens. This is used by the 141 * default implementation of the {@link Realm#supports(org.apache.shiro.authc.AuthenticationToken)} method to 142 * determine whether or not the given authentication token is supported by this realm. 143 */ 144 private Class<? extends AuthenticationToken> authenticationTokenClass; 145 146 /*------------------------------------------- 147 | C O N S T R U C T O R S | 148 ============================================*/ 149 public AuthenticatingRealm() { 150 this(null, new SimpleCredentialsMatcher()); 151 } 152 153 public AuthenticatingRealm(CacheManager cacheManager) { 154 this(cacheManager, new SimpleCredentialsMatcher()); 155 } 156 157 public AuthenticatingRealm(CredentialsMatcher matcher) { 158 this(null, matcher); 159 } 160 161 public AuthenticatingRealm(CacheManager cacheManager, CredentialsMatcher matcher) { 162 authenticationTokenClass = UsernamePasswordToken.class; 163 164 //retain backwards compatibility for Shiro 1.1 and earlier. Setting to true by default will probably cause 165 //unexpected results for existing applications: 166 this.authenticationCachingEnabled = false; 167 168 int instanceNumber = INSTANCE_COUNT.getAndIncrement(); 169 this.authenticationCacheName = getClass().getName() + DEFAULT_AUTHENTICATION_CACHE_SUFFIX; 170 if (instanceNumber > 0) { 171 this.authenticationCacheName = this.authenticationCacheName + "." + instanceNumber; 172 } 173 174 if (cacheManager != null) { 175 setCacheManager(cacheManager); 176 } 177 if (matcher != null) { 178 setCredentialsMatcher(matcher); 179 } 180 } 181 182 /*-------------------------------------------- 183 | A C C E S S O R S / M O D I F I E R S | 184 ============================================*/ 185 186 /** 187 * Returns the CredentialsMatcher used during an authentication attempt to verify submitted 188 * credentials with those stored in the system. 189 *
 190 *
Unless overridden by the {@link #setCredentialsMatcher setCredentialsMatcher} method, the default 191 * value is a {@link org.apache.shiro.authc.credential.SimpleCredentialsMatcher SimpleCredentialsMatcher} instance. 192 * 193 * @return the CredentialsMatcher used during an authentication attempt to verify submitted 194 * credentials with those stored in the system. 195 */ 196 public CredentialsMatcher getCredentialsMatcher() { 197 return credentialsMatcher; 198 } 199 200 /** 201 * Sets the CrendialsMatcher used during an authentication attempt to verify submitted credentials with those 202 * stored in the system. The implementation of this matcher can be switched via configuration to 203 * support any number of schemes, including plain text comparisons, hashing comparisons, and others. 204 *
 205 *
Unless overridden by this method, the default value is a 206 * {@link org.apache.shiro.authc.credential.SimpleCredentialsMatcher} instance. 207 * 208 * @param credentialsMatcher the matcher to use. 209 */ 210 public void setCredentialsMatcher(CredentialsMatcher credentialsMatcher) { 211 this.credentialsMatcher = credentialsMatcher; 212 } 213 214 /** 215 * Returns the authenticationToken class supported by this realm. 216 *
 217 *
The default value is <tt>{@link org.apache.shiro.authc.UsernamePasswordToken UsernamePasswordToken.class}</tt>, since 218 * about 90% of realms use username/password authentication, regardless of their protocol (e.g. over jdbc, ldap, 219 * kerberos, http, etc). 220 *
 221 *
If subclasses haven't already overridden the {@link Realm#supports Realm.supports(AuthenticationToken)} method, 222 * they must {@link #setAuthenticationTokenClass(Class) set a new class} if they won't support 223 * <tt>UsernamePasswordToken</tt> authentication token submissions. 224 * 225 * @return the authenticationToken class supported by this realm. 226 * @see #setAuthenticationTokenClass 227 */ 228 public Class getAuthenticationTokenClass() { 229 return authenticationTokenClass; 230 } 231 232 /** 233 * Sets the authenticationToken class supported by this realm. 234 *
 235 *
Unless overridden by this method, the default value is 236 * {@link org.apache.shiro.authc.UsernamePasswordToken UsernamePasswordToken.class} to support the majority of applications. 237 * 238 * @param authenticationTokenClass the class of authentication token instances supported by this realm. 239 * @see #getAuthenticationTokenClass getAuthenticationTokenClass() for more explanation. 240 */ 241 public void setAuthenticationTokenClass(Class<? extends AuthenticationToken> authenticationTokenClass) { 242 this.authenticationTokenClass = authenticationTokenClass; 243 } 244 245 /** 246 * Sets an explicit {@link Cache} instance to use for authentication caching. If not set and authentication 247 * caching is {@link #isAuthenticationCachingEnabled() enabled}, any available 248 * {@link #getCacheManager() cacheManager} will be used to acquire the cache instance if available. 249 *
 250 * WARNING: Only set this property if safe caching conditions apply, as documented at the top 251 * of this page in the class-level JavaDoc. 252 * 253 * @param authenticationCache an explicit {@link Cache} instance to use for authentication caching or 254 * {@code null} if the cache should possibly be obtained another way. 255 * @see #isAuthenticationCachingEnabled() 256 * @since 1.2 257 */ 258 public void setAuthenticationCache(Cache<Object, AuthenticationInfo> authenticationCache) { 259 this.authenticationCache = authenticationCache; 260 } 261 262 /** 263 * Returns a {@link Cache} instance to use for authentication caching, or {@code null} if no cache has been 264 * set. 265 * 266 * @return a {@link Cache} instance to use for authentication caching, or {@code null} if no cache has been 267 * set. 268 * @see #setAuthenticationCache(org.apache.shiro.cache.Cache) 269 * @see #isAuthenticationCachingEnabled() 270 * @since 1.2 271 */ 272 public Cache<Object, AuthenticationInfo> getAuthenticationCache() { 273 return this.authenticationCache; 274 } 275 276 /** 277 * Returns the name of a {@link Cache} to lookup from any available {@link #getCacheManager() cacheManager} if 278 * a cache is not explicitly configured via {@link #setAuthenticationCache(org.apache.shiro.cache.Cache)}. 279 *
 280 * This name will only be used to look up a cache if authentication caching is 281 * {@link #isAuthenticationCachingEnabled() enabled}. 282 *
 283 * WARNING: Only set this property if safe caching conditions apply, as documented at the top 284 * of this page in the class-level JavaDoc. 285 * 286 * @return the name of a {@link Cache} to lookup from any available {@link #getCacheManager() cacheManager} if 287 * a cache is not explicitly configured via {@link #setAuthenticationCache(org.apache.shiro.cache.Cache)}. 288 * @see #isAuthenticationCachingEnabled() 289 * @since 1.2 290 */ 291 public String getAuthenticationCacheName() { 292 return this.authenticationCacheName; 293 } 294 295 /** 296 * Sets the name of a {@link Cache} to lookup from any available {@link #getCacheManager() cacheManager} if 297 * a cache is not explicitly configured via {@link #setAuthenticationCache(org.apache.shiro.cache.Cache)}. 298 *
 299 * This name will only be used to look up a cache if authentication caching is 300 * {@link #isAuthenticationCachingEnabled() enabled}. 301 * 302 * @param authenticationCacheName the name of a {@link Cache} to lookup from any available 303 * {@link #getCacheManager() cacheManager} if a cache is not explicitly configured 304 * via {@link #setAuthenticationCache(org.apache.shiro.cache.Cache)}. 305 * @see #isAuthenticationCachingEnabled() 306 * @since 1.2 307 */ 308 public void setAuthenticationCacheName(String authenticationCacheName) { 309 this.authenticationCacheName = authenticationCacheName; 310 } 311 312 /** 313 * Returns {@code true} if authentication caching should be utilized if a {@link CacheManager} has been 314 * {@link #setCacheManager(org.apache.shiro.cache.CacheManager) configured}, {@code false} otherwise. 315 *
 316 * The default value is {@code true}. 317 * 318 * @return {@code true} if authentication caching should be utilized, {@code false} otherwise. 319 */ 320 public boolean isAuthenticationCachingEnabled() { 321 return this.authenticationCachingEnabled && isCachingEnabled(); 322 } 323 324 /** 325 * Sets whether or not authentication caching should be utilized if a {@link CacheManager} has been 326 * {@link #setCacheManager(org.apache.shiro.cache.CacheManager) configured}, {@code false} otherwise. 327 *
 328 * The default value is {@code false} to retain backwards compatibility with Shiro 1.1 and earlier. 329 *
 330 * WARNING: Only set this property to {@code true} if safe caching conditions apply, as documented at the top 331 * of this page in the class-level JavaDoc. 332 * 333 * @param authenticationCachingEnabled the value to set 334 */ 335 @SuppressWarnings({"UnusedDeclaration"}) 336 public void setAuthenticationCachingEnabled(boolean authenticationCachingEnabled) { 337 this.authenticationCachingEnabled = authenticationCachingEnabled; 338 if (authenticationCachingEnabled) { 339 setCachingEnabled(true); 340 } 341 } 342 343 public void setName(String name) { 344 super.setName(name); 345 String authcCacheName = this.authenticationCacheName; 346 if (authcCacheName != null && authcCacheName.startsWith(getClass().getName())) { 347 //get rid of the default heuristically-created cache name. Create a more meaningful one 348 //based on the application-unique Realm name: 349 this.authenticationCacheName = name + DEFAULT_AUTHENTICATION_CACHE_SUFFIX; 350 } 351 } 352 353 354 /*-------------------------------------------- 355 | M E T H O D S | 356 ============================================*/ 357 358 /** 359 * Convenience implementation that returns 360 * <tt>getAuthenticationTokenClass().isAssignableFrom( token.getClass() );</tt>. Can be overridden 361 * by subclasses for more complex token checking. 362 *
Most configurations will only need to set a different class via 363 * {@link #setAuthenticationTokenClass}, as opposed to overriding this method. 364 * 365 * @param token the token being submitted for authentication. 366 * @return true if this authentication realm can process the submitted token instance of the class, false otherwise. 367 */ 368 public boolean supports(AuthenticationToken token) { 369 return token != null && getAuthenticationTokenClass().isAssignableFrom(token.getClass()); 370 } 371 372 /** 373 * Initializes this realm and potentially enables an authentication cache, depending on configuration. Based on 374 * the availability of an authentication cache, this class functions as follows: 375 *
 376 *
If the {@link #setAuthenticationCache cache} property has been set, it will be 377 * used to cache the AuthenticationInfo objects returned from {@link #getAuthenticationInfo} 378 * method invocations. 379 * All future calls to {@link #getAuthenticationInfo} will attempt to use this cache first 380 * to alleviate any potentially unnecessary calls to an underlying data store.
 381 *
If the {@link #setAuthenticationCache cache} property has not been set, 382 * the {@link #setCacheManager cacheManager} property will be checked. 383 * If a {@code cacheManager} has been set, it will be used to eagerly acquire an authentication 384 * {@code cache}, and this cache which will be used as specified in #1.
 385 *
If neither the {@link #setAuthenticationCache (org.apache.shiro.cache.Cache) authenticationCache} 386 * or {@link #setCacheManager(org.apache.shiro.cache.CacheManager) cacheManager} 387 * properties are set, caching will not be utilized and authentication look-ups will be delegated to 388 * subclass implementations for each authentication attempt.
 389 *
 390 *
 391 * This method finishes by calling {@link #onInit()} is to allow subclasses to perform any init behavior desired. 392 * 393 * @since 1.2 394 */ 395 public final void init() { 396 //trigger obtaining the authorization cache if possible 397 getAvailableAuthenticationCache(); 398 onInit(); 399 } 400 401 /** 402 * Template method for subclasses to implement any initialization logic. Called from 403 * {@link #init()}. 404 * 405 * @since 1.2 406 */ 407 protected void onInit() { 408 } 409 410 /** 411 * This implementation attempts to acquire an authentication cache if one is not already configured. 412 * 413 * @since 1.2 414 */ 415 protected void afterCacheManagerSet() { 416 //trigger obtaining the authorization cache if possible 417 getAvailableAuthenticationCache(); 418 } 419 420 /** 421 * Returns any available {@link Cache} instance to use for authentication caching. This functions as follows: 422 *
 423 *
If an {@link #setAuthenticationCache(org.apache.shiro.cache.Cache) authenticationCache} has been explicitly 424 * configured (it is not null), it is returned.
 425 *
If there is no {@link #getAuthenticationCache() authenticationCache} configured: 426 *
 427 *
If authentication caching is {@link #isAuthenticationCachingEnabled() enabled}, any available 428 * {@link #getCacheManager() cacheManager} will be consulted to obtain an available authentication cache. 429 *
 430 *
If authentication caching is disabled, this implementation does nothing.
 431 *
 432 *
 433 *
 434 * 435 * @return any available {@link Cache} instance to use for authentication caching. 436 */ 437 private Cache<Object, AuthenticationInfo> getAvailableAuthenticationCache() { 438 Cache<Object, AuthenticationInfo> cache = getAuthenticationCache(); 439 boolean authcCachingEnabled = isAuthenticationCachingEnabled(); 440 if (cache == null && authcCachingEnabled) { 441 cache = getAuthenticationCacheLazy(); 442 } 443 return cache; 444 } 445 446 /** 447 * Checks to see if the authenticationCache class attribute is null, and if so, attempts to acquire one from 448 * any configured {@link #getCacheManager() cacheManager}. If one is acquired, it is set as the class attribute. 449 * The class attribute is then returned. 450 * 451 * @return an available cache instance to be used for authentication caching or {@code null} if one is not available. 452 * @since 1.2 453 */ 454 private Cache<Object, AuthenticationInfo> getAuthenticationCacheLazy() { 455 456 if (this.authenticationCache == null) { 457 458 log.trace("No authenticationCache instance set. Checking for a cacheManager..."); 459 460 CacheManager cacheManager = getCacheManager(); 461 462 if (cacheManager != null) { 463 String cacheName = getAuthenticationCacheName(); 464 log.debug("CacheManager [{}] configured. Building authentication cache '{}'", cacheManager, cacheName); 465 this.authenticationCache = cacheManager.getCache(cacheName); 466 } 467 } 468 469 return this.authenticationCache; 470 } 471 472 /** 473 * Returns any cached AuthenticationInfo corresponding to the specified token or {@code null} if there currently 474 * isn't any cached data. 475 * 476 * @param token the token submitted during the authentication attempt. 477 * @return any cached AuthenticationInfo corresponding to the specified token or {@code null} if there currently 478 * isn't any cached data. 479 * @since 1.2 480 */ 481 private AuthenticationInfo getCachedAuthenticationInfo(AuthenticationToken token) { 482 AuthenticationInfo info = null; 483 484 Cache<Object, AuthenticationInfo> cache = getAvailableAuthenticationCache(); 485 if (cache != null && token != null) { 486 log.trace("Attempting to retrieve the AuthenticationInfo from cache."); 487 Object key = getAuthenticationCacheKey(token); 488 info = cache.get(key); 489 if (info == null) { 490 log.trace("No AuthorizationInfo found in cache for key [{}]", key); 491 } else { 492 log.trace("Found cached AuthorizationInfo for key [{}]", key); 493 } 494 } 495 496 return info; 497 } 498 499 /** 500 * Caches the specified info if authentication caching 501 * {@link #isAuthenticationCachingEnabled(org.apache.shiro.authc.AuthenticationToken, org.apache.shiro.authc.AuthenticationInfo) isEnabled} 502 * for the specific token/info pair and a cache instance is available to be used. 503 * 504 * @param token the authentication token submitted which resulted in a successful authentication attempt. 505 * @param info the AuthenticationInfo to cache as a result of the successful authentication attempt. 506 * @since 1.2 507 */ 508 private void cacheAuthenticationInfoIfPossible(AuthenticationToken token, AuthenticationInfo info) { 509 if (!isAuthenticationCachingEnabled(token, info)) { 510 log.debug("AuthenticationInfo caching is disabled for info [{}]. Submitted token: [{}].", info, token); 511 //return quietly, caching is disabled for this token/info pair: 512 return; 513 } 514 515 Cache<Object, AuthenticationInfo> cache = getAvailableAuthenticationCache(); 516 if (cache != null) { 517 Object key = getAuthenticationCacheKey(token); 518 cache.put(key, info); 519 log.trace("Cached AuthenticationInfo for continued authentication. key=[{}], value=[{}].", key, info); 520 } 521 } 522 523 /** 524 * Returns {@code true} if authentication caching should be utilized based on the specified 525 * {@link AuthenticationToken} and/or {@link AuthenticationInfo}, {@code false} otherwise. 526 *
 527 * The default implementation simply delegates to {@link #isAuthenticationCachingEnabled()}, the general-case 528 * authentication caching setting. Subclasses can override this to turn on or off caching at runtime 529 * based on the specific submitted runtime values. 530 * 531 * @param token the submitted authentication token 532 * @param info the {@code AuthenticationInfo} acquired from data source lookup via 533 * {@link #doGetAuthenticationInfo(org.apache.shiro.authc.AuthenticationToken)} 534 * @return {@code true} if authentication caching should be utilized based on the specified 535 * {@link AuthenticationToken} and/or {@link AuthenticationInfo}, {@code false} otherwise. 536 * @since 1.2 537 */ 538 protected boolean isAuthenticationCachingEnabled(AuthenticationToken token, AuthenticationInfo info) { 539 return isAuthenticationCachingEnabled(); 540 } 541 542 /** 543 * This implementation functions as follows: 544 *
 545 *
It attempts to acquire any cached {@link AuthenticationInfo} corresponding to the specified 546 * {@link AuthenticationToken} argument. If a cached value is found, it will be used for credentials matching, 547 * alleviating the need to perform any lookups with a data source.
 548 *
If there is no cached {@link AuthenticationInfo} found, delegate to the 549 * {@link #doGetAuthenticationInfo(org.apache.shiro.authc.AuthenticationToken)} method to perform the actual 550 * lookup. If authentication caching is enabled and possible, any returned info object will be 551 * {@link #cacheAuthenticationInfoIfPossible(org.apache.shiro.authc.AuthenticationToken, org.apache.shiro.authc.AuthenticationInfo) cached} 552 * to be used in future authentication attempts.
 553 *
If an AuthenticationInfo instance is not found in the cache or by lookup, {@code null} is returned to 554 * indicate an account cannot be found.
 555 *
If an AuthenticationInfo instance is found (either cached or via lookup), ensure the submitted 556 * AuthenticationToken's credentials match the expected {@code AuthenticationInfo}'s credentials using the 557 * {@link #getCredentialsMatcher() credentialsMatcher}. This means that credentials are always verified 558 * for an authentication attempt.
 559 *
 560 * 561 * @param token the submitted account principal and credentials. 562 * @return the AuthenticationInfo corresponding to the given {@code token}, or {@code null} if no 563 * AuthenticationInfo could be found. 564 * @throws AuthenticationException if authentication failed. 565 */ 566 public final AuthenticationInfo getAuthenticationInfo(AuthenticationToken token) throws AuthenticationException { 567 568 AuthenticationInfo info = getCachedAuthenticationInfo(token); 569 if (info == null) { 570 //otherwise not cached, perform the lookup: 571 info = doGetAuthenticationInfo(token); 572 log.debug("Looked up AuthenticationInfo [{}] from doGetAuthenticationInfo", info); 573 if (token != null && info != null) { 574 cacheAuthenticationInfoIfPossible(token, info); 575 } 576 } else { 577 log.debug("Using cached authentication info [{}] to perform credentials matching.", info); 578 } 579 580 if (info != null) { 581 assertCredentialsMatch(token, info); 582 } else { 583 log.debug("No AuthenticationInfo found for submitted AuthenticationToken [{}]. Returning null.", token); 584 } 585 586 return info; 587 } 588 589 /** 590 * Asserts that the submitted {@code AuthenticationToken}'s credentials match the stored account 591 * {@code AuthenticationInfo}'s credentials, and if not, throws an {@link AuthenticationException}. 592 * 593 * @param token the submitted authentication token 594 * @param info the AuthenticationInfo corresponding to the given {@code token} 595 * @throws AuthenticationException if the token's credentials do not match the stored account credentials. 596 */ 597 protected void assertCredentialsMatch(AuthenticationToken token, AuthenticationInfo info) throws AuthenticationException { 598 CredentialsMatcher cm = getCredentialsMatcher(); 599 if (cm != null) { 600 if (!cm.doCredentialsMatch(token, info)) { 601 //not successful - throw an exception to indicate this: 602 String msg = "Submitted credentials for token [" + token + "] did not match the expected credentials."; 603 throw new IncorrectCredentialsException(msg); 604 } 605 } else { 606 throw new AuthenticationException("A CredentialsMatcher must be configured in order to verify " + 607 "credentials during authentication. If you do not wish for credentials to be examined, you " + 608 "can configure an " + AllowAllCredentialsMatcher.class.getName() + " instance."); 609 } 610 } 611 612 /** 613 * Returns the key under which {@link AuthenticationInfo} instances are cached if authentication caching is enabled. 614 * This implementation defaults to returning the token's 615 * {@link org.apache.shiro.authc.AuthenticationToken#getPrincipal() principal}, which is usually a username in 616 * most applications. 617 *
Cache Invalidation on Logout
 618 * NOTE: If you want to be able to invalidate an account's cached {@code AuthenticationInfo} on logout, you 619 * must ensure the {@link #getAuthenticationCacheKey(org.apache.shiro.subject.PrincipalCollection)} method returns 620 * the same value as this method. 621 * 622 * @param token the authentication token for which any successful authentication will be cached. 623 * @return the cache key to use to cache the associated {@link AuthenticationInfo} after a successful authentication. 624 * @since 1.2 625 */ 626 protected Object getAuthenticationCacheKey(AuthenticationToken token) { 627 return token != null ? token.getPrincipal() : null; 628 } 629 630 /** 631 * Returns the key under which {@link AuthenticationInfo} instances are cached if authentication caching is enabled. 632 * This implementation delegates to 633 * {@link #getAvailablePrincipal(org.apache.shiro.subject.PrincipalCollection)}, which returns the primary principal 634 * associated with this particular Realm. 635 *
Cache Invalidation on Logout
 636 * NOTE: If you want to be able to invalidate an account's cached {@code AuthenticationInfo} on logout, you 637 * must ensure that this method returns the same value as the 638 * {@link #getAuthenticationCacheKey(org.apache.shiro.authc.AuthenticationToken)} method! 639 * 640 * @param principals the principals of the account for which to set or remove cached {@code AuthenticationInfo}. 641 * @return the cache key to use when looking up cached {@link AuthenticationInfo} instances. 642 * @since 1.2 643 */ 644 protected Object getAuthenticationCacheKey(PrincipalCollection principals) { 645 return getAvailablePrincipal(principals); 646 } 647 648 /** 649 * This implementation clears out any cached authentication data by calling 650 * {@link #clearCachedAuthenticationInfo(org.apache.shiro.subject.PrincipalCollection)}. 651 * If overriding in a subclass, be sure to call {@code super.doClearCache} to ensure this behavior is maintained. 652 * 653 * @param principals principals the principals of the account for which to clear any cached data. 654 * @since 1.2 655 */ 656 @Override 657 protected void doClearCache(PrincipalCollection principals) { 658 super.doClearCache(principals); 659 clearCachedAuthenticationInfo(principals); 660 } 661 662 private static boolean isEmpty(PrincipalCollection pc) { 663 return pc == null || pc.isEmpty(); 664 } 665 666 /** 667 * Clears out the AuthenticationInfo cache entry for the specified account. 668 *
 669 * This method is provided as a convenience to subclasses so they can invalidate a cache entry when they 670 * change an account's authentication data (e.g. reset password) during runtime. Because an account's 671 * AuthenticationInfo can be cached, there needs to be a way to invalidate the cache for only that account so that 672 * subsequent authentication operations don't used the (old) cached value if account data changes. 673 *
 674 * After this method is called, the next authentication for that same account will result in a call to 675 * {@link #doGetAuthenticationInfo(org.apache.shiro.authc.AuthenticationToken) doGetAuthenticationInfo}, and the 676 * resulting return value will be cached before being returned so it can be reused for later authentications. 677 *
 678 * If you wish to clear out all associated cached data (and not just authentication data), use the 679 * {@link #clearCache(org.apache.shiro.subject.PrincipalCollection)} method instead (which will in turn call this 680 * method by default). 681 * 682 * @param principals the principals of the account for which to clear the cached AuthorizationInfo. 683 * @see #clearCache(org.apache.shiro.subject.PrincipalCollection) 684 * @since 1.2 685 */ 686 protected void clearCachedAuthenticationInfo(PrincipalCollection principals) { 687 if (!isEmpty(principals)) { 688 Cache<Object, AuthenticationInfo> cache = getAvailableAuthenticationCache(); 689 //cache instance will be non-null if caching is enabled: 690 if (cache != null) { 691 Object key = getAuthenticationCacheKey(principals); 692 cache.remove(key); 693 } 694 } 695 } 696 697 /** 698 * Retrieves authentication data from an implementation-specific datasource (RDBMS, LDAP, etc) for the given 699 * authentication token. 700 *
 701 * For most datasources, this means just 'pulling' authentication data for an associated subject/user and nothing 702 * more and letting Shiro do the rest. But in some systems, this method could actually perform EIS specific 703 * log-in logic in addition to just retrieving data - it is up to the Realm implementation. 704 *
 705 * A {@code null} return value means that no account could be associated with the specified token. 706 * 707 * @param token the authentication token containing the user's principal and credentials. 708 * @return an {@link AuthenticationInfo} object containing account data resulting from the 709 * authentication ONLY if the lookup is successful (i.e. account exists and is valid, etc.) 710 * @throws AuthenticationException if there is an error acquiring data or performing 711 * realm-specific authentication logic for the specified <tt>token</tt> 712 */ 713 protected abstract AuthenticationInfo doGetAuthenticationInfo(AuthenticationToken token) throws AuthenticationException; 714 715}


In this assignment we will make a small change to a simple Tsugi grade sending tool to make sure to never send a lower grade (i.e. keep the highest grade).
There are several resources you might find useful:
One you have successfully credited the tables and have the database connection working, go to the Developer option. You only see the Developer option in the Tsugi interface if you set the
$CFG->DEVELOPER = true;in your config.php. If you are challenged for a secret to go into Developer mode - it is usually "secret" unless you have changed it during installation.
Developer mode is a way to quickly test Tsugi tools without using a Learning Management System like Moodle, Canvas or Sakai. Developer mode is like a minature built-in LMS with an instructor and two student accounts pre-configured.
Once you are in Developer mode, you can pick the tool you want to launch using the Tool drop-down menu:
If you play with the application under samples, you will see that it sends any grade between 0.0 and 1.0 inclusive. So grades can go up and down. Tsugi retains the most recently sent grade in the table lti_result. You can verify the grade that was sent by checking this table each time you run sample/grade/index.php. This previous grade is available to the application in the global variable $LINK->grade as you can see in the var_dump() of the Tsugi global objects in the grade code.
If you play with the application code under exercises/grade/index.php you will see that it sends all grades above 0.5 and does not send any grade below 0.5. You can test the code by first trying to send "0.4" as the grade and it will claim that the grade has already been sent. Then try to send "0.7" and it will send the grade. Then try to send "0.6" as the grade and it will send the grade.
This is the flaw/problem/issue with the exercises/grade/index.php. It has hard coded the "old value" to always be "0.5".
The goal of this program is to make it so that the system never sends back a lower grade than a grade previously sent and stored. You will find the previous grade in the $LINK->grade. If the new grade is not higher than the previous grade you will put out a message a message. For example if the following sequence were entered, it should have these results:
0.2 (sent) 0.1 (not sent) 0.6 (sent) 0.7 (sent) 0.6 (not sent)The code in Github is fully functional except it always hard-codes the "previous grade" to 0.5.
Once you have tested your application, you will want to set the grade back to zero. You can enter "0.0" as the grade to reset it back to zero. The application sends the zero. You can also change the grade in the lti_result table and then press "Refresh" on the grade code in your browser to re-load the "old grade" into $RESULT->grade – when in doubt scroll down and see the old grade in the var_dump() output.
For this assignment you will hand in:
The Tsugi lti_result table in PHPMyAdmin:
Provided by:
www.tsugi.org


[dscrdeql] <CowboyCrypto- Founder> Hot gyms are where champions are made
[dscrdeql] <CowboyCrypto- Founder> Air conditioned gyms make ppl dependent on comfort lol
GatewayBOT20-Oct-18 05:16 AM
[dscrdeql] <Jellysmash> it's called Quantum Martial Arts
[dscrdeql] <Jellysmash> they teach the Northstar Ju Jitsu system
[dscrdeql] <Jellysmash> he got his Blue belt... he's been doing it for a year now. so not half way yet to black. He'll have another few years to go
[dscrdeql] <Jellysmash> but he's very light on his feet and quick. Although he's only 11 years old
[dscrdeql] <Jellysmash> Yea I agree about the hot gyms. So many gymns are airconditioned and ppl whine like little bitches if they raise too much of a sweat.
[dscrdeql] <Jellysmash> When I work out it's downstairs from the house so it's outside, it's cold as in winter and hot af in summer.  So I wear full length tracksuit pants and long sleeve tshirt even on hottest days in summer. I sweat a bucket load.
[dscrdeql] <Jellysmash> anyways, good to get home.... make myself some tea..
[dscrdeql] <Jellysmash> I just put a roast pork leg in the oven. fully salted for the crunchiest crackle in the world. it'll take 2.5 hours to cook.
GatewayBOT20-Oct-18 08:40 AM
[dscrdeql] <nille> have a nice day
GatewayBOT20-Oct-18 10:59 AM
[dscrdeql] <AndronicusBass-Founder> I'm making steak dianne with baked potato in the BBQ. One day we have to have an equaliser BBQ and mega feast for community.
[dscrdeql] <Jellysmash> Ha, yes that sounds good
GatewayBOT20-Oct-18 03:33 PM
[dscrdeql] <Linkara6669-Mod> @AndronicusBass Yummmmm! That sounds so good xD
[dscrdeql] <CowboyCrypto- Founder> @AndronicusBass-Founder you know I can cook lol
[dscrdeql] <CowboyCrypto- Founder> May be too stoned to light a grill but the cooking I got
[dscrdeql] <CowboyCrypto- Founder>
GatewayBOT20-Oct-18 05:18 PM
[dscrdeql] <Linkara6669-Mod>
GatewayBOT20-Oct-18 05:58 PM
[dscrdeql] <CowboyCrypto- Founder> lol link true story bro..
[dscrdeql] <CowboyCrypto- Founder> andy had to light it for me
[dscrdeql] <CowboyCrypto- Founder> then we smashed on steak and lobster.
[dscrdeql] <CowboyCrypto- Founder> cheap af too
[dscrdeql] <CowboyCrypto- Founder> we paid like 50 bucks for steak and lobster for 4 people with shells n cheese and all the fixins
GatewayBOT20-Oct-18 08:18 PM
[dscrdeql] <MassimoStyle> hola everyone
GatewayBOT20-Oct-18 08:59 PM
[dscrdeql] <Jellysmash> morning all
[dscrdeql] <Jellysmash>
[dscrdeql] <Jellysmash> nice to have a sunday morning without having to rush around
GatewayBOT20-Oct-18 09:22 PM
[dscrdeql] <Jellysmash> I'd like steak and lobster for 4 people as well. I reckon I could eat most of it myself as well.
[dscrdeql] <Jellysmash> Love steak and lobster so why not have them in the same meal....sounds like a good idea.
[dscrdeql] <Jellysmash> I've seen prawns on top of steak in some places in Australia...I'vce seen it called: Surf and Turf
GatewayBOT20-Oct-18 10:18 PM
[dscrdeql] <CowboyCrypto- Founder> yup
[dscrdeql] <CowboyCrypto- Founder> lol I like to cook
[dscrdeql] <CowboyCrypto- Founder> well we all do pretty much lol
[dscrdeql] <CowboyCrypto- Founder> our early meetings used to consist of food conversation at some point everyday
GatewayBOT20-Oct-18 10:50 PM
[dscrdeql] <Jellysmash> food is always a good starting point for a meeting....then drinnks
GatewayBOT20-Oct-18 11:02 PM
[dscrdeql] <CowboyCrypto- Founder> lol I started with drinks. I got off the plane loaded
[dscrdeql] <CowboyCrypto- Founder> apparently I was so much fun that I got bumped up to business on my way back because I was fun to talk to.
GatewayBOT20-Oct-18 11:15 PM
[dscrdeql] <Jellysmash> haha...good way to get an upgrade....just drink a heap and talk shit
[dscrdeql] <Jellysmash> people love that
GatewayBOT21-Oct-18 01:37 AM
[dscrdeql] <AndronicusBass-Founder> Hands down the funniest dude I know
[dscrdeql] <AndronicusBass-Founder> I was awake about 60 hours after my flights and passed out sitting up in the car to the way to our accommodation
Last year January 2017 if u invested $1000 in #bitcoin you would have made $15,000
And if you invested at the same $1000 in $ltc you would have made $50,000
My question is:
Which project/s will make you more profits?
GatewayBOT21-Oct-18 10:26 PM
[dscrdeql] <Jellysmash> Just replied, it's equaliser of course
GatewayBOT21-Oct-18 11:04 PM
[dscrdeql] <CowboyCrypto- Founder> whats up everyone
[dscrdeql] <CowboyCrypto- Founder> hope all of you have had a good weekend.
[dscrdeql] <CowboyCrypto- Founder> Just a fast update here from me: Im currently working on getting more funds raised us so that we can do a few things to improve our situation. Everything I've done the past few weeks has worked well and I will continue to grind everyday to make this work out.
[dscrdeql] <Jellysmash> L @CowboyCrypto hey there
[dscrdeql] <CowboyCrypto- Founder> hey there
[dscrdeql] <Jellysmash> Ok, sounds good
[dscrdeql] <Jellysmash>
[dscrdeql] <Jellysmash> I'm on my third...at work now
[dscrdeql] <CowboyCrypto- Founder> lol Im grinding away trying to put us in a better position.
[dscrdeql] <Jellysmash> Doing AML training
[dscrdeql] <CowboyCrypto- Founder> hoping I can accomplish a few things this week and get rocking.
[dscrdeql] <Jellysmash> @CowboyCrypto I'm glad you're on the case
[dscrdeql] <Jellysmash> I think it'll help when building is being done. Ppl will see the results, and see progress..
[dscrdeql] <Jellysmash> But like most building processes, they start off slow as there's a lot of groundwork to do before construction starts
[dscrdeql] <CowboyCrypto- Founder> there's a ton of work for sure
GatewayBOT21-Oct-18 11:28 PM
[dscrdeql] <Jellysmash> The thing is that you almost need one person concentrating on raising funds. Another concentrating purely on PR and marketing. Another on building and materials and design. And a 4th on the blockchain and changes required.


Find the Cru staff that authorized this scholarship by searching below and choosing his or her name from the results list.
{{currentPayment.scholarship.staffEmail}}
An email will be sent to {{currentPayment.scholarship.staffApprovalName}} to confirm the scholarship.


HIGH COURT OF ORISSA: CUTTACK W.P.(C) No.11607 of 2009 In the matter of an application under Articles 226 and 227 of the Constitution of India. --------
Sri Amarendra Mallik, Son of Sunakara Mallik, Plot No.850, Nilakantheswar Marg, PO: Baramunda, PS: Khandagiri, Bhubaneswar, Dist: Khurda ... Petitioner
-Versus-
State of Orissa & Others ... Opp.Parties For Petitioner : M/s. Patitapaban Panda, B.B. Mohanty & R.N. Rout. For Opp. Parties : Advocate General & Government Advocate (for opp. party nos. 2 & 3) M/s. S.K. Nayak-I, A.C. Baral, D. Nayak & B.R.Sarangi. (for opp. party no.1) ---------- P R E S E N T:
THE HONOURABLE THE CHIEF JUSTICE SHRI.V.GOPALA GOWDA AND THE HONOURABLE SHRI JUSTICE B.N.MAHAPATRA Date of hearing : 02.11.2010 : Date of Judgment : 15.12.2010 B.N. MAHAPATRA, J. This writ petition has been filed with a prayer for quashing order dated 18.07.2009 (Annexure-5) passed by opposite party No.1- Commissioner-cum-Secretary to Government, Department of Steel & Mines, 2 Government of Orissa and letter dated 18.07.2009 (Annexure-6) issued by the Under Secretary to Government, Department of Steel & Mines, Government of Orissa. The opposite party No.1 under Annexure-5 rejected the representation of the petitioner for removal of 473.565 MTs of quartz from Stack Nos.3/07 to 6/07 of Burubuda Jungle Mines. Under Annexure- 6, the Under Secretary to Government of Orissa, Steel & Mines Department vide his letter dated 18.07.2009 requested the Director of Mines, Orissa, Bhubaneswar to issue a direction to the Mining Officer, Bolangir to recover cost of the minerals removed unauthorizedly by the petitioner- Amarendra Mallik from the mining area in village Burubuda Jungle of Subarnapur district and to collect the royalty due thereon as per the provisions of laws and also to initiate the legal action against Sri Mallik as per the provisions of law.
2. Bereft of unnecessary details, the facts and circumstances giving rise to the present writ petition are that the petitioner, a mining lessee in respect of two number of mining leases, one over 37.433 hects in the village Burubuda Jungle and another over 18.000 hects. in village Chandili for quartz, gemstone and mica. The aforesaid mining leases were granted and executed in favour of the petitioner on 28.02.2006. After execution of the lease deeds, the petitioner started quarrying operation in respect of the said two leases and made production of quartz minerals from both the leases and dispatched the minerals on the basis of transit permit 3 issued by opposite parties from time to time on the application made by the petitioner to that effect. On 21.06.2007 the petitioner applied for transit permit for removal of 508.500 MTs quartz minerals extracted from the lease hold mines and the opposite party No.3-Mining Officer, Bolangir Circle, Bolangir issued transit pass (Annexure-3) allowing the petitioner to remove 508.500 MTs from the stack of the petitioner's mines. The said permit was issued on 21.06.2007 and remained valid for the period 21.06.2007 to 20.07.2007. According to the petitioner, pursuant to the said transit permit issued under Annexure-3, he could be able to remove 34.935 MTs minerals and the balance he could not be able to remove as he fell ill due to brain malaria. Apart from the above, the road was completely damaged due to rainy season and remained closed. The petitioner again on 27.08.2008 applied to opposite party No.3 for extension of time for removal of balance 473.565 MTs of quartz. In the meantime, the Collector, Khurda reported to the Mining Officer, Bolangir that the petitioner furnished a forged solvency certificate at the time of granting the mining lease. The Mining Officer reported the matter to the police and the petitioner was behind the bar for a period of one month. Since no transit permit was issued by opposite party No.3, the petitioner filed a writ petition before this Court bearing W.P.(C) No.2142 of 2009 praying for issuance of permit. The said writ petition was disposed of on 06.04.2009 with a direction to opposite party No.1 to take a decision on the representation of the petitioner with regard to issuance of 4 transit permit within a period of one month from the date of communication of the order. Since the representation of the petitioner was not disposed of within the time stipulated by this Court, the petitioner filed a contempt petition bearing CONTC No.797 of 2009. After filing of the contempt petition, opposite party No.1 rejected the application for extension of transit permit of the petitioner vide order dated 18.07.2009 (Annexure-5). Thereafter, Under Secretary to Government issued letter dated 18.07.2009 (Annexure-6) to opposite party No.2-Director of Mines, Orissa, Bhubaneswar to initiate a legal proceeding against the petitioner. Hence, this writ petition.
3. Mr. Patitapaban Panda, learned counsel appearing for the petitioner vehemently argued that the orders passed under Annexures-5 and 6 are arbitrary, illegal, mala fide and contrary to the provisions of law and the materials available on record and as such the same are liable to be quashed. The reasons mentioned in the rejection order are non est in the eye of law, biased, far from truth, self created, mala fide and inconsistent with their own orders passed from time to time. Mr. Pravat Kumar Ojha, the Mining Officer has wrongly reported regarding non-availability of physical possession of the stock in the leased out area. Since, the petitioner has made an application for extension of the period of permit after lapse of the validity period on 21.07.2007, the opposite party No.1 is wrong to reject the petitioner's application for extension of the permit on the ground that 5 the same has not been made in specific Form-'J' accompanied by the required fee as has been prescribed under Sub-Rule (2) of Rule 10 of the Orissa Mineral (Prevention of Theft, Smuggling & Illegal Mining and Regulation of Possession, Storage, Trading and Transportation) Rules, 2007 (for short, "Rules, 2007"), which came into force w.e.f. 20.09.2007. Since the petitioner has only utilized 14 number of Forms out of 50 from the book bearing Book No.19, the opposite parties are not correct to say that the petitioner has not submitted the returns of used transit passes. The petitioner has filed monthly returns in Form A for Burubuda Jungle Mines till 31.12.2007. The petitioner has also filed monthly returns in Form B showing all the details. The allegation that the application made for removal of stock from stack Nos.3/07 to 6/07 was not found physically available at the petitioner's mines is false and fabricated. Since there was no need to submit any solvency certificate along with the application for grant of mining lease, there was no occasion for the Collector, Sonepur or the Mining Officer to find out whether any false solvency certificate has been submitted by the petitioner or not. It is the Director of Mines, who can say whether the petitioner has submitted any solvency certificate or not. Opposite party No.3 has no business to initiate a police case against the petitioner as he was not an authorized officer to do so. All alleged forgery and irregularities were committed by his childhood friend, Manas Ranjan Sahoo to whom in good faith he entrusted the work of supervision of 6 mining activities because of his illness. Earlier the opposite parties have granted several extension of transit permits after lapse of their validity period, but presently the said extension is not granted only to harass the petitioner. Concluding his argument, Mr. Panda urged that Annexures-5 and 6 should be quashed.
4. Learned Advocate General appearing for opposite parties submits that the impugned orders passed under Annexures 5 and 6 are valid and legal. In the present case disputed questions of fact are involved and therefore, this Court by exercising jurisdiction under Articles 226 and 227 of the Constitution cannot effectually adjudicate the disputed questions of fact. The petitioner has not approached this Court with clean hands. In the meantime, the lease granted has been cancelled. After cancellation of the lease no permit can be granted for removal of any stack. Moreover, the petitioner has raised minerals from outside the lease hold area. Therefore, the writ petition is liable to be dismissed. It is submitted that though it is averred by the petitioner that the forgery and irregularities as alleged against the petitioner by the opposite parties were committed by one Sri Manas Ranjan Sahoo, who was the childhood friend of the petitioner, the petitioner has not made him a party in the writ petition. Similarly, though the petitioner has raised allegation against the Collector, Khurda, he has also not been made him a party in the writ petition. Hence, the writ petition is not maintainable due to non-joinder of necessary 7 parties. On 17.01.2008 the Sub-Collector, Bhubaneswar intimated the Collector, Khurda that the solvency certificates bearing Nos.57/2003 and 12/2006 were forged documents. On 25.01.2008, the Collector, Khurda intimated to the Collector, Bolangir regarding the above facts. The Collector, Bolangir vide his letter dated 01.02.2008 intimated the same to the opposite party No.3-Mining Officer. On 02.02.2008, the opposite party No.3 intimated the matter to the Director of Mines, Orissa, Bhubaneswar. On 04.02.2008 the Collector, Subarnapur intimated the facts to the opposite party No.2-Director of Mines, Orissa, Bhubaneswar as well as the opposite party No.1-Commissioner-cum-Secretary to Government in Steel and Mines Department for taking appropriate action. On 20.05.2008 the Director of Mines intimated the Steel & Mines Department for cancellation of two granted MLs bearing Nos.29/S and 30/S in view of submission of forged solvency certificates. The application for extension of time for removal of balance quantity of 473.565 MT of quartz from Burubuda Jungle ML area was not in the prescribed Form-'J'. The said application was submitted without specific dimension of the stack Nos. 3/07 to 6/07 and was also not accompanied with the prescribed fee as provided under Sub-Rule (2) of Rule 10 of Rules, 2007. The opposite party No.3 filed an F.I.R. against the petitioner on 08.03.2008 in the Town Police Station, Bolangir. Thereafter, the petitioner was arrested on 12.07.2008 in Bolangir Town P.S. Case No.178/2008 and released on bail by order of the Sessions 8 Judge, Bolangir on 22.07.2008. The petitioner has not yet submitted returns of used transit passes in Form-M showing the details of dispatched quantity of quartz from the above stacks out of 508.500 MTs of Quartz permitted earlier for removal. Despite request dated 03.03.2008 the petitioner has not submitted the monthly returns in the prescribed Forms A & B in respect of the aforesaid mines after May, 2007. During the inspection of Burubuda Jungle Quartz Mines of the petitioner by the Joint Director of Mines, Orissa on 15.01.2008, it was noticed that the petitioner had unauthorizedly removed 10,900 Cubic Meters of morrum from his leasehold area (Burubuda Jungle) and used the same in construction of road out side the leasehold area without obtaining permission from opposite party No.3, who is the competent authority. The petitioner was asked to pay royalty amounting to Rs.1,09,000/- (Rupees One Lakh nine Thousand) and to pay Rs.71,967/- (Rupees Seventy One Thousand Nine Hundred and Sixty Seven) only towards outstanding arrears of dues of Dead Rent, Surface Rent and interest on delayed payment thereof. As the petitioner did not respond to make payment of the outstanding dues as mentioned above, a certificate case was initiated against him in the Court of the Certificate Officer-cum-Sub-Collector, Bolangir vide Certificate Case No.5/2008 under the provisions of Orissa Public Demand Recovery Act, 1962. The State Pollution Control Board, Orissa, Bhubaneswar vide its letter No.1335 dated 18.01.2008 issued instruction to the petitioner for 9 closure of the above two mines under Section 31(A) of Air (Prevention and Control of Pollution) Act, 1981 and Section 33(A) of Water (Prevention and Control of Pollution) Act, 1974 in view of the fact that the petitioner had not taken any steps in compliance to obtain the consent of the State Pollution Control Board under the aforesaid Act for mining operations.
Sri R.K. Das, Senior Inspector of Mines, Bolangir during his visit on 25.06.2009 to the said mines noticed and reported that the applied stacks Nos. 3/07 to 6/07 could not be found in the mines area of the petitioner. It was further detected that neither the boundary pillars all along the boundary lines of the leasehold area nor surface right area therein were found existing in the leasehold area. During his visit to the mines, neither the petitioner nor his representative was found available at the mines site except only one watchman, who stated that all their staff have left the mines since long and all the reports, returns, records etc. pertaining to mining activities are kept with the petitioner at Bhubaneswar. Therefore, the Senior Inspector of Mines could not verify the area from which the mineral was removed. He also could not know the balance stock out of the previously permitted quantity and so also the total stock at mines site. Therefore, he could not recommend for extension of time of the permit to lift the balance left out quartz permitted earlier, as required under the provisions of sub-rules (5) & (6) of Rule 10 of the Rules, 2007. 10 Prior to the application dated 27.08.2008 for issue of transit permit, proceedings have been initiated for fraudulent action of the petitioner.
The Vigilance Cell, Orissa, Bhubaneswar has instituted a case vide Case No.8/2008 for submission of forged solvency certificate by the petitioner during grant of M.L. No.30/S over 37.433 hects in village Burubuda Jungle and M.L. No.29/S over 18.000 hects in village Chandli of Subarnapur district for quartz, mica and gemstone.
The petitioner has defaulted in payment of dead rent and surface rent in respect of both the leases. Since the petitioner could manage to acquire/obtain the grant of these mining leases which is contrary to the provisions of the Act, 1957 and the Rules, 1960, the entire mining operation including production and despatch of minerals carried out by the petitioner is in contravention of the provisions of Section 4(1) and 4(1A) of the Act, 1957. Under Section 21(5) of the Act, 1957, the price of mineral unauthorizedly and unlawfully removed from a void and non- existent leasehold area in contravention of Section 4(1) of the Act, 1957 is to be recovered from the person concerned along with rent, royalty or tax, as the case may be. The reasons for rejection of order for issuance of transit permit by opposite party No.1 are based on facts and provisions of MM(DR) Act, 1957, MC Rules, 1960 and the Rules, 2007. The petitioner applied for extension of the originally granted permit to him for removal of balance quantity of the mineral on 27.08.2008, when the Rules, 2007 was already 11 in force w.e.f. 16.07.2007. It is submitted that as per the provisions of Rule 10(11) of the Rules, 2007, the transit permit was to be issued by the competent authority after verification of the quantity of mineral available in the stack and other information. Since the petitioner has not submitted any returns in the prescribed form, the availability of balance mineral could not be checked by opposite party No.3. Since the petitioner did not submit the said monthly returns beyond May, 2007, he was instructed by opposite party No.3, vide letter No.772 dated 03.03.2008 to make good of the same.
5. The petitioner in the present writ petition challenges the order dated 18.07.2009 (Annexure-5) rejecting his request for extension of transit permit to remove the minerals extracted from the leasehold area granted in his favour. He has also challenged the order dated 18.07.2009 (Annexure-6) issued by Deputy Secretary to Government to the Director of Mines requesting him to recover the cost of minerals removed unauthorizedly as per the provisions of law and to initiate legal proceedings against him. Petitioner's request for grant of transit permit for removal of minerals was rejected by opposite party No.1 on the ground that the petitioner has transported the quartz mineral unauthorizedly and he has violated the covenants of the lease deed. While rejecting the petitioner's prayer the opposite party No.1 has taken into consideration the following aspects:
(a) The petitioner has not submitted application for issuance of permit for removal of the mineral from mines in specific form i.e. Form-'J'.12
(b) The application was not accompanied by the required fees as has been prescribed under Sub-rule (2) of Rule 10 of Orissa Mineral (Prevention of Theft, Smuggling & Illegal Mining and Regulation of Possession, Storage, Trading and Transportation) Rules, 2007.
(c) The petitioner has not submitted the returns of used TP in Form No.M showing details of dispatched quantity of quartz from the stacks i.e. stack Nos.3/07 to 6/07.
(d) Despite request by M.O., Bolangir, vide letter No.7729, dt.
03.03.08, the petitioner has not submitted the monthly returns in Form Nos.A & B for Burubuda Jungle Mines since May, 2007.
(e) The applied stacks for removal i.e. stack Nos.3/07 to 6/07 are not found physically available at the petitioner's mines as revealed by the visit of Shri R.K. Das, SIM to the Mines on 25.06.2009. This field visit also reveals that neither the boundary pillars all along the boundary lines nor surface right pillars of the granted surface right area were in existence.
(f) The Director of Mines vide his letter No.7767/DM dated 30.06.2009 reported that as per the communication of Collector, Sonepur, the petitioner has submitted false solvency certificate for grant of two mining leases including the mines at Burubuda Jungle from which the petitioner seeks to remove 473.565 mts of quartz.
6. The reason/basis given by opposite party No.1 for rejecting the petitioner's request for extension of time of the transit permit to remove the minerals as applied for and the reply of the petitioner to the same involve purely disputed questions of fact. Such factual questions of fact cannot be 13 adjudicated by this Court in exercise of its writ jurisdiction under Articles 226 and 227 of the Constitution. Apart from the above, we find that action has been taken against the petitioner by the State Pollution Control Board, Orissa, Bhubaneswar under Section 31(A) of the Air (Prevention and Control of Pollution) Act, 1981 and Section 33(A) of the Water (Prevention and Control of Pollution) Act, 1974, suggesting closure of its mines. Proceedings for realization of royalty for unauthorized removal of minor minerals was also initiated. Criminal cases have been instituted for submitting forged solvency certificate to obtain the mining lease. Vigilance Case No.8/2008 has also been instituted by the State Vigilance Cell, Orissa, Bhubaneswar. Criminal case in G.R. Case No.386/2008 arising out of Bolangir Town P.S. Case No.178/2008 has also been instituted against the petitioner by the Police in the Court of S.D.J.M., Bloangir. Therefore, this is not a fit case for interference by this Court. However, we are expressing no opinion on the merit of the above noted cases.
7. In the result, the writ petition is dismissed.
No order as to costs.
...........................
B.N.Mahapatra, J.
V.Gopala Gowda, C. J. I agree. ........................... Chief Justice Orissa High Court, Cuttack Dated 15 December, 2010/sss/skj/ssd


{{title}}
Inspiration for revealing content by morphing the action element. Examples:
Login/Signup
Terms
Info Overlay
Subscribe
Share
Video Player
Sidebar Settings
Rounded
Checkout
$40.70
Item
QTY
Price
Imitations
Mark Lanegan
1
$12.90
Out Of Exile
Audioslave
1
$15.90
Cure For Pain
Morphine
1
$11.90
Close


Encryption Keys
AES encryption uses a single key as a part of the
encryption process. The key can be 128 bits (16 bytes),
192 bits (24 bytes), or 256 bits (32 bytes) in length.
With AES both the encryption and the
decryption are performed using the same key. This is
called a symmetric encryption algorithm. An encryption key
is simply a binary string of data used
in the encryption process. Because the same encryption
key is used to encrypt and decrypt data, it is important
to keep the encryption key a secret and to use keys that
are hard to guess. Some keys are generated by software
used for this specific task. Another method is to derive a
key from a pass phrase. Good encryption systems never
use a pass phrase alone as an encryption key.


| | |
- enum.IntEnum(builtins.int, enum.Enum)
-
- Destination
- Input
class Destination(enum.IntEnum) |
| |
Enumeration of the different destinations the car can have. |
| |
- Method resolution order:
- Destination
- enum.IntEnum
- builtins.int
- enum.Enum
- builtins.object
Data and other attributes defined here:
- APPLE = <Destination.APPLE: 3>
- END = <Destination.END: 4>
- SCIENCE = <Destination.SCIENCE: 2>
- STARBUCKS = <Destination.STARBUCKS: 1>
- STOP = <Destination.STOP: 0>
Data descriptors inherited from enum.Enum:
- name
- The name of the Enum member.
- value
- The value of the Enum member.
Data descriptors inherited from enum.EnumMeta:
- __members__
- Returns a mapping of member name->value.
This mapping lists all enum members, including aliases. Note that this
is a read-only view of the internal mapping.
|
class Input(enum.IntEnum) |
| |
Enumeration of the different inputs the sensor reads |
| |
- Method resolution order:
- Input
- enum.IntEnum
- builtins.int
- enum.Enum
- builtins.object
Data and other attributes defined here:
- INTERSECTION = <Input.INTERSECTION: 3>
- LEFT = <Input.LEFT: 1>
- MIDDLE = <Input.MIDDLE: 2>
- NO_SENSOR = <Input.NO_SENSOR: 4>
- RIGHT = <Input.RIGHT: 0>
Data descriptors inherited from enum.Enum:
- name
- The name of the Enum member.
- value
- The value of the Enum member.
Data descriptors inherited from enum.EnumMeta:
- __members__
- Returns a mapping of member name->value.
This mapping lists all enum members, including aliases. Note that this
is a read-only view of the internal mapping.
| |


1.5km | 6pm - 12pm
italian, donuts, ice-creams, shakes
1.5km | 6pm - 12pm
italian, donuts, ice-creams, shakes
1.5km | 6pm - 12pm
Burgers, Fried Chicken, ice-creams, shakes
1.5km | 6pm - 12pm
Pizza, Pasta, Salads, shakes
1.5km | 6pm - 12pm
Burgers, steak, shakes, Cakes


...or to view a list of the most recent drug, medical device, or food recalls select one of the links below.


Profile
Check Attendance
Add course
Add student
Class look up
Course Manage
Support
Term & Service
Sign Out
ADD DATA HERE (SUPPORT)