HOW TO
Recover Tunes From Your iPod
Someday the hard drive on your computer will crash, stranding thousands of songs on your iPod. Here's how to get them back onto your PC or Mac.
1) Reinstall iTunes. Launch the app and sign in to your itunes music Store account. Don't plug in your iPod yet.
2) Install and launch a free trial of PodUtil from KennettNet software (www.kennettnet.co.uk). The app will sit there idling, displaying a Waiting-for-iPods message.
3) Plug in your iPod. PodUtil will detect it and display a window that shows the files and playlists on your ipod. Click the "Choose" button at the bottom of Pod-Util and select your iTunes music folder. Next, click the "Copy Settings" button. In the dialog box that appears, select both "Add Tracks to iTunes" and "Rebuild Playlists." Click "OK."
4) Read the Don't-Steal-Music warning in the lower right corner of PodUtil. Think carefully. Click the "Copy" button below it.
 Reauthorize your iTunes music store tracks. Done!
6) Happy? Hit the "Register now" button and send the site £10 (about 18 bucks).
➜Match Beats //
When mixing two songs, you need to match their speeds. Do this by concentrating on the snare drum: its crisp, distinctive rhythm will help you recognize which song needs to speed up and which needs to slow down. Adjust the tempo of one of the songs until the two are in sync.
Make a Playlist
The iTunes playlist function makes everyone a DJ. But crafting the perfect soundtrack takes more finesse than just piling a bunch of songs together. DJ Qbert (shown), two-time winner of the DMC world DJ championships, drops some science on the art of the mix.
- 1 Even Paris Hilton needs a few drinks before she's ready for a dance-off, so your playlist should start off mellow and slowly board the soul train. Figure two hours before you raise the roof.
- 2 Soundtracks, like conversations, can be jarring without transitions. Don't attempt to pair Air with Quiet Riot unless you're a professional DJ. Look for songs that complement each other.
- 3 Dead space between tracks is for amateurs. Since the iPod can't crossfade, use ProTools to merge tunes into a single song file. If you can match beats, even better.
- 4 Be sure to include a few hits. Everyone loves listening to hip new music, but every now and then you gotta get the party moving with an old classic - even if the party's just you.
Score tickets to the big show
- 1) Join the fan club. Club memberships often unlock online presale deals.
- 2) Coordinate your attack. Team up with friends so one person hops on Ticketmaster's Web site, one works the phones, and one stands outside an old-fashioned ticket window.
- 3) Find the right outlet. If you're the one schlepping to an actual ticket counter, pick an obscure location. That music store in the exurban mall is often overlooked. But visit ahead of time to make sure someone there knows how to work the machine.
- 4) Do a trial run. Preload your user info on Ticketmaster.com to speed through your purchase on the big day.


PIRCS Meeting
12 January 1999, 7:30 pm
Dallas, Texas
The next PIRCS meeting will be held at the 1999 Annual Meeting of the American Meteorological Society in Dallas, Texas on Tuesday, January 12. We will meet in the Batik B conference room at the Wyndam Anatole hotel (the AMS conference HQ hotel). A buffet dinner will be available at 7:30 pm, with formal business starting at 8 pm. The start of the meeting has been pushed back to avoid overlap with a GCIP meeting called by Rick Lawford.
Attendance is limited to PIRCS participants and invited guests. If you have questions or would like to suggest agenda items for the meeting, please email the project coordinators at<EMAIL_ADDRESS>Agenda
1. Dinner, compliments of the Electric Power Research Institute
2. Welcome and introductions
3. PIRCS involvement at past and future meetings:
a) WGNE
b) CLIVAR
c) MERCURE
d) IUGG special session
e) Trieste symposium on regional climate modeling
f) NCAR CSM simulation of 20th and 21st centuries4. Overview of results of PIRCS Experiment 1b: Summer 1993
a) Total precipitation for participating models compared to Higgins observed data
i) time history
ii) episodes
iii) maps of cumulative precipb) Low-level jets
c) Possible additional diagnostics
i) Onset of the North American monsoon
ii) P-E
iii) Wet/dry periods?
iv) Max/min temps?
5. Comparison with PIRCS Experiment 1a: Summer 1988
6. Publication of results
a) JGR article under review
b) Publication of 1993 results
c) Additional publications
d) Conference presentations7. Stretched grids/variable resolution grids
8. Future directions of PIRCS
a) 1988 & 1993 output analysis for California Energy Commission
b) Additional experimentation under Experiments 1a and 1bi) domain-size sensitivity
ii) initial soil moisturec) Further experiments
9. Other business


|
FlashCards
|
Functions | |
| def | get_scraping (level) |
| Acquisition of data on the word of the current level. More... | |
| def | get_file_path (level) |
| Acquire the file path. More... | |
| def | get_columns (file_path, level) |
| Characterization of data columns for the current level. More... | |
| def | get_scraping2 (level, columns) |
| Acquisition of data on the word of the current level and known columns. More... | |
| def | get_data (level, columns) |
| Acquisition of data relating to a word. More... | |
| def | get_sync (level) |
| Synchronization of colums for data acquisition. More... | |
| def | get_soup (url, header) |
| def | get_pronunciation_path (word) |
| Acquiring the path of the pronunciation file. More... | |
| def | filter_cyrillic (word) |
| Cyrillic characters for acceptable characters. More... | |
| def | easy (request, number, current_box) |
| Rule for the choice of low difficulty. More... | |
| def | ok (request, number, current_box) |
| Rule for the choice of medium difficulty. More... | |
| def | hard (request, number, current_box) |
| Rule for the choice of medium difficulty. More... | |
Variables | |
| int | words_step = 50 |
| Amount of words per page in the database. More... | |
| def russian.words.easy | ( | request, | |
| number, | |||
| current_box | |||
| ) |
Rule for the choice of low difficulty.
It demands user login
| request | Standard Django request |
| number | Current user level |
| current_box | Current user context |
| def russian.words.filter_cyrillic | ( | word | ) |
Cyrillic characters for acceptable characters.
| word | Word under analysis |
| def russian.words.get_columns | ( | file_path, | |
| level | |||
| ) |
Characterization of data columns for the current level.
| file_path | The source file path |
| level | Current user level |
| def russian.words.get_data | ( | level, | |
| columns | |||
| ) |
Acquisition of data relating to a word.
| level | Current user level |
| columns | Matching columns |
| def russian.words.get_file_path | ( | level | ) |
Acquire the file path.
| level | Current user level |
| def russian.words.get_pronunciation_path | ( | word | ) |
Acquiring the path of the pronunciation file.
| word | Word under analysis |
| def russian.words.get_scraping | ( | level | ) |
Acquisition of data on the word of the current level.
| level | Current user level |
| def russian.words.get_scraping2 | ( | level, | |
| columns | |||
| ) |
Acquisition of data on the word of the current level and known columns.
| level | Current user level |
| columns | Matching columns |
| def russian.words.get_soup | ( | url, | |
| header | |||
| ) |
| def russian.words.get_sync | ( | level | ) |
Synchronization of colums for data acquisition.
| level | Current user level |
| def russian.words.hard | ( | request, | |
| number, | |||
| current_box | |||
| ) |
Rule for the choice of medium difficulty.
It demands user login
| request | Standard Django request |
| number | Current user level |
| current_box | Current user context |
| def russian.words.ok | ( | request, | |
| number, | |||
| current_box | |||
| ) |
Rule for the choice of medium difficulty.
It demands user login
| request | Standard Django request |
| number | Current user level |
| current_box | Current user context |
| russian.words.words_step = 50 |
Amount of words per page in the database.


Welcome to the unofficial site for the Data Science at UCSB Project Group Organizational Repo.
This website was created to supplement the organizational repo that was created for the project group at Data Science at UCSB. A simple tool used to showcase the GitHub repository and the inertia7 hosted demonstration. We will be rotating a lot of interesting member projects so remember to come back.
If you have any questions feel free to let us know!


Reporting
How to learn more about the activity of your nodes.
Reports and Reporting
Puppet clients can be configured to send reports at the end of every configuration run. These reports include all of the log messages generated during the configuration run and metrics related to what happened on that run.
Logs
The bulk of the report is every log message generated during the transaction. This is a simple way to send almost all client logs to the Puppet server; you can use the log report to send all of these client logs to syslog on the server.
Metrics
The rest of the report contains some basic metrics describing what happened in the transaction. There are three types of metrics in each report, and each type of metric has one or more values:
- Time: Keeps track of how long things took.
- Total: Total time for the configuration run
- File:
- Exec:
- User:
- Group:
- Config Retrieval: How long the configuration took to retrieve
- Service:
- Package:
- Resources: Keeps track of the following stats:
- Total: The total number of resources being managed
- Skipped: How many resources were skipped, because of either tagging or scheduling restrictions
- Scheduled: How many resources met any scheduling restrictions
- Out of Sync: How many resources were out of sync
- Applied: How many resources were attempted to be fixed
- Failed: How many resources were not successfully fixed
- Restarted: How many resources were restarted because their dependencies changed
- Failed Restarts: How many resources could not be restarted
- Changes: The total number of changes in the transaction.
Setting Up Reporting
By default, the agent does not send reports, and the master is only configured to store reports, which just dumps reports as YAML
in the reportdir
.
Make Agent Nodes Send Reports
Set the report
setting in the puppet.conf
file to true in order to turn on reporting on agent nodes.
#
# /etc/puppet/puppet.conf
#
[agent]
report = true
With this setting enabled, the agent will then send the report to the puppet master server at the end of every transaction.
Agents default to sending reports to the same server they get
their configurations from, but you can change that by setting
reportserver
, so if you have load-balanced Puppet
servers you can keep all of your reports consolidated on a single
machine. (This is unimportant if the puppet masters are using report processors like http
or puppetdb
, which just hand off reports to an external system.)
Make Masters Process Reports
By default, the puppet master server stores incoming YAML reports to
disk in the reportdir
. There are other report types available that can process each report as it arrives; you can use Puppet’s built-in report processors, write custom report processor plugins, or write an out-of-band report analyzer task that consumes the stored YAML reports on your own schedule.
Using Built-In Reports
Select the report processors to use with the reports
setting in the puppet master’s puppet.conf
file. This setting should be a comma-separated list of report processors to use; if there is more than one, Puppet will run all of them.
The most useful one is usually the http
processor, which sends reports to an arbitrary URL. Puppet Dashboard uses this, and it’s easy enough to write a web service that consumes reports.
The PuppetDB terminus plugins also include a puppetdb
report processor.
Writing Custom Reports
You can easily write your own report processor in place of any of
the built-in reports. Put the report into the puppet master’s lib/puppet/reports
directory to make it available.
Documentation of the report plugin API is forthcoming; however, you can use the built-in reports as a guide, or use and/or hack one of these simple custom reports:
- Report failed runs to an IRC channel
- Report failed runs and logs to PagerDuty
- Report failed runs to Jabber/XMPP
- Report failed runs to Twitter
- Report failed runs and logs to Campfire
- Report failed runs to Twilio
- Report failed runs to Boxcar
- Report failed runs to HipChat
- Send metrics to a Ganglia server via gmetric
- Report failed runs to Growl
These example reports were posted to the Puppet users group by a Puppet Labs employee, and are linked here for educational purposes.
When writing a report processor, you will need to handle a Puppet::Transaction::Report object provided by Puppet. See Report Formats below.
Using External Report Processors
Alternately, you can use the default store
report and write an external
report processor that reads in and analyzes the saved YAML files. This is ideal for analyzing large amounts of reports on demand, and allows the report processor to be written in any common scripting language.
Report Formats
Puppet creates reports as Puppet::Transaction::Report objects, which have changed format several times over the course of Puppet’s history. We have report format references for the following Puppet versions:
- Puppet 3.x (report format 3)
- Puppet 2.7.x (report formats 3 and 2)
- Puppet 2.6.x (report formats 2 and 1)
- Puppet 0.25.5 (report format 0)
The report format applies to both the Ruby object handed to a report processor and the YAML object written to disk by the default store
processor.


{% extends "global/Page.html" %} {% load staticfiles otree_tags %} {% block title %} TeacherEachYearResults {% endblock %} {% block content %}
There are now {{ num_fish_left_in_fishery }} fish left in fishery.
Current Graph:
{# show graph here #}
Last Year Results:
{# show results here: #}
{# two buttons: next_year, stop & result #} {% endblock %}


{% extends "layout.html" %} {% block content %} Contact us Need help? We're here for you! Send {% endblock content %}
Need help? We're here for you!


essential oil {border-style px;} #ffffff;} activity α-bisabolol Leishmania major used arborea VAEO Vanillosmopsis promastigotes amazonensis showed cell leishmaniasis lipid cells different treated treatment using changes compounds cutaneous products px; results {font-family Costa analysis font-size leishmanicidal parasites potential Figure Lippia Parasitology Research antileishmanial double; evaluated intracellular oils plant plants presence species studies α-bisabolol, μg/mL, (IC Antileishmanial Instituto Phytomedicine Silva action border-color border-width compound cultured cytotoxicity effect effects especially infected membranes mice parasite solid; vitro volume {font-style {font-weight μg/mL -bisabolol Activity Cruz Essential FFG JGM Leishmaniasis Natural Oil Promastigote Rodrigues added agents amastigotes blank bold composition compound, concentration concentrations control courier; disease drugs em; forms hours, increased macrophages membrane number production pt;} shown sodium various volatile


---
layout: page
title: Routine
permalink: /routine/
tags: routine
---
Table of Contents
Full Daily Checklist
The life non negotiables are health (which consists of diet, exercise, sleep) and productivity
Health
- Meal compliance (Morning Shake, Pureed Veggie Protein, Protein Assortment or West Coast Medley, Berry Nut Shake)
- Supplement consumption (full listed below)
- 8 hour feeding window. 7 AM - 3 PM.
- Weight lifting : 1-2 PM
- Cardio 2-2:30 PM
- No devices 1 hour before bed time - physical book
- 8 hours sleep (no alarm). East Coast bedtime 10 PM. West Coast Bed Time 8:30 PM
- Stress Zero - practiced 1x/ day
Productivity
Morning stand up which covers current milestone document (a periodically updated Google Doc)
KPI sheet updated in evening
10 hours of deep work with 30 minute tracking blocks
20 mins or less iPhone screen time
Full compliance goal for 365 days (August 2024)
Diet
Morning Shake:
- 8 oz water
- 1 tablespoon spirulina
- 2 scoops Vital Protein Collagen Peptides
- 2 teaspoons ceylon cinnamon
- 1 scoop whey protein
- 1 tablespoon raw cacao
- 2 tsp matcha powder
- Vitamix/ shaker bottle
Pureed Veggie Protein
- 1 cup lentils
- 2 cups broccoli
- 1 cup cauliflower
- 1 tbsp olive oil
- 1 tsp paprika
- Juice of 1 lemon
- ½ oz raw almonds
- prepared in bulk. Lentils cooked via Instant Pot. Pureed with bulk cooked vegetables via Vitamix.
Protein Assortment - Puerto Rico
- High protein tofu or Quorn (mycoprotein)
- Air fried green banana + fresh root vegetables
- Kimchi
- Seasonal vegetable / fruit additions – ideally in season/ rotating
- Prepared in air fryer
West Coast Medley - Vancouver
- Fresh local vegetables - green beans, tomatoes, etc
- Apple, oranges or plum
- Protein infused yogurt with sliced almond served with fruit
Berry/ Nut Shake
- 1 cup Mixed berries (raspberries, blackberries, blueberries) - frozen
- .75 cups Almonds, walnuts
- 1 cup Kefir or greek yogurt (prefer Kefir)
- Matcha powder, cinnamon, cocoa powder
- Blended in Vitamix
Morning Pill Pack:
- turmeric curcumin 500 mg
- ginger 1.1g
- creatine 5g
- b complex
- garlic 350 mg
- taurine 500 mg
- flaxseed oil 1300 mg
- ashwaganda 400 mg
Evening Pill Pack
- Taurine (500mg)
- flaxseed oil (1.3g)
- creatine (2.5g)
- ginger (1.15g)
Exercise
MONDAY: CHEST/TRICEPS + (at full gym)
- BENCH PRESS (BARBELL): 4 SETS X 6-8 REPS
- INCLINE BENCH PRESS (DUMBELL): 4 SETS X 10-12 REPS
- DECLINE PRESS (DUMBELL): 4 SETS X 10-12 REPS
- CABLE FLYS: 4 SETS X 10-12 REPS
- CLOSE-GRIP BENCH PRESS: 4 SETS X 10-12 REPS
- SKULL CRUSHERS: 4 SETS X 10-12 REPS
- TRICEP PUSHDOWN: 4 SETS X 10-12 REPS
- 3 mile run
TUESDAY: BACK/BICEPS + (at full gym)
- DEADLIFT: 4 SETS X 6-8 REPS
- PULLUPS: 4 SETS X TO FAILURE
- SEATED ROWS 4 SETS X 10-12 REPS
- FACE PULLS: 4 SETS X 10-12 REPS
- STANDING BARBELL CURLS: 4 SETS X 10-12 REPS
- HAMMER CURLS: 4 SETS X 10-12 REPS
- CONCENTRATION CURLS: 4 SETS X 10-12 REPS
- 3 mile run
WEDNESDAY: LEGS (at full gym)
- SQUATS: 4 SETS X 6-8 REPS
- ROMANIAN DEADLIFTS: 4 SETS X 10-12 REPS
- WALKING LUNGES (DUMBBELLS) 4 SETS X 10-12 REPS (EACH LEG)
- CALF RAISES: 4 SETS X 15-20 REPS
- LEG PRESS: 3 SETS X 10-12 REPS
- LEG EXTENSIONS: 3 SETS X 10-12 REPS
- Rowing machine (21 minutes)
THURSDAY: SHOULDERS (at full gym)
- STANDING OVERHEAD PRESS (BARBELL): 4 SETS X 6-8 REPS
- DUMBBELL LATERAL RAISES: 4 SETS X 10-12 REPS
- ARNOLD PRESS: 4 SETS X 10-12 REPS
- REAR DELT FLYS (DUMBBELLS) 4 SETS X 10-12 REPS
- 3 mile run
FRIDAY: ARMS (home gym)
- ALTERNATING DUMBBELL CURLS: 4 SETS X 10-12 REPS
- OVERHEAD TRICEP EXT (DUMBBELL): 4 SETS X 10-12 REPS
- INCLINE DUMBBELL CURL: 4 SETS X 10-12 REPS
- LYING TRICEP EXTENSION: 4 SETS X 10-12 REPS
- HAMMER CURLS: 3 SETS X 10-12 REPS
- CLOSE GRIP BENCH PRESS: 3 SETS X 10-12 REPS
- Swim immediately on wake up (20 mins) [or can run 3 miles or do 45 min elliptical)
SATURDAY: CORE AND GRIP (home gym)
- DUMBBELL DEADLIFTS: 4 SETS X 6-8 REPS
- PLANK WITH DUMBBELL DRAG: 3 SETS X 10-12 REPS
- DUMBBELL V SITS: 4 SETS X 15-20 REPS
- DUMBBELL PLANK ROWS: 3 SETS X 10-12 REPS
- DUMBBELL PINCH HOLD: 3 SETS X 30 SEC - 1 MIN
- Swim immediately on wake up (20 mins) [or can run 3 miles or do 45 min elliptical)
SUNDAY: FULL BODY (home gym)
- DUMBBELL GOBLET SQUAT: 4 SETS X 10-12 REPS
- BULGARIAN SPLIT SQUATS: 4 SETS X 10-12 REPS EACH LEG
- RENEGADE ROWS: 4 SETS X 10-12 REPS
- RUSSIAN TWISTS: 3 SETS X 15-20 REPS EACH SIDE
- GLUTE BRIDGES: 3 SETS X 12-15 REPS
- SIDE PLANKS: 3 SETS X 30-45 SEC HOLD EACH SIDE
- 1 full hour of medium intensity elliptical training
- Stretching / yoga
Wellness
Stress Zero
- Identify spiritually charged intention
- State gratitude
- Iterate through key stressors until stressors have been fully addressed
- Should be recorded for future reference / analytics
Sleep
- 8 or more hours daily with deep sleep tracked via Apple Watch
- No electronic devices 1+ hours before bed
- Consistent bed time
Productivity
My two main tools are Google Docs and a Discord server where I have Python tooling to track my work and thoughts.
Work
- Google Doc periodically updated with Milestones and fed into Project Manager Script to determine next actions
- Every 30 mins of Deep Work logged - triggered w Apple Watch
- 10 hours of deep work/day, 7 days a week
- 1 hour+ per day inside VR - Immersed / office hours
- Important corporate context logged with !ccon function in Discord
What is Deep Work?
Not logged in to Social Media
No Notifications from messaging apps or push notifications
Just one main focus
Autonomous Self
- Default Prompt is clearly defined and referenced
- Big decisions are not made without running the Decisionmaking exercise
- Personal and Corporate KPIs updated daily. KPI performance referenced in decision making
- Important personal context logged with !pcon function in Discord
Weekly Professional/Personal Process
- 1-2 hours spent writing weekly reviewing past week and updating milestone doc
- Updating Sprint Plan / Milestone Document
- Grocery shopping / meal prep (lentil dish is bulk preparation)
- 2-3 hours of feature implementation of software features to improve overall AI systems architecture
- Hire Maid etc.
Manual Override Parameters
- If Diet/Exercise drop off hire personal trainer
- If AI execution system drop off hire personal coach
- If corporate KPIs drop off cut scope


How to make writing in a file, safe ?
General Architecture
![DB1](/img/Screenshot from 2018-08-27 18-09-19.png){:class=“img-responsive”}
Before We start
It’s totally theoritical I have no practical experience in this topic. I want that(practical experience) that’s why I am writing this blog 😉 . This is an original content.
Let’s start
Problem Statement ->
This is a distributed system. Multiple system is trying to read or write from a file, Now how to make it safe ? . Safe in the sense that how can sys 4 possibly know that sys 1 is writing in the file. or how can sys 2 and sys 3 can know that it can get stale data.
Solution 1
As this is a totally controlled environment, we can write our code for write() in the file as, when any of the system loads file in it’s own ram to edit or insert it creates a new file as filename.safe with edit permission to only that system. We can add multiple metadata in filename.safe. Then after completion of task by that system it will remove filename.safe. Now if the sytem 4 wants to write in filename then it will check first that if filename.safe exists or not, if not then it will write by creating .safe else it will wait till .safe is deleted. For reading you can write your read() fucntion as to return request with different code for stale request.
Solution 2
We can write a file controller which will run on system 5 and it will record write request from different system with timestamp and execute it sequentially if some request take lot of time(that’s why timestamp). I think this will be a better solution as it is non blocking in nature and server need not worry as there is only one agent writing to it. I think it is also consume less resource as no one has to continuously check it .safe file exist or not.


EventPump
s to filter the given AWT event.AsyncWorker
.asynchronous tasks
.Task
s and Job
s, but differently
from Worker
, execute them concurrently and not one after the other, though
the invocations to ConcurrentWorker.post(Task)
or ConcurrentWorker.post(Job)
will finish one after
the other.EventPump
s before they're dispatched.EventPumps
that implement this interface have the possibility
to filter AWT events before they are dispatched.Task
s.Task.setResult(java.lang.Object)
.Task
s subclasses in a thread
that is not the Event Dispatch Thread.Task
s.WorkerThread
that uses one or more threads to run
Task
s subclasses.completed
; must be
called from the Event Dispatch Thread.Task
from the internal queue via SingleWorkerThread.takeTask()
and then executes it.Task
.Task
s subclasses in a thread
that is not the Event Dispatch Thread.WorkerThread
that uses a single worker thread to run
Task
s subclasses.Task
s (not in the
Event Dispatch Thread).Task
from the internal queue.Task
s in a thread that is not the Event Dispatch Thread.Copyright © 2002-2011. All Rights Reserved.


| Name |
Description |
awe_child_process_main
|
|
awe_history_entry_destroy
|
History Entry *
|
awe_history_entry_get_title
|
Get the title of the page
|
awe_history_entry_get_url
|
Get the URL of the page
|
awe_history_entry_get_visit_count
|
Get the number of times this page was visited.
|
awe_history_entry_get_visit_time
|
Get the last time this page was visited (in seconds since epoch)
|
awe_history_query_result_destroy
|
History Query Result *
|
awe_history_query_result_get_entry_at_index
|
Get a certain entry (you must destroy any returned entry using awe_history_entry_destroy ).
May return NULL if the index is out of bounds.
|
awe_history_query_result_get_size
|
Get the total number of entries
|
awe_is_child_process
|
|
awe_jsarray_create
|
JS Value Array Functions *
|
awe_jsarray_destroy
|
Destroys a JSValue Array created with awe_jsarray_create .
|
awe_jsarray_get_element
|
Get a specific element of a JSValue Array. The Array retains ownership
of the returned JSValue instance (you do not need to destroy it).
|
awe_jsarray_get_size
|
Get the size of a JSValue Array.
|
awe_jsobject_create
|
JS Value Object Functions *
|
awe_jsobject_destroy
|
Destroys a JSValue Object created with awe_jsobject_create
|
awe_jsobject_get_keys
|
Get a list of all key names as a JSValue Array, you need to call
awe_jsarray_destroy on the returned value after you're done using it.
|
awe_jsobject_get_property
|
Gets the value of a certain named property of a JSValue Object. You do not
need to destroy the returned jsvalue instance, it is owned by the object.
|
awe_jsobject_get_size
|
Get the number of key/value pairs in a JSValue object.
|
awe_jsobject_has_property
|
Returns whether or not a JSValue Object has a certained named property.
|
awe_jsobject_set_property
|
Sets the value of a certained named property of a JSValue Object.
|
awe_jsvalue_create_array_value
|
Create a JSValue instance initialized with an array type. You must call
awe_jsvalue_destroy with the returned instance once you're done using it.
|
awe_jsvalue_create_bool_value
|
Create a JSValue instance initialized with a boolean type. You must call
awe_jsvalue_destroy with the returned instance once you're done using it.
|
awe_jsvalue_create_double_value
|
Create a JSValue instance initialized with a double type. You must call
awe_jsvalue_destroy with the returned instance once you're done using it.
|
awe_jsvalue_create_integer_value
|
Create a JSValue instance initialized with an integer type. You must call
awe_jsvalue_destroy with the returned instance once you're done using it.
|
awe_jsvalue_create_null_value
|
Create a JSValue instance initialized as a null type. You must call
awe_jsvalue_destroy with the returned instance once you're done using it.
|
awe_jsvalue_create_object_value
|
Create a JSValue instance initialized with an object type. You must call
awe_jsvalue_destroy with the returned instance once you're done using it.
|
awe_jsvalue_create_string_value
|
Create a JSValue instance initialized with a string type. You must call
awe_jsvalue_destroy with the returned instance once you're done using it.
|
awe_jsvalue_destroy
|
Destroys a JSValue instance.
|
awe_jsvalue_get_array
|
Returns this value as an array. Will throw an exception if not an array.
|
awe_jsvalue_get_object
|
Returns this value as an object. Will throw an exception if not an object.
|
awe_jsvalue_get_type
|
Get the type of a JSValue.
|
awe_jsvalue_to_boolean
|
Returns this value as an boolean.
|
awe_jsvalue_to_double
|
Returns this value as an double.
|
awe_jsvalue_to_integer
|
Returns this value as an integer.
|
awe_jsvalue_to_string
|
Get the value as a string.
|
awe_renderbuffer_copy_to
|
Copy a RenderBuffer to a specific destination with the same dimensions.
|
awe_renderbuffer_copy_to_float
|
Copy a RenderBuffer to a pixel buffer with a floating-point pixel format
for use with game engines like Unity3D.
|
awe_renderbuffer_flush_alpha
|
Sets the alpha channel to completely opaque values.
|
awe_renderbuffer_get_alpha_at_point
|
Get the alpha value at a certain point (origin is top-left). This is
useful for alpha-picking.
|
awe_renderbuffer_get_buffer
|
Get a pointer to the actual pixel buffer within a RenderBuffer.
|
awe_renderbuffer_get_height
|
Get the height (in pixels) of a RenderBuffer.
|
awe_renderbuffer_get_rowspan
|
Get the rowspan (number of bytes per row) of a RenderBuffer.
|
awe_renderbuffer_get_width
|
Render Buffer Functions *
|
awe_renderbuffer_save_to_jpeg
|
Save a copy of this RenderBuffer to a JPEG image file with quality 1 to 100.
|
awe_renderbuffer_save_to_png
|
Save a copy of this RenderBuffer to a PNG image file.
|
|
|
Append an extra header to the request .
|
awe_resource_request_append_upload_bytes
|
Append a string of bytes for POST data (adds a new UploadElement)
|
awe_resource_request_append_upload_file_path
|
Append a file for POST data (adds a new UploadElement)
|
awe_resource_request_cancel
|
Resource Request *
|
awe_resource_request_clear_upload_elements
|
Clear all upload elements
|
|
|
Get extra headers for the request (You must destroy returned string)
|
awe_resource_request_get_method
|
Get the HTTP method (usually "GET" or "POST") (You must destroy returned string)
|
awe_resource_request_get_num_upload_elements
|
Get the number of upload elements (essentially, batches of POST data).
|
awe_resource_request_get_referrer
|
Get the referrer (You must destroy returned string)
|
awe_resource_request_get_upload_element
|
Get a certain upload element (returned instance is owned by this class)
|
awe_resource_request_get_url
|
Get the URL associated with this request . (You must destroy returned string)
|
|
|
Override extra headers for the request , delimited by /r/n (CRLF).
|
awe_resource_request_set_method
|
Set the HTTP method
|
awe_resource_request_set_referrer
|
Set the referrer
|
awe_resource_response_create
|
Create a ResourceResponse from a raw block of data. (Buffer is copied)
|
awe_resource_response_create_from_file
|
Create a ResourceResponse from a file on disk.
|
awe_string_create_from_ascii
|
Create a string from an ASCII string. You must call awe_string_destroy
with the returned instance once you're done using it.
|
awe_string_create_from_utf16
|
Create a string from a UTF-16 string. You must call awe_string_destroy
with the returned instance once you're done using it.
|
awe_string_create_from_utf8
|
Create a string from a UTF-8 string. You must call awe_string_destroy
with the returned instance once you're done using it.
|
awe_string_create_from_wide
|
Create a string from a Wide string. You must call awe_string_destroy
with the returned instance once you're done using it.
|
awe_string_destroy
|
Destroys a string instance created with one of the above functions.
|
awe_string_empty
|
UTF-16 String Definitions *
|
awe_string_get_length
|
Gets the length of a string.
|
awe_string_get_utf16
|
Get a pointer to the actual internal UTF-16 bytes of a string.
|
awe_string_to_utf8
|
Converts a string to a UTF-8 string by copying to the destination buffer.
|
awe_string_to_wide
|
Converts a string to a wide string by copying to the destination buffer.
|
awe_upload_element_get_bytes
|
Get the string of bytes associated with this UploadElement (You must destroy returned string)
|
awe_upload_element_get_file_path
|
Get the file path associated with this UploadElement (You must destroy returned string)
|
awe_upload_element_is_bytes
|
Whether or not this UploadElement is a string of bytes
|
awe_upload_element_is_file_path
|
Upload Element *
|
awe_webcore_are_plugins_enabled
|
Returns whether or not plugins are enabled.
|
awe_webcore_clear_cache
|
Clear the disk cache and media cache.
|
awe_webcore_clear_cookies
|
Clear all cookies.
|
awe_webcore_create_webview
|
Creates a new WebView.
|
awe_webcore_delete_cookie
|
Deletes a certain cookie on a certain URL.
|
awe_webcore_get_base_directory
|
Retrieves the base directory.
|
awe_webcore_get_cookies
|
Gets all cookies for a certain URL.
|
awe_webcore_initialize
|
Web Core Functions *
|
awe_webcore_initialize_default
|
Instantiates the WebCore singleton with the default parameters
specified in the method above.
|
awe_webcore_query_history
|
Query the on-disk history database.
|
awe_webcore_set_base_directory
|
Sets the base directory.
|
awe_webcore_set_cookie
|
Sets a cookie for a certain URL.
|
awe_webcore_set_custom_response_page
|
Sets a custom response page to use when a WebView encounters a
certain HTML status code from the server (like '404 - File not found').
|
awe_webcore_set_suppress_printer_dialog
|
Set whether or not the printer dialog should be suppressed or not.
Set this to "true" to hide printer dialogs and print immediately
using the OS's default printer when WebView::print is called.
Default is "false" if you never call this.
|
awe_webcore_shutdown
|
Destroys the WebCore singleton and destroys any remaining WebViews.
|
awe_webcore_update
|
Updates the WebCore and allows it to conduct various operations such
as updating the render buffer of each WebView, destroying any
WebViews that are queued for destruction, and invoking any queued
callback events.
|
awe_webview_activate_ime
|
Call this method to let the WebView know you will be passing
text input via IME and will need to be notified of any
IME-related events (caret position, user unfocusing textbox, etc.)
Please see awe_webview_set_callback_update_ime
|
|
|
Adds a new a header re-write rule . All requests whose URL matches the
specified rule will have its HTTP headers re-written with the
specified header definition before sending it to the server.
|
awe_webview_add_url_filter
|
Adds a new URL Filter rule.
|
awe_webview_call_javascript_function
|
Call a certain function defined in Javascript directly.
|
awe_webview_cancel_ime_composition
|
Cancel a current IME text composition.
|
awe_webview_cancel_login
|
Respond to the "request login" callback by telling the
server that the user cancelled the authentication request.
|
awe_webview_choose_file
|
This should be called as a response to the request file chooser callback.
|
awe_webview_clear_all_url_filters
|
Clears all URL Filter rules.
|
awe_webview_close_javascript_dialog
|
Respond to the "show javascript dialog" callback.
|
awe_webview_confirm_ime_composition
|
Confirm a current IME text composition.
|
awe_webview_copy
|
Invokes a 'copy' action using the system clipboard.
|
awe_webview_copy_image_at
|
Copies an image on the page to the system clipboard.
|
awe_webview_create_object
|
Creates a new global Javascript object that will persist throughout
the lifetime of this WebView. This object is managed directly by
Awesomium and so you can modify its properties and bind callback
functions via awe_webview_set_object_property () and
awe_webview_set_object_callback (), respectively.
|
awe_webview_cut
|
Invokes a 'cut' action using the system clipboard.
|
awe_webview_destroy
|
Web View Functions *
|
awe_webview_destroy_object
|
Destroys a Javascript object previously created by
awe_webview_create_object
|
awe_webview_execute_javascript
|
Executes a string of Javascript in the context of the current page
asynchronously.
|
awe_webview_execute_javascript_with_result
|
Executes a string of Javascript in the context of the current page
asynchronously with a result.
|
awe_webview_find
|
Start finding a certain string on the current web-page. All matches
of the string will be highlighted on the page and you can jump
to different instances of the string by using the 'findNext'
parameter. To get actual stats about a certain query, please see
awe_webview_set_callback_get_find_results .
|
awe_webview_focus
|
Notifies the current page that is has gained focus. You will need
to call this to gain textbox focus, among other things. (If you
fail to ever see a blinking caret when typing text, this is why).
|
awe_webview_get_dirty_bounds
|
Returns the bounds of the area that has changed since the last call
to awe_webview_render .
|
awe_webview_get_history_back_count
|
Get the number of steps back in history we can go.
|
awe_webview_get_history_forward_count
|
Get the number of steps forward in history we can go.
|
awe_webview_get_url
|
|
awe_webview_get_zoom
|
Gets the current zoom level.
|
awe_webview_get_zoom_for_host
|
Gets the zoom level for a specific hostname.
|
awe_webview_go_to_history_offset
|
Navigates back/forward in history via a relative offset .
|
awe_webview_inject_keyboard_event
|
Injects a keyboard event. You'll need to initialize the members of
awe_webkeyboardevent yourself.
|
awe_webview_inject_keyboard_event_win
|
Injects a native Windows keyboard event.
|
awe_webview_inject_mouse_down
|
Injects a mouse-down event.
|
awe_webview_inject_mouse_move
|
Injects a mouse-move event in local coordinates.
|
awe_webview_inject_mouse_up
|
Injects a mouse-up event.
|
awe_webview_inject_mouse_wheel
|
Injects a mouse-wheel event.
|
awe_webview_is_dirty
|
Returns whether or not the WebView is dirty and needs to be
re-rendered via awe_webview_render .
|
awe_webview_is_loading_page
|
Returns whether or not a page is currently loading in the WebView.
|
awe_webview_is_resizing
|
Checks whether or not there is a resize operation pending.
|
awe_webview_is_transparent
|
|
awe_webview_load_file
|
Loads a local file into the WebView asynchronously.
|
awe_webview_load_html
|
Loads a string of HTML into the WebView asynchronously.
|
awe_webview_load_url
|
Loads a URL into the WebView asynchronously.
|
awe_webview_login
|
Respond to the "request login" callback with some user-supplied
credentials.
|
awe_webview_paste
|
Invokes a 'paste' action using the system clipboard.
|
awe_webview_pause_rendering
|
All rendering is actually done asynchronously in a separate process
and so the page is usually continuously rendering even if you never
call awe_webview_render . Call this to temporarily pause rendering.
|
awe_webview_print
|
Print the current page. To suppress the printer selection dialog and
print immediately using the operating system's defaults, see
awe_webcore_set_suppress_printer_dialog .
|
awe_webview_reload
|
Reloads the current page.
|
|
|
Removes a header re-write rule from this WebView.
|
|
|
Removes all header re-write rules that are using a certain header
definition.
|
awe_webview_render
|
Renders this WebView into an offscreen render buffer and clears the
dirty state.
|
awe_webview_request_scroll_data
|
Request the page dimensions and scroll position of the page. You can
retrieve the response via the get scroll data callback.
|
awe_webview_reset_zoom
|
Resets the zoom level.
|
awe_webview_resize
|
Resizes this WebView to certain dimensions.
|
awe_webview_resume_rendering
|
Resume rendering after all call to awe_webview_pause_rendering .
|
awe_webview_select_all
|
Selects all items on the current page.
|
awe_webview_set_callback_begin_loading
|
Assign a callback function to be notified when a WebView begins to actually
receive data from a server.
|
awe_webview_set_callback_begin_navigation
|
Assign a callback function to be notified when a WebView begins navigation
to a certain URL.
|
awe_webview_set_callback_change_cursor
|
Assign a callback function to be notified when a cursor has changed state.
|
awe_webview_set_callback_change_history
|
Assign a callback function to be notified whenever the history state
has changed. (eg, the state of thie back/forward buttons should be
updated)
|
awe_webview_set_callback_change_keyboard_focus
|
Assign a callback function to be notified when keyboard focus has changed.
|
awe_webview_set_callback_change_target_url
|
Assign a callback function to be notified when the target URL has changed.
This is usually the result of hovering over a link on the page.
|
awe_webview_set_callback_change_tooltip
|
Assign a callback function to be notified when a tooltip has changed state.
|
awe_webview_set_callback_dom_ready
|
Assign a callback function to be notified once the DOM (Document Object
Model) for a page is ready. This is very useful for executing Javascript
on a page before its content has finished loading.
|
awe_webview_set_callback_finish_loading
|
Assign a callback function to be notified when a WebView has finished
all loads.
|
awe_webview_set_callback_finish_resize
|
Assign a callback function to be notified whenever a WebView has
finished resizing to a certain size (and has finished repainting
the RenderBuffer).
|
awe_webview_set_callback_get_find_results
|
Assign a callback function to be notified whenever we receive
results back from an in-page find operation (awe_webview_find ).
|
awe_webview_set_callback_get_page_contents
|
Assign a callback function to be notified when the contents of the page has finished
loading. This occurs at the end of most page loads.
|
awe_webview_set_callback_get_scroll_data
|
Assign a callback function to be notified of a response to
awe_webview_request_scroll_data .
|
awe_webview_set_callback_js_callback
|
Assign a callback function to be notified when a Javascript object callback
has been invoked on a page.
|
awe_webview_set_callback_js_console_message
|
Assign a callback function to be notified of any Javascript
console messages. (Usually Javascript errors encountered in scripts)
|
awe_webview_set_callback_open_external_link
|
Assign a callback function to be notified when an external link is attempted
to be opened. An external link is any link that normally opens in a new
window in a standard browser (for example, links with target="blank",
calls to window.open(url), and URL open events from Flash plugins).
|
awe_webview_set_callback_plugin_crashed
|
Assign a callback function to be notified when when the renderer for a
certain plugin (usually Flash, which is isolated in a separate process)
crashes unexpectedly.
|
awe_webview_set_callback_receive_title
|
Assign a callback function to be notified when a page title is received.
|
awe_webview_set_callback_request_download
|
Assign a callback function to be notified when a page requests for a certain
URL to be downloaded by the user.
|
awe_webview_set_callback_request_file_chooser
|
Assign a callback function to be notified whenever a page requests a file
chooser dialog to be displayed (usually the result of an "input" element
with type "file" being clicked by a user). You will need to display your
own dialog (it does not have to be modal, this request does not block).
Once a file has been chosen by the user, awe_webview_choose_file or
awe_webview_choose_multiple_files should be called.
|
awe_webview_set_callback_request_login
|
Assign a callback function to be notified whenever a page requests
authentication from the user (ex, Basic HTTP Auth, NTLM Auth, etc.).
See awe_webview_login and awe_webview_cancel_login
|
awe_webview_set_callback_request_move
|
Assign a callback function to be notified when the page requests for the
containing window to be moved to a certain location on the screen.
|
awe_webview_set_callback_resource_request
|
Resource Interceptor *
|
awe_webview_set_callback_resource_response
|
Assign a callback function to intercept responses to requests. You can use
this for tracking/statistic purposes.
|
|
|
Assign a callback function to be notified whenever the page requests
a context menu to be shown (usually the result of a user right-clicking
somewhere on the page). It is your responsiblity to display a menu for
the user to select an appropriate action.
|
awe_webview_set_callback_show_javascript_dialog
|
Assign a callback function to be notified whenever a WebView
requests that a certain Javascript dialog be shown (eg, alert,
confirm, prompt). See awe_webview_close_javascript_dialog for
more information.
|
awe_webview_set_callback_update_ime
|
Assign a callback function to be notified whenever the user does
something that may change the position or visiblity of the IME Widget.
This callback is only active when IME is activated (please
see awe_webview_activate_ime ).
|
awe_webview_set_callback_web_view_crashed
|
Assign a callback function to be notified when the renderer for a certain
WebView (which is isolated in a separate process) crashes unexpectedly.
|
|
|
Defines a new Header Definition or updates it if it already exists.
|
awe_webview_set_ime_composition
|
Update the current IME text composition.
|
awe_webview_set_object_callback
|
Sets a callback function of a Javascript object previously created
by awe_webview_create_object (). This is very useful for passing events
from Javascript to C. To receive notification of the callback, please
see awe_webview_set_callback_js_callback ().
|
awe_webview_set_object_property
|
Sets a property of a Javascript object previously created by
awe_webview_create_object ().
|
awe_webview_set_transparent
|
Sets whether or not pages should be rendered with transparency
preserved. (ex, for pages with style="background-color:transparent")
|
awe_webview_set_url_filtering_mode
|
Sets the current URL Filtering Mode (default is AWE_UFM_NONE).
See awe_url_filtering_mode for more information on the modes.
|
awe_webview_set_zoom
|
Zooms the page a specified percent.
|
awe_webview_stop
|
Stops the current navigation.
|
awe_webview_stop_find
|
Stop finding. This will un-highlight all matches of a previous
call to awe_webview_find .
|
awe_webview_translate_page
|
Attempt automatic translation of the current page via Google
Translate. All language codes are ISO 639-2.
|
awe_webview_unfocus
|
Notifies the current page that it has lost focus.
|


Australia win first Test against Pakistan in Brisbane
by https://www.facebook.com/dunyanewsBRISBANE, Australia (AFP) – Australia beat Pakistan by an innings and five runs in the first Test in Brisbane to go 1-0 up in the two match series on Sunday.
After trailing the hosts by 340 runs on the first innings, Pakistan were bowled out for 335 late on the fourth day.
Earlier, Azam reached his second Test century and his first in Australia with an impressive knock.
The elegant right-hander had been in excellent form in the lead-up games but was out to a disappointing shot in the first innings for just one.
However, he was a different player in the second innings and never looked in any trouble until he edged Nathan Lyon to Tim Paine to fall for 104.
It was Azam’s second century in 22 Tests following hie maiden ton against New Zealand in Dubai in November last year.
He shared partnerships of 68 with Shan Masood and 132 with Rizwan as Pakistan battled hard throughout the first two sessions.

His 42-run partnership with Yasir came in quick time off only 48 balls as they looked to put the pressure back onto the Australians.
After resuming their second innings at 64 for three at the start of day four, Masood and Azam showed great commitment to frustrate the Australian attack.
The Pakistan pair looked comfortable from the beginning and brought up their 50-run partnership midway through the first hour’s play.
But on 42 Masood tried to hook a Pat Cummins short ball and got a thin edge to Australian wicketkeeper Paine to leave the visitors 93 for four.
One run later Paine was in the action again when new batsman Iftikhar Ahmed was squared up by a beautiful ball from Josh Hazlewood and could only manage to edge it through to the Australian captain.
The second Test begins in Adelaide on November 29.
Scoreboard at the end of the first Test between Australia and Pakistan at the Gabba in Brisbane on Sunday
Pakistan 1st innings 240
Australia 1st innings 580
Pakistan 2nd innings (overnight 64-3)
Shan Masood c Paine b Cummins 42
Azhar Ali lbw Starc 5
Haris Sohail c Paine b Starc 8
Asad Shafiq c Smith b Cummins 0
Babar Azam c Paine b Lyon 104
Iftikhar Ahmed c Paine b Hazlewood 0
Mohammad Rizwan c Lyon b Hazlewood 95
Yasir Shah c Wade b Hazlewood 42
Shaheen Afridi c Cummins b Hazlewood 10
Imran Khan c Wade b Starc 5
Naseem Shah not out 0
Extras (b9, lb9, nb1, w5) 24
Total (all out; 84.2 overs) 335
Fall of wickets: 1-13 (Azhar), 2-25 (Sohail), 3-25 (Shafiq), 4-93 (Masood), 5-94 (Iftikhar), 6-226 (Azam), 7-305 (Rizwan), 8-324 (Yasir), 9-331 (Shaheen), 10-335 (Imran)
Bowling: Starc 16.2-1-73-3 (1nb), Cummins 21-6-69-2 (5w), Hazlewood 21-3-63-4, Lyon 21-3-74-1, Labuschagne 5-0-38-0
Toss: Pakistan
Player of the match: Marnus Labuschagne


25th May 2017
I am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectively.I am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectivelyI am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectivelyI am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectively
I am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectively.I am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectivelyI am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectivelyI am a very simple card. I am good at containing small bits of information. I am convenient because I require little markup to use effectively
#python program
n = input("Enter a number")
def func(x,y):
print(x+y)
while(1):
print(123)
About Author
Developer, Tech. Evangalist, Loves to read and write about new tech. Madly in love with Python. Follow him on social media.


East Coast freeze will be so cold, it could break up to 200 records
by CNN NewsourceDon your jackets and mittens, East Coasters. You're going to need them.
The next five to seven days won't just be cold — they'll be record breaking.
That's according to data from the National Weather Service, which predicts that more than 200 record lows could be tied or set from Monday to Wednesday.
It's all part of the Arctic blast that's hitting the East Coast , bringing below-freezing temperatures to some places. On Monday, temperatures are expected to plummet in the Great plains, before moving farther east on Tuesday and Wednesday.
Record low temperatures are possible across Texas, Oklahoma and parts of the Ohio Valley starting Tuesday morning. By Wednesday, more than a dozen record lows could be set in the Deep South and the Gulf Coast, according to CNN meteorologist Taylor Ward.
Some places in the East could experience temperatures on Wednesday afternoon that are up to 30 degrees below average .


First row should be headers and is not imported. Import information to display for each student:
Net ID, Family Name, Given Name, Field 1, Field 2, Field 3, Field 4, Field 5, Field 6
{{admin.import_res}}


mixed gettimeofday ([ bool $return_float = false ] )
This is an interface to gettimeofday(2). It returns an associative array containing the data returned from the system call.
By default an array is returned. If return_float is set, then a float is returned. Array keys: "sec" - seconds since the Unix Epoch "usec" - microseconds "minuteswest" - minutes west of Greenwich "dsttime" - type of dst correction


East Delhi Hub was conceptualized to be a new Transit Oriented Development that imbibes the core values of a sustainable “Smart City”. As a pilot project that experiments with the new TOD policy drafted by DDA, our approach was to incorporate an “organic density” that introduces extensive vertical mixed-use development to tackle the issue of high density and ensure 24-hour active, safer spaces. This includes commercial, residential, medical and recreational facilities and an iconic 100 storey LEED Platinum rated tower that will be a new landmark in Delhi. East Delhi Hub’s design is based on a sustainable grid and building configuration which combines a sustainable orientation with the complex geometry of the site. The result is a highly efficient radial hexagonal system that upholds “Smart Mobility”, “Smart Infrastructure” and “Smart Living”.
Project involves re-development of existing Gandhinagar Capital Station (GNC) building through passenger amenities and modern facilities. The Project also involves development of a 300 Room Hotel building at its air space above station tracks. The entire development is first of its kind in India and therefore a potential landmark project for entire nation.
Read MoreThe Pragati Maidan Convention Centre is designed for a capacity of 7000 people and is proposed to be a world class state of the art Iconic Building deriving its architectural form from the rich architectural heritage of Lutyen’s New Delhi.
Read MoreThis is a high rise, mixed use development in the capital city of Colombo, surrounded by a rich context. Within the vicinity of the site lie the Port of Colombo in the Indian Ocean, Beira Lake, the World Trade Center, Fort Railway Station, Central Bank, Hilton Hotel, the Secretariat Railway Station, etc.
Read MoreDesigned for Delhi Integrated Multi-Modal Transit System Ltd., this prestigious project it comprises of a modern bus terminal keeping in mind passenger volumes for the next 4 decades.
Read MoreFor any kind of query, contact us with the details below.
Please complete the details in the fields below and a TRES stylist will be in contact with you to discuss your styling campaign. Thank you.


XiPKI
XiPKI (eXtensible sImple Public Key Infrastructure) is a highly scalable and high-performance open source PKI (CA and OCSP responder).
License
- The Apache Software License, Version 2.0
Owner
Lijun Liao, LinkedIn
Support
Just create issues.
Prerequisite
- OS: Linux, Windows, MacOS
- JRE / JDK 8 (build 162 or higher)
- Database: DB2, H2, HSQLDB, MariaDB, MySQL, Oracle, PostgreSQL
Tested PKCS#11 Devices
- Softhsm v1 & v2,
- Smartcard HSM EA+,
- Thales nCipher Connect, Thales nCipher Solo, Utimaco Se
Get Started
JAVA_HOME
Set the environment variable JAVA_HOME
to point to root directory of the to
the JRE/JDK installation.
CA and OCSP Responder
Download the binary package xipki-pki-<version>.tar.gz
from
XiPKI releases.
Only if you want to use the development version, build it from source code as follows.
-
Get a copy of project code
git clone https://github.com/xipki/xipki
-
Build the project
In folder
xipki
mvn clean install -Pdist -DskipTests
Then you will find
xipki-pki-*.tar.gz
in the directoryassemblies/xipki-pki/target
.
Configure the CA and OCSP Responder
-
Unpack the binary
xipki-pki-<version>.tar.gz
filetar xvf xipki-pki-<version>.tar.gz
The following steps use
$XIPKI_HOME
to point to the unpacked root folder.The next steps can be skipped if you just want to try out.
-
Adapt the database configuration (optional)
This step may be skipped if you just want to try out XiPKI.
In the folder $XIPKI_HOME/xipki/ca-config
, copy the CA database
configuration template file example/ca-db.properties-<type>
to
ca-db.properties
, and the OCSP database configuration file
example/ocsp-db.properties-<type>
to ocsp-db.properties
, and then adapt
them.
The database users must have both the read and write permissions.
-
Configure PKCS#11 device (optional)
This step is only required if the real PKCS#11 device instead of the emulator is used.
-
In file etc/org.xipki.security.pkcs11.cfg, change the pkcs11.confFile as follows:
pkcs11.confFile = xipki/security/pkcs11-hsm.xml #pkcs11.confFile = xipki/security/pkcs11-emulator.xml
-
In file xipki/security/pkcs11-hsm.xml, change the PKCS#11 configuration.
- Configure how to handle SSL client certificate (optional)
This step is only required if the CA is behind a reverse proxy apache httpd.
-
In file etc/org.xipki.ca.server.cfg, change the sslCertInHttpHeader as follows:
sslCertInHttpHeader = true
-
configure the proxy to forward the headers via mod_proxy with the following configuration
RequestHeader set SSL_CLIENT_VERIFY "%{SSL_CLIENT_VERIFY}s" RequestHeader set SSL_CLIENT_CERT "%{SSL_CLIENT_CERT}s"
For more details please refer to
- Add JDBC drivers (optional)
This step is only required if you want to use database other than H2.
| Database Software | Driver | Download URL |
|---|---|---|
| Oracle | ojdbc7.jar | http://www.oracle.com/technetwork/database/features/jdbc/jdbc-drivers-12c-download-1958347.html |
| DB2 | db2jcc4.jar | |
| MySQL | mysql-connector-java.jar | https://dev.mysql.com/downloads/connector/j, In debian, use the mysql-connector-java.jar from the package libmysql-java (e.g. under /usr/share/java/mysql-connector-java.jar) |
| MariaDB | mariadb-java-client-<version> .jar |
https://downloads.mariadb.org/connector-java/ |
| PostgreSQL | postgresql-<version> .jar |
https://jdbc.postgresql.org/download.html |
| HSQLDB | hsqldb-<version> .jar |
http://hsqldb.org |
-
Copy the jar file to the folder
lib/jdbc
. -
Append the bundle URL to the feature
xipki-jdbc
in the filelib/jdbc/features.xml
, And comment the unneeded jdbc drivers.<feature name="xipki-jdbc" description="JDBC drivers"> ... <bundle start-level="75">file:lib/jdbc/....jar</bundle> </feature>
Note that if the bundle is not an OSGi-bundle, the URL must be prepended by the prefix "wrap:". In general, a bundle contains the header Export-Package in the manifest file META-INF/MANIFEST.MF.
<feature name="xipki-jdbc" description="JDBC drivers"> ... <bundle start-level="75">wrap:file:..</bundle> </feature>
- Use the native features (optional)
In Linux-X86_64 and OSX-X56_64 environment, openssl as SSL engine and the OS
native transport mechanism (Epoll in Linux and KQueue in OSX) can be used in
XiPKI. Please refer to the configuration file
etc/org.apache.karaf.features.cfg
for more details.
Setup CA and OCSP Responder
- Prepare the configuration and scripts
This step is not required if you setup a new root CA (self-signed) using RSA keys which will be generated during the installation process, and the keys are saved in PKCS#12 keystore.
-
If you use the existing CA certificate, OCSP Responder certificate, and SCEP certificate
-
Copy the certificates to the directory to
xipki/setup/keycerts
. -
In case of the key and certificate are saved in PKCS#12 keystore file, copy the PKCS#12 files to the directory
xipki/setup/keycerts
. Note that the key and certificate must be under the same alias in keystore. -
Adapt the CA configuration file
xipki/setup/cacert-present-ca-conf.xml
-
- Start XiPKI
2.1 Alternative: Start XiPKI as a normal application
In folder xipki-pki-<version>
bin/karaf
HSM devices of Thales, e.g. nCipher, can use Thales preload to manage the PKCS#11 sessions. In this case, XiPKI should be started as follows
preload bin/karaf
2.2 Alternative: Start XiPKI as a daemon
The same as Alternative 1 except the command bin/start
instead of
bin/karaf
is used.
For both alternatives, if the content within folder etc
or system
has been
changed, please delete the folder data/cache
before starting XiPKI.
- Setup the CA and OCSP responder
3.1. In case XiPKI is started as a normal application
-
In case of using new keys and certificates, in OSGi console:
source file:./xipki/setup/cacert-none/setup-*.script
where * is place holder. -
In case of using existing keys and certificates, in OSGi console:
source file:./xipki/setup/cacert-present/setup-*.script
where * is place holder. -
Verify the installation, execute the OSGi command
ca-info MYCA1
3.2. In case XiPKI is started as a daemon
-
In case of using new keys and certificates, in shell console:
bin/client "sourcefile:./xipki/setup/cacert-none/setup-*.script"
-
In case of using existing keys and certificates, in shell console:
bin/client "sourcefile:./xipki/setup/cacert-present/setup*.script"
- Enroll/Revoke Certificate and Get CRL via Shell (optional)
-
The following shell script demonstrates how to enroll and revoke certificates, and how to get the current CRL:
xipki/client-script/rest.sh
Note that this script tells CA to generate real certificates. DO NOT use it in the production environment.
Enroll/Revoke Certificate
-
SCEP
Any SCEP client. XiPKI provides also a SCEP client. -
XiPKI SDK
XiPKI SDK provides both the full-featured CA client and the lite version to enroll and revoke certificates via CMP.The binary
xipki-sdk-<version>
.tar.gz contains several example scripts in the folder xipki/client-script. They can be executed in the karaf shell as follows:source file:./xipki/client-script/cmp-client.script
source file:./xipki/client-script/rest-client.script
source file:./xipki/client-script/scep-client.script
-
REST API
The shell scriptxipki/client-script/rest.sh
of thexipki-pki
demonstrates the use of REST API.
Karaf Features
The karaf feature can be installed via the command
feature:install -r <feature name>
(the flag -r disables the refreshing of
already installed bundles) and uninstalled in the OSGi console via the command
feature:uninstall <feature name>
. The possible feature can be auto-completed
by typing the TAB
key.
A list of all available XiPKI features can be retrieved via the command
feature:list | grep xipki
in OSGi console.
For details of karaf features please refer to Karaf Manual: Provisioning
Karaf Commands
Please refer to commands.md for more details.
Components
-
CA (Certification Authority)
- X.509 Certificate v3 (RFC 5280)
- X.509 CRL v2 (RFC 5280)
- SCEP (draft-gutmann-scep-00, draft-nourse-scep-23)
- EN 319 411 (eIDAS)
- EN 319 412 (eIDAS)
- Supported databases: DB2, H2, HSQLDB, MariaDB, MySQL, Oracle
- Direct and indirect CRL
- FullCRL and DeltaCRL
- Customized extension to embed certificates in CRL
- CMP (RFC 4210 and RFC 4211)
- API to specify customized certificate profiles
- Support of XML-based certificate profile
- API to specify customized publisher, e.g. for LDAP and OCSP responder
- Support of publisher for OCSP responder
- Signature algorithms of certificates
- SM3withSM2
- SHA3-*withRSA: where * is 224, 256, 384 and 512
- SHA3-*withRSAandMGF1: where * is 224, 256, 384 and 512
- SHA3-*withECDSA: where * is 224, 256, 384 and 512
- SHA3-*withDSA: where * is 224, 256, 384 and 512
- SHA*withRSA: where * is 1, 224, 256, 384 and 512
- SHA*withRSAandMGF1: where * is 1, 224, 256, 384 and 512
- SHA*withECDSA: where * is 1, 224, 256, 384 and 512
- SHA*withPlainECDSA: where * is 1, 224, 256, 384 and 512
- SHA*withDSA: where * is 1, 224, 256, 384 and 512
-
Native support of X.509 extensions (other extensions can be supported by configuring it as blob)
- AdditionalInformation (German national standard CommonPKI)
- Admission (German national standard CommonPKI)
- AuthorityInformationAccess (RFC 5280)
- AuthorityKeyIdentifier (RFC 5280)
- BasicConstraints (RFC 5280)
- BiometricInfo (RFC 3739)
- CertificatePolicies (RFC 5280)
- CRLDistributionPoints (RFC 5280)
- ExtendedKeyUsage (RFC 5280)
- FreshestCRL (RFC 5280)
- InhibitAnyPolicy (RFC 5280)
- IssuerAltName (RFC 5280)
- KeyUsage (RFC 5280)
- NameConstraints (RFC 5280)
- OcspNoCheck (RFC 6960)
- PolicyConstrains (RFC 5280)
- PolicyMappings (RFC 5280)
- PrivateKeyUsagePeriod (RFC 5280)
- QCStatements (RFC 3739, eIDAS standard EN 319 412)
- Restriction (German national standard CommonPKI)
- SMIMECapabilities (RFC 4262)
- SubjectAltName (RFC 5280)
- SubjectDirectoryAttributes (RFC 3739)
- SubjectInfoAccess (RFC 5280)
- SubjectKeyIdentifier (RFC 5280)
- TLSFeature (RFC 7633)
- ValidityModel (German national standard CommonPKI)
-
Management of multiple CAs in one software instance
-
Support of database cluster
-
Multiple software instances (all can be in active mode) for the same CA
-
Native support of management of CA via embedded OSGi commands
-
API to specify CA management, e.g. GUI
-
Database tool (export and import CA database) simplifies the switch of databases, upgrade of XiPKi and switch from other CA system to XiPKI CA
-
Client to enroll, revoke, unrevoke and remove certificates, to generate and download CRLs
-
All configuration of CA except those of databases is saved in database
-
OCSP Responder
- OCSP Responder (RFC 2560 and RFC 6960)
- Support of Common PKI 2.0
- Management of multiple certificate status sources
- Support of certificate status source published by XiPKI CA
- Support of certificate status source CRL and DeltaCRL
- API to support proprietary certificate sources
- Support of both unsigned and signed OCSP requests
- Multiple software instances (all can be in active mode) for the same OCSP signer and certificate status sources.
- Supported databases: DB2, H2, HSQLDB, MariaDB, MySQL, Oracle
- Database tool (export and import OCSP database) simplifies the switch of databases, upgrade of XiPKi and switch from other OCSP system to XiPKI OCSP.
- Client to send OCSP request
-
SCEP
- Supported SCEP versions
- draft-gutmann-scep-00
- draft-nourse-scep-23
- Supported SCEP versions
-
Toolkit (for both PKCS#12 and PKCS#11 tokens)
- Generating keypairs of RSA, EC and DSA in token
- Deleting keypairs and certificates from token
- Updating certificates in token
- Generating CSR (PKCS#10 request)
- Exporting certificate from token
-
For both CA and OCSP Responder
- Support of PKCS#12 and JKS keystore
- Support of PKCS#11 devices, e.g. HSM
- API to use customized key types, e.g. smartcard
- High performance
- OSGi-based (java), OS independent
- Support of health check
- Audit with syslog and slf4j
-
For CA, OCSP Responder and Toolkit
- API to resolve password
- Support of PBE (password based encryption) password resolver
- All passwords can be encrypted by the master password
- Support of OBF (as in jetty) password resolver


@* * * This template takes a single argument, a String containing a * message to display. *@ @(message: String) @* * Call the `main` template with two arguments. The first * argument is a `String` with the title of the page, the second * argument is an `Html` object containing the body of the page. *@ @main("Add user") { @* * Get an `Html` object by calling the built-in Play welcome * template and passing a `String` message. *@ Home Add user About


There is a growing list of configuration options for the boto library. Many of these options can be passed into the constructors for top-level objects such as connections. Some options, such as credentials, can also be read from environment variables (e.g. AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SECURITY_TOKEN and AWS_PROFILE). It is also possible to manage these options in a central place through the use of boto config files.
A boto config file is a text file formatted like an .ini configuration file that specifies values for options that control the behavior of the boto library. In Unix/Linux systems, on startup, the boto library looks for configuration files in the following locations and in the following order:
In Windows, create a text file that has any name (e.g. boto.config). It’s recommended that you put this file in your user folder. Then set a user environment variable named BOTO_CONFIG to the full path of that file.
The options in the config file are merged into a single, in-memory configuration that is available as boto.config. The boto.pyami.config.Config class is a subclass of the standard Python ConfigParser.SafeConfigParser object and inherits all of the methods of that object. In addition, the boto Config class defines additional methods that are described on the PyamiConfigMethods page.
An example boto config file might look like:
[Credentials]
aws_access_key_id = <your_access_key_here>
aws_secret_access_key = <your_secret_key_here>
The following sections and options are currently recognized within the boto config file.
The Credentials section is used to specify the AWS credentials used for all boto requests. The order of precedence for authentication credentials is:
This section defines the following options: aws_access_key_id and aws_secret_access_key. The former being your AWS key id and the latter being the secret key.
For example:
[profile name_goes_here]
aws_access_key_id = <access key for this profile>
aws_secret_access_key = <secret key for this profile>
[Credentials]
aws_access_key_id = <your default access key>
aws_secret_access_key = <your default secret key>
Please notice that quote characters are not used to either side of the ‘=’ operator even when both your AWS access key ID and secret key are strings.
If you have multiple AWS keypairs that you use for different purposes, use the profile style shown above. You can set an arbitrary number of profiles within your configuration files and then reference them by name when you instantiate your connection. If you specify a profile that does not exist in the configuration, the keys used under the [Credentials] heading will be applied by default.
The shared credentials file in ~/.aws/credentials uses a slightly different format. For example:
[default]
aws_access_key_id = <your default access key>
aws_secret_access_key = <your default secret key>
[name_goes_here]
aws_access_key_id = <access key for this profile>
aws_secret_access_key = <secret key for this profile>
[another_profile]
aws_access_key_id = <access key for this profile>
aws_secret_access_key = <secret key for this profile>
aws_security_token = <optional security token for this profile>
For greater security, the secret key can be stored in a keyring and retrieved via the keyring package. To use a keyring, use keyring, rather than aws_secret_access_key:
[Credentials]
aws_access_key_id = <your access key>
keyring = <keyring name>
To use a keyring, you must have the Python keyring package installed and in the Python path. To learn about setting up keyrings, see the keyring documentation
Credentials can also be supplied for a Eucalyptus service:
[Credentials]
euca_access_key_id = <your access key>
euca_secret_access_key = <your secret key>
Finally, this section is also be used to provide credentials for the Internet Archive API:
[Credentials]
ia_access_key_id = <your access key>
ia_secret_access_key = <your secret key>
The Boto section is used to specify options that control the operation of boto itself. This section defines the following options:
| debug: | Controls the level of debug messages that will be printed by the boto library. The following values are defined: 0 - no debug messages are printed
1 - basic debug messages from boto are printed
2 - all boto debugging messages plus request/response messages from httplib
|
|---|---|
| proxy: | The name of the proxy host to use for connecting to AWS. |
| proxy_port: | The port number to use to connect to the proxy host. |
| proxy_user: | The user name to use when authenticating with proxy host. |
| proxy_pass: | The password to use when authenticating with proxy host. |
| num_retries: | The number of times to retry failed requests to an AWS server. If boto receives an error from AWS, it will attempt to recover and retry the request. The default number of retries is 5 but you can change the default with this option. |
For example:
[Boto]
debug = 0
num_retries = 10
proxy = myproxy.com
proxy_port = 8080
proxy_user = foo
proxy_pass = bar
| connection_stale_duration: | |
|---|---|
| Amount of time to wait in seconds before a connection will stop getting reused. AWS will disconnect connections which have been idle for 180 seconds. | |
| is_secure: | Is the connection over SSL. This setting will overide passed in values. |
| https_validate_certificates: | |
| Validate HTTPS certificates. This is on by default | |
| ca_certificates_file: | |
| Location of CA certificates or the keyword “system”. Using the system keyword lets boto get out of the way and makes the SSL certificate validation the responsibility the underlying SSL implementation provided by the system. | |
| http_socket_timeout: | |
| Timeout used to overwrite the system default socket timeout for httplib . | |
| send_crlf_after_proxy_auth_headers: | |
| Change line ending behaviour with proxies. For more details see this discussion | |
| endpoints_path: | Allows customizing the regions/endpoints available in Boto. Provide an absolute path to a custom JSON file, which gets merged into the defaults. (This can also be specified with the BOTO_ENDPOINTS environment variable instead.) |
These settings will default to:
[Boto]
connection_stale_duration = 180
is_secure = True
https_validate_certificates = True
ca_certificates_file = cacerts.txt
http_socket_timeout = 60
send_crlf_after_proxy_auth_headers = False
endpoints_path = /path/to/my/boto/endpoints.json
You can control the timeouts and number of retries used when retrieving information from the Metadata Service (this is used for retrieving credentials for IAM roles on EC2 instances):
| metadata_service_timeout: | |
|---|---|
| Number of seconds until requests to the metadata service will timeout (float). | |
| metadata_service_num_attempts: | |
| Number of times to attempt to retrieve information from the metadata service before giving up (int). |
These settings will default to:
[Boto]
metadata_service_timeout = 1.0
metadata_service_num_attempts = 1
This section is also used for specifying endpoints for non-AWS services such as Eucalyptus and Walrus.
| eucalyptus_host: | |
|---|---|
| Select a default endpoint host for eucalyptus | |
| walrus_host: | Select a default host for Walrus |
For example:
[Boto]
eucalyptus_host = somehost.example.com
walrus_host = somehost.example.com
Finally, the Boto section is used to set defaults versions for many AWS services
AutoScale settings:
options: :autoscale_version: Set the API version :autoscale_endpoint: Endpoint to use :autoscale_region_name: Default region to use
For example:
[Boto]
autoscale_version = 2011-01-01
autoscale_endpoint = autoscaling.us-west-2.amazonaws.com
autoscale_region_name = us-west-2
Cloudformation settings can also be defined:
| cfn_version: | Cloud formation API version |
|---|---|
| cfn_region_name: | |
| Default region name | |
| cfn_region_endpoint: | |
| Default endpoint |
For example:
[Boto]
cfn_version = 2010-05-15
cfn_region_name = us-west-2
cfn_region_endpoint = cloudformation.us-west-2.amazonaws.com
Cloudsearch settings:
| cs_region_name: | Default cloudsearch region |
|---|---|
| cs_region_endpoint: | |
| Default cloudsearch endpoint |
For example:
[Boto]
cs_region_name = us-west-2
cs_region_endpoint = cloudsearch.us-west-2.amazonaws.com
Cloudwatch settings:
| cloudwatch_version: | |
|---|---|
| Cloudwatch API version | |
| cloudwatch_region_name: | |
| Default region name | |
| cloudwatch_region_endpoint: | |
| Default endpoint |
For example:
[Boto]
cloudwatch_version = 2010-08-01
cloudwatch_region_name = us-west-2
cloudwatch_region_endpoint = monitoring.us-west-2.amazonaws.com
EC2 settings:
| ec2_version: | EC2 API version |
|---|---|
| ec2_region_name: | |
| Default region name | |
| ec2_region_endpoint: | |
| Default endpoint |
For example:
[Boto]
ec2_version = 2012-12-01
ec2_region_name = us-west-2
ec2_region_endpoint = ec2.us-west-2.amazonaws.com
ELB settings:
| elb_version: | ELB API version |
|---|---|
| elb_region_name: | |
| Default region name | |
| elb_region_endpoint: | |
| Default endpoint |
For example:
[Boto]
elb_version = 2012-06-01
elb_region_name = us-west-2
elb_region_endpoint = elasticloadbalancing.us-west-2.amazonaws.com
EMR settings:
| emr_version: | EMR API version |
|---|---|
| emr_region_name: | |
| Default region name | |
| emr_region_endpoint: | |
| Default endpoint |
For example:
[Boto]
emr_version = 2009-03-31
emr_region_name = us-west-2
emr_region_endpoint = elasticmapreduce.us-west-2.amazonaws.com
Even if you have your boto config setup, you can also have credentials and options stored in environmental variables or you can explicitly pass them to method calls i.e.:
>>> boto.ec2.connect_to_region(
... 'us-west-2',
... aws_access_key_id='foo',
... aws_secret_access_key='bar')
In these cases where these options can be found in more than one place boto will first use the explicitly supplied arguments, if none found it will then look for them amidst environment variables and if that fails it will use the ones in boto config.
If you are using notifications for boto.pyami, you can specify the email details through the following variables.
| smtp_from: | Used as the sender in notification emails. |
|---|---|
| smtp_to: | Destination to which emails should be sent |
| smtp_host: | Host to connect to when sending notification emails. |
| smtp_port: | Port to connect to when connecting to the :smtp_host: |
Default values are:
[notification]
smtp_from = boto
smtp_to = None
smtp_host = localhost
smtp_port = 25
smtp_tls = True
smtp_user = john
smtp_pass = hunter2
The SWF section allows you to configure the default region to be used for the Amazon Simple Workflow service.
| region: | Set the default region |
|---|
Example:
[SWF]
region = us-west-2
The Pyami section is used to configure the working directory for PyAMI.
| working_dir: | Working directory used by PyAMI |
|---|
Example:
[Pyami]
working_dir = /home/foo/
The DB section is used to configure access to databases through the boto.sdb.db.manager.get_manager() function.
| db_type: | Type of the database. Current allowed values are SimpleDB and XML. |
|---|---|
| db_user: | AWS access key id. |
| db_passwd: | AWS secret access key. |
| db_name: | Database that will be connected to. |
| db_table: | Table name :note: This doesn’t appear to be used. |
| db_host: | Host to connect to |
| db_port: | Port to connect to |
| enable_ssl: | Use SSL |
More examples:
[DB]
db_type = SimpleDB
db_user = <aws access key id>
db_passwd = <aws secret access key>
db_name = my_domain
db_table = table
db_host = sdb.amazonaws.com
enable_ssl = True
debug = True
[DB_TestBasic]
db_type = SimpleDB
db_user = <another aws access key id>
db_passwd = <another aws secret access key>
db_name = basic_domain
db_port = 1111
This section is used to configure SimpleDB
| region: | Set the region to which SDB should connect |
|---|
Example:
[SDB]
region = us-west-2
This section is used to configure DynamoDB
| region: | Choose the default region |
|---|---|
| validate_checksums: | |
| Check checksums returned by DynamoDB |
Example:
[DynamoDB]
region = us-west-2
validate_checksums = True


|
Xerces-C++
3.1.4
|
Default base class for handlers. More...
Public Member Functions | |
| HandlerBase () | |
| virtual | ~HandlerBase () |
Default handlers for the DocumentHandler interface | |
| virtual void | characters (const XMLCh *const chars, const XMLSize_t length) |
| Receive notification of character data inside an element. More... | |
| virtual void | endDocument () |
| Receive notification of the end of the document. More... | |
| virtual void | endElement (const XMLCh *const name) |
| Receive notification of the end of an element. More... | |
| virtual void | ignorableWhitespace (const XMLCh *const chars, const XMLSize_t length) |
| Receive notification of ignorable whitespace in element content. More... | |
| virtual void | processingInstruction (const XMLCh *const target, const XMLCh *const data) |
| Receive notification of a processing instruction. More... | |
| virtual void | resetDocument () |
| Reset the Document object on its reuse. More... | |
Default implementation of DocumentHandler interface | |
| virtual void | setDocumentLocator (const Locator *const locator) |
| Receive a Locator object for document events. More... | |
| virtual void | startDocument () |
| Receive notification of the beginning of the document. More... | |
| virtual void | startElement (const XMLCh *const name, AttributeList &attributes) |
| Receive notification of the start of an element. More... | |
Default implementation of the EntityResolver interface. | |
| virtual InputSource * | resolveEntity (const XMLCh *const publicId, const XMLCh *const systemId) |
| Resolve an external entity. More... | |
Default implementation of the ErrorHandler interface | |
| virtual void | error (const SAXParseException &exc) |
| Receive notification of a recoverable parser error. More... | |
| virtual void | fatalError (const SAXParseException &exc) |
| Report a fatal XML parsing error. More... | |
| virtual void | warning (const SAXParseException &exc) |
| Receive notification of a parser warning. More... | |
| virtual void | resetErrors () |
| Reset the Error handler object on its reuse. More... | |
Default implementation of DTDHandler interface. | |
| virtual void | notationDecl (const XMLCh *const name, const XMLCh *const publicId, const XMLCh *const systemId) |
| Receive notification of a notation declaration. More... | |
| virtual void | resetDocType () |
| Reset the DTD object on its reuse. More... | |
| virtual void | unparsedEntityDecl (const XMLCh *const name, const XMLCh *const publicId, const XMLCh *const systemId, const XMLCh *const notationName) |
| Receive notification of an unparsed entity declaration. More... | |
| Public Member Functions inherited from EntityResolver | |
| EntityResolver () | |
| Default Constructor. More... | |
| virtual | ~EntityResolver () |
| Destructor. More... | |
| Public Member Functions inherited from DTDHandler | |
| DTDHandler () | |
| Default Constructor. More... | |
| virtual | ~DTDHandler () |
| Destructor. More... | |
| Public Member Functions inherited from DocumentHandler | |
| DocumentHandler () | |
| Default constructor. More... | |
| virtual | ~DocumentHandler () |
| Destructor. More... | |
| Public Member Functions inherited from ErrorHandler | |
| ErrorHandler () | |
| Default constructor. More... | |
| virtual | ~ErrorHandler () |
| Destructor. More... | |
Default base class for handlers.
This class implements the default behaviour for four SAX interfaces: EntityResolver, DTDHandler, DocumentHandler, and ErrorHandler.
Application writers can extend this class when they need to implement only part of an interface; parser writers can instantiate this class to provide default handlers when the application has not supplied its own.
Note that the use of this class is optional.
| HandlerBase::HandlerBase | ( | ) |
|
virtual |
Receive notification of character data inside an element.
By default, do nothing. Application writers may override this method to take specific actions for each chunk of character data (such as adding the data to a node or buffer, or printing it to a file).
| chars | The characters. |
| length | The number of characters to use from the character array. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DocumentHandler.
|
virtual |
Receive notification of the end of the document.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the beginning of a document (such as finalising a tree or closing an output file).
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DocumentHandler.
|
virtual |
Receive notification of the end of an element.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the end of each element (such as finalising a tree node or writing output to a file).
| name | The element type name. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DocumentHandler.
|
virtual |
Receive notification of a recoverable parser error.
The default implementation does nothing. Application writers may override this method in a subclass to take specific actions for each error, such as inserting the message in a log file or printing it to the console.
| exc | The warning information encoded as an exception. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ErrorHandler.
|
virtual |
Report a fatal XML parsing error.
The default implementation throws a SAXParseException. Application writers may override this method in a subclass if they need to take specific actions for each fatal error (such as collecting all of the errors into a single report): in any case, the application must stop all regular processing when this method is invoked, since the document is no longer reliable, and the parser may no longer report parsing events.
| exc | The error information encoded as an exception. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ErrorHandler.
Receive notification of ignorable whitespace in element content.
By default, do nothing. Application writers may override this method to take specific actions for each chunk of ignorable whitespace (such as adding data to a node or buffer, or printing it to a file).
| chars | The whitespace characters. |
| length | The number of characters to use from the character array. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DocumentHandler.
|
virtual |
Receive notification of a notation declaration.
By default, do nothing. Application writers may override this method in a subclass if they wish to keep track of the notations declared in a document.
| name | The notation name. |
| publicId | The notation public identifier, or null if not available. |
| systemId | The notation system identifier. |
Implements DTDHandler.
|
virtual |
Receive notification of a processing instruction.
By default, do nothing. Application writers may override this method in a subclass to take specific actions for each processing instruction, such as setting status variables or invoking other methods.
| target | The processing instruction target. |
| data | The processing instruction data, or null if none is supplied. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DocumentHandler.
|
virtual |
|
virtual |
Reset the Document object on its reuse.
Implements DocumentHandler.
|
virtual |
Reset the Error handler object on its reuse.
Implements ErrorHandler.
|
virtual |
Resolve an external entity.
Always return null, so that the parser will use the system identifier provided in the XML document. This method implements the SAX default behaviour: application writers can override it in a subclass to do special translations such as catalog lookups or URI redirection.
| publicId | The public identifier, or null if none is available. |
| systemId | The system identifier provided in the XML document. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements EntityResolver.
|
virtual |
Receive a Locator object for document events.
By default, do nothing. Application writers may override this method in a subclass if they wish to store the locator for use with other document events.
| locator | A locator for all SAX document events. |
Implements DocumentHandler.
|
virtual |
Receive notification of the beginning of the document.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the beginning of a document (such as allocating the root node of a tree or creating an output file).
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DocumentHandler.
|
virtual |
Receive notification of the start of an element.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the start of each element (such as allocating a new tree node or writing output to a file).
| name | The element type name. |
| attributes | The specified or defaulted attributes. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DocumentHandler.
|
virtual |
Receive notification of an unparsed entity declaration.
By default, do nothing. Application writers may override this method in a subclass to keep track of the unparsed entities declared in a document.
| name | The entity name. |
| publicId | The entity public identifier, or null if not available. |
| systemId | The entity system identifier. |
| notationName | The name of the associated notation. |
Implements DTDHandler.
|
virtual |
Receive notification of a parser warning.
The default implementation does nothing. Application writers may override this method in a subclass to take specific actions for each warning, such as inserting the message in a log file or printing it to the console.
| exc | The warning information encoded as an exception. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ErrorHandler.


BART
Bay Area Rapid Transit
Welcome! Your visit number is:
Quick Plan
View Map
Trip Details
Station Information
Sourrce Station
Destination Station
Next train will arrive in


I'm A Celebrity viewers in awe of Caitlyn Jenner as campmates take first jungle showers
Hunky James Haskell also stripped off for a wash
by Robert LeighFans of Caitlyn Jenner were bursting with pride this evening as the 70-year-old ex Olympian stripped down for a jungle shower on I'm A Celebrity.
Caitlyn and rugby hunk James Haskell became the first campmates to flash some flesh this series as they got down to their smalls to keep clean.
The pumping efforts of Adele Roberts and Nadine Coyle meant the water was available to go in the campsite.
And Kate Garraway was among the other stars to lend a helping hand and pour the water from above the heads of Caitlyn and James.
Read more: I'm A Celebrity viewers demand ITV add subtitles for Nadine Coyle
But the sudden gushes of water seemed to take Caitlyn by surprise, leaving her spluttering.
James, however, seemed less surprised by the spurting water and managed to lather up without any difficulty.
And even though dozens of viewers expressed admiration on Twitter for James' physique, it was Caitlyn's moment under the makeshift waterfall that stole the attention.
Disappointingly, negative comments surrounding her gender transition were all over Twitter.
Read more: Andi Peters takes the mick out of himself as he addresses Ant and Dec jibe
However, there were also many positive remarks from those watching who found her bravery inspirational.
"Seeing caitlyn jenner, a 70 year-old transgender woman, having a shower in a bikini on mainstream TV honestly is so important and amazing🥰 #ImACeleb," tweeted one person.
Another wrote: "Say what you want about Caitlyn Jenner but not many people would be brave enough to go on tv in a bikini in the shower after all the criticism and judgement she gets! 👏🏼 #ImACeleb #imacelebrity."

And yet another praised her: "Hats off to caitlyn jenner, I’m sorry but she’s a transgender woman, she is 70 years old, she jumped out of a plane at 70 YEARS OLD and now she’s brave enough to shower in front of the world when she knows exactly what people will be thinking and saying👏🏼👏🏼 #ImACeleb."
- Episode 3 of I'm A Celebrity airs on ITV on Tuesday November 19 at 9pm
Leave us a comment on our Facebook page @EntertainmentDailyFix and let us know what you think of this story.


This API is used for communication with phone/softphone apps. This API is closely related to API "com.innovaphone.phone". If an App provides this API it receives messages "CallAdded" and "CallUpdated" and "CallRemoved". An App can provide call-related display information to the phone app (e.g. about remote party).
The provideApi function is used to subscribe for API messages:
var phoneinfoApi = start.provideApi("com.innovaphone.phoneinfo");
phoneinfoApi.onmessage.attach(function (sender, obj) {
switch (obj.msg.mt) {
case "CallAdded":
break;
case "CallUpdated":
break;
case "CallRemoved":
break;
}
});
Send by Phone-App to all API providers whenever a new call is born.
{
mt: "CallAdded",
id: 1,
guid: "fff79c5bd2115d0109f400903341035b"
}
| string mt | message type [mandatory] |
| number id | uniqe call-id [mandatory] |
| string guid | globally uniqe call-id [optional] |
Send by Phone-App to all API providers whenever call's attributes have changed.
{
mt: "CallUpdated",
id: 1,
guid: "fff79c5bd2115d0109f400903341035b",
dir: "i",
num: "200",
sip: "charlie.chaplin",
dn: "Sir Charles Spencer Chaplin",
state: "Connected"
}
| string mt | message type [mandatory] |
| number id | uniqe call-id [mandatory] |
| string guid | globally uniqe call-id [optional] |
| string dir | "i" for inbound call or "o" for outbound call [mandatory] |
| string num | Phonenumber (e.g. 202 or +49 7031 73009 0) [optional] |
| string sip | SIP-URI (e.g. charlie.chaplin or<EMAIL_ADDRESS>[optional] |
| string dn | Displayname [optional] |
| string state | Setup | Dialing | Ringback | Queued | Alerting | Connected | Holding | Held | Disconnected [mandatory] |
Send by Phone-App to all API providers whenever a call has died.
{
mt: "CallRemoved",
id: 1,
guid: "fff79c5bd2115d0109f400903341035b"
}
| string mt | message type [mandatory] |
| number id | uniqe call-id [mandatory] |
| string guid | globally uniqe call-id [optional] |
An App can provide call-related display information to the phone app (e.g. about remote party).
See API "com.innovaphone.phone" for details.
var phoneApi = start.consumeApi("com.innovaphone.phone");
var phoneinfoApi = start.provideApi("com.innovaphone.phoneinfo");
phoneinfoApi.onmessage.attach(function (sender, obj) {
switch (obj.msg.mt) {
case "CallAdded":
break;
case "CallUpdated":
if (obj.msg.state == "Connected") {
phoneApi.send({ mt: "CallInfo", id: obj.msg.id, guid: obj.msg.guid, html: "
Here's my info
" }, obj.consumer);
}
break;
case "CallRemoved":
break;
}
});


|
Embedded Artistry Framework
Embedded Systems C++ Framework
|
Files | |
| file | e_acoshl.c |
| file | e_atanhl.c |
| file | e_coshl.c |
| file | e_expl.c |
| file | e_fmodl.c |
| file | e_hypotl.c |
| file | e_lgammal_r.c |
| file | e_log10l.c |
| file | e_log2l.c |
| file | e_logl.c |
| file | e_powl.c |
| file | e_rem_pio2l.h |
| file | e_sinhl.c |
| file | e_tgammal.c |
| file | invtrig.c |
| file | invtrig.h |
| file | k_cosl.c |
| file | k_sinl.c |
| file | k_tanl.c |
| file | s_asinhl.c |
| file | s_ceill.c |
| file | s_erfl.c |
| file | s_exp2l.c |
| file | s_expm1l.c |
| file | s_floorl.c |
| file | s_log1pl.c |
| file | s_modfl.c |
| file | s_nanl.c |
| file | s_nextafterl.c |
| file | s_nexttoward.c |
| file | s_nexttowardf.c |
| file | s_remquol.c |
| file | s_tanhl.c |
| file | s_truncl.c |


This will send a message from the main-context, await until the iframe and the web-worker answered, then repeat until all messages have been send.
This is kirby, which stucks if the process is blocked


We're sorry but mqttx doesn't work properly without JavaScript enabled. Please enable it to continue.