The beach (party)
Went to a market in nearby Bangalow, then spent the rest of the day working on Jeff's web site. Except that I got plastered at a beach party; 15 of us tried to leg it in over the back to avoid paying. Most of us got caught, but the guy who caught us was sao relaxed he apologised about it! That's how chilled out this place is.
Apart from some of the Brits. Upper-class dickheads almost started a puch-up outside the pie shop at 3am. But when the guys from Bristol we were with offered them out they bricked it and ran away. Har-de-har-har!
Back to the main page


{% extends 'templates/nhsbsa_website_template.html' %} {% import 'includes/form_macros.html' as form_macros %} {% block content %} NHSBSA Back Do you get any of the following Additional Elements of Universal Credit? Child element Limited capability for work element £126.11 per month Limited capability for work related activity element £315.60 per month Yes No {{ form_macros.button({ label: 'Next' }) }} {% endblock %}


Return Value
a Reducer<GlobalAction, GlobalState>
that maps actions and states from the original specialized reducer into a more generic and global reducer, to be used in a larger context.
Reducer
handles Part, that is a sub-state.
func lift<GlobalActionType, GlobalStateType>(action: KeyPath<GlobalActionType, ActionType?>, state: WritableKeyPath<GlobalStateType, StateType>) -> Reducer<GlobalActionType, GlobalStateType>
a Reducer<GlobalAction, GlobalState>
that maps actions and states from the original specialized reducer into a more generic and global reducer, to be used in a larger context.
action
a read-only key-path from global action into a local action, but it’s optional because maybe this reducer shouldn’t care about certain actions. Because actions are usually enums, you can switch over the enum and in case it’s nothing you care about, you simply return nil in the closure. If you don’t want to lift this reducer in terms of action
, just remove this parameter from the call.
state
a writable key-path from global state that traverses into a local state, by extracting only the part that it’s relevant for this reducer. This will also be used to set the new local state into the global state once the reducer finishes it’s operation. For example: \.currentGame.scoreBoard
.
Let’s suppose you may want to have a gpsReducer
that knows about the following struct
:
struct Location {
let latitude: Double
let longitude: Double
}
Let’s call it Part. Both, this state and its reducer will be part of an external framework, used by dozens of apps. Internally probably the Reducer
will receive some known ActionType
and calculate a new location. On the main app we have a global state, that we now call Whole.
struct MyGlobalState {
let title: String?
let listOfItems: [Item]
let currentLocation: Location
}
As expected, Part (Location
) is a property of Whole (MyGlobalState
). This relationship could be less direct, for example there could be several levels of properties until you find the Part in the Whole, like global.firstLevel.secondLevel.currentLocation
, but let’s keep it a single-level for this example.
Because our Store
understands Whole (MyGlobalState
) and our gpsReducer
understands Part (Location
), we must lift
the Reducer
to the Whole level, by using:
let globalStateReducer = gpsReducer.lift(action: \.locationActions,
state: \.currentLocation)
Now this reducer can be used within our Store
or even composed with others. It also can be used in other apps as long as we have a way to lift it to the world of Whole.
Same strategy works for the action
, as you can guess by the action
parameter. You can provide a key-path that traverses from a global action (Whole) and to an optional local action (Part). It’s optional because perhaps you want to ignore actions that are not relevant for this reducer.


| Assignments | {{ student.name }} | {{ addStudent.error }} | ||
| Category | Due Date | Total Points | {{ asPercent(gradeFor(classroom, student)) }} | |
|
{{ addAssignment.error }}
|
| Category | Weight | Percentage |
| {{ category }} | {{ categoryWeightPercent(category) }} |


| Card number: |
************4242 |
| Expiration date: |
{{data['exp-month']}}/{{data['exp-year']}} |
| Name on card: |
{{data['card-name']}} |
| Billing address: |
{{data['address']}} {{data['city']}} {{data['postcode']}}
|
| Email address: |
{{data['email']}} |
| Payment description: |
{{data['payment-description']}} |
| Amount to pay: |
£{{data['amount-paid']}} |


QuantumVariationalEigensolver¶
-
class
zyglrox.models.qve.
QuantumVariationalEigensolver
(hamiltonian: zyglrox.core.hamiltonians.Hamiltonian, qc: zyglrox.core.circuit.QuantumCircuit, exact=False, optimizer=None, **kwargs)¶ Quantum Variational Eigensolver according to Peruzzo et al. (2014) with gradient based optimization.
We take a quantum circuit with parameters \(\theta\) which implements some unitary transformation \(\mathcal{U}(\theta)\). This unitary brings our initial state \(|0\rangle\) to a state \(|\psi(\theta)\rangle\).
\[\mathcal{U}(\theta)|0\rangle = |\psi(\theta)\rangle\]Then, we realize that any Hamiltonian \(H\) can be written as a polynomial of single qubit interactions.
\[H = \sum_{i\alpha} h_\alpha^i \sigma_i^\alpha + \sum_{ij\alpha\beta} w_{\alpha\beta}^{ij} \sigma_{i}^{\alpha}\sigma_{j}^{\beta} + \ldots\]where \(i,j,\ldots=1,\ldots,N\) indicate the qubit and \(\alpha,\beta,\ldots=x,y,z\) indicates the Pauli operator. By measuring the expectation values of the quantum circuit, we obtain a variational energy which is a lower bound on the true energy \(\langle H \rangle = \langle \psi| H |\psi \rangle\).
\[\langle H \rangle \approx \langle H \rangle_{\theta} = \sum_{i\alpha} h_\alpha^i \langle\sigma_i^\alpha\rangle + \sum_{ij\alpha\beta} w_{\alpha\beta}^{ij} \langle \sigma_{i}^{\alpha} \sigma_{j}^{\beta}\rangle + \ldots\]By minimizing this variational energy, we hope to learn a quantum circuit which best represents the groundstate of \(H\). If this minimization is successful, we can easily sample the ground state.
For the Gradient-based QVE, we calculate the gradient for each parametrized unitary in the quantum circuit as follows:
\[\frac{\partial \mathcal{U}(\theta) }{\partial \theta_j} = \left(\prod_{i=1}^{j-1} \mathcal{U}_i(\theta_i)\right) \frac{\partial \mathcal{U}_j(\theta_j) }{\partial \theta_j} \left(\prod_{i=j+1}^{M} \mathcal{U}_i(\theta_i)\right)\]- Args:
- hamiltonian (list):
List of numpy arrays containing the operators and their locations. See
verify_hamiltonian()
for the required format.- qc (QuantumCircuit):
QuantumCircuit
object containing a quantum circuit architecture.- exact (bool):
Boolean indicating whether we want to calculate the exact ground state and eigenvectors of the Hamiltonian. Will throw an error if the number of qubits is larger than 18.
- optimizer (tf.optimizers.Optimizer):
Desired optimizer to perform the QVE algorithm.
- Returns (inplace):
None
-
train
(max_iter: int = 1000, tol: float = 1e-08, fetch_from_graph={}, sc_method: str = 'single') → numpy.ndarray¶ Train the quantum variational eigensolver. We minimize the energy \(\langle H \rangle_\theta\) as defined above.
- Args:
- max_iter (int):
Number of max iterations for the training algorithm.
- tol (float):
Tolerance on the energy. If the absolute difference between iterations is smaller than this value, training stops.
- fetch_from_graph (dict):
Tolerance on the energy. If the absolute difference between iterations is smaller than this value, training stops.
- sc_method (str):
Method for stopping criterion.
- Returns expvals (np.ndarray):
Expectation values after training is complete.
-
get_convergence
(plot=False) → Optional[float]¶ Plot the energy at each epoch. If the argument exact=True was passed to the``QuantumVariationalEigensolverGradFree`` constructor we also calculates the residual energy \(\epsilon_{\text{res}} = |\text{min}(E_{qc} - E_{gs_wavefunction})|\). Otherwise returns None
- Args:
- plot (bool):
Wheter to plot the training schedule.
- Returns (float):
Residual energy.
-
get_statistics
(plot=True)¶ Compare the ground state statistics of the
QuantumCircuit
with the exact ground state statistics.\[\begin{split}\text{MSE}_{h} = \frac{1}{M} \sum_i^M (\langle \sigma_i \rangle - \langle \hat{\sigma}_i \rangle)^2 \\ \text{MSE}_{w} = \frac{1}{M} \sum_{i,j}^M (\langle \sigma_i \sigma_j \rangle - \langle \hat{\sigma}_i \hat{\sigma}_j\rangle)^2\end{split}\]- Args:
- plot (bool):
Whether to plot the training schedule.
- Returns (dict):
Dict with entries ‘field’ and ‘coupling’ with the respective MSE between the circuit and true statistics.
-
get_wavefunction
(plot=False)¶ Compare the exact ground state wave function with the quantum circuit wave function by calculating the overlap
\[R = |\langle \psi(\theta)| \psi_0\rangle|^2\]- Args:
- plot (bool):
Whether to plot the training schedule.
- Returns (float):
The overlap \(R\)


{% extends "global/Base.html" %} {% load staticfiles otree_tags %} {% block title %} Period 2 {% endblock %} {% block content %}
You will now start the Earnings Task of Period 2.


Select two cascs whose projects you would like to compare for similarity. (NB: Similarity is based solely on the project summary)
Hover over CASCs (the squares) or links (connections) for more information on them
Click on a CASC to open its Sciencebase page in a new tab
Click on a link (connection) to view details about the two connected projects
Move the slider below the visualization to filter out links with lower similarities      (the slider range is set to the lowest and highest project similarity values for the selected CASCs)


ZooKeeper 3.0.0 Release Notes
These release notes include new developer and user facing incompatibilities, features, and major improvements.
Migration Instructions when Upgrading to 3.0.0
You should only have to read this section if you are upgrading from a previous version of ZooKeeper to version 3.0.0, otw skip down to changes
A small number of changes in this release have resulted in non-backward compatible Zookeeper client user code and server instance data. The following instructions provide details on how to migrate code and date from version 2.2.1 to version 3.0.0.
Note: ZooKeeper increments the major version number (major.minor.fix) when backward incompatible changes are made to the source base. As part of the migration from SourceForge we changed the package structure (com.yahoo.zookeeper.* to org.apache.zookeeper.*) and felt it was a good time to incorporate some changes that we had been withholding. As a result the following will be required when migrating from 2.2.1 to 3.0.0 version of ZooKeeper.
Migrating Client Code
The underlying client-server protocol has changed in version 3.0.0 of ZooKeeper. As a result clients must be upgraded along with serving clusters to ensure proper operation of the system (old pre-3.0.0 clients are not guaranteed to operate against upgraded 3.0.0 servers and vice-versa).
Watch Management
In previous releases of ZooKeeper any watches registered by clients were lost if the client lost a connection to a ZooKeeper server. This meant that developers had to track watches they were interested in and reregister them if a session disconnect event was recieved. In this release the client library tracks watches that a client has registered and reregisters the watches when a connection is made to a new server. Applications that still manually reregister interest should continue working properly as long as they are able to handle unsolicited watches. For example, an old application may register a watch for /foo and /goo, lose the connection, and reregister only /goo. As long as the application is able to recieve a notification for /foo, (probably ignoring it) it does not need to be changed. One caveat to the watch management: it is possible to miss an event for the creation and deletion of a znode if watching for creation and both the create and delete happens while the client is disconnected from ZooKeeper.
This release also allows clients to specify call specific watch functions. This gives the developer the ability to modularize logic in different watch functions rather than cramming everything in the watch function attached to the ZooKeeper handle. Call specific watch functions receive all session events for as long as they are active, but will only receive the watch callbacks for which they are registered.
Java API
-
The java package structure has changed from com.yahoo.zookeeper* to org.apache.zookeeper*. This will probably effect all of your java code which makes use of ZooKeeper APIs (typically import statements)
-
A number of constants used in the client ZooKeeper API were re-specified using enums (rather than ints). See ZOOKEEPER-7, ZOOKEEPER-132 and ZOOKEEPER-139 for full details
-
ZOOKEEPER-18 removed KeeperStateChanged, use KeeperStateDisconnected instead
Also see the current java API
C API
-
A number of constants used in the client ZooKeeper API were renamed in order to reduce namespace collision, see ZOOKEEPER-6 for full details
Migrating Server Data
The following issues resulted in changes to the on-disk data format (the snapshot and transaction log files contained within the ZK data directory) and require a migration utility to be run.
The following must be run once, and only once, when upgrading the ZooKeeper server instances to version 3.0.0.
The <dataLogDir> and <dataDir> directories referenced below are specified by the dataLogDir and dataDir specification in your ZooKeeper config file respectively. dataLogDir defaults to the value of dataDir if not specified explicitly in the ZooKeeper server config file (in which case provide the same directory for both parameters to the upgrade utility).
-
Shutdown the ZooKeeper server cluster.
-
Backup your <dataLogDir> and <dataDir> directories
-
Run upgrade using
-
bin/zkServer.sh upgrade <dataLogDir> <dataDir>
or
-
java -classpath pathtolog4j:pathtozookeeper.jar UpgradeMain <dataLogDir> <dataDir>
where <dataLogDir> is the directory where all transaction logs (log.*) are stored. <dataDir> is the directory where all the snapshots (snapshot.*) are stored.
-
-
Restart the cluster.
If you have any failure during the upgrade procedure keep reading to sanitize your database.
This is how upgrade works in ZooKeeper. This will help you troubleshoot in case you have problems while upgrading
-
Upgrade moves files from <dataLogDir> and <dataDir> to <dataLogDir>/version-1/ and <dataDir>/version-1 respectively (version-1 sub-directory is created by the upgrade utility).
-
Upgrade creates a new version sub-directory <dataDir>/version-2 and <dataLogDir>/version-2
-
Upgrade reads the old database from <dataDir>/version-1 and <dataLogDir>/version-1 into the memory and creates a new upgraded snapshot.
-
Upgrade writes the new database in <dataDir>/version-2.
Troubleshooting.
-
In case you start ZooKeeper 3.0 without upgrading from 2.0 on a 2.0 database - the servers will start up with an empty database. This is because the servers assume that <dataDir>/version-2 and <dataLogDir>/version-2 will have the database to start with. Since this will be empty in case of no upgrade, the servers will start with an empty database. In such a case, shutdown the ZooKeeper servers, remove the version-2 directory (remember this will lead to loss of updates after you started 3.0.) and then start the upgrade procedure.
-
If the upgrade fails while trying to rename files into the version-1 directory, you should try and move all the files under <dataDir>/version-1 and <dataLogDir>/version-1 to <dataDir> and <dataLogDir> respectively. Then try upgrade again.
-
If you do not wish to run with ZooKeeper 3.0 and prefer to run with ZooKeeper 2.0 and have already upgraded - you can run ZooKeeper 2 with the <dataDir> and <dataLogDir> directories changed to <dataDir>/version-1 and <dataLogDir>/version-1. Remember that you will lose all the updates that you made after the upgrade.
Migrating Server Configuration
There is a significant change to the ZooKeeper server configuration file.
The default election algorithm, specified by the electionAlg configuration attribute, has changed from a default of 0 to a default of 3. See Cluster Options section of the administrators guide, specifically the electionAlg and server.X properties.
You will either need to explicitly set electionAlg to it's previous default value of 0 or change your server.X options to include the leader election port.
Changes Since ZooKeeper 2.2.1
Version 2.2.1 code, documentation, binaries, etc... are still accessible on SourceForge
| Issue | Notes |
|---|---|
| ZOOKEEPER-43 | Server side of auto reset watches. |
| ZOOKEEPER-132 | Create Enum to replace CreateFlag in ZooKepper.create method |
| ZOOKEEPER-139 | Create Enums for WatcherEvent's KeeperState and EventType |
| ZOOKEEPER-18 | keeper state inconsistency |
| ZOOKEEPER-38 | headers in log/snap files |
| ZOOKEEPER-8 | Stat enchaned to include num of children and size |
| ZOOKEEPER-6 | List of problem identifiers in zookeeper.h |
| ZOOKEEPER-7 | Use enums rather than ints for types and state |
| ZOOKEEPER-27 | Unique DB identifiers for servers and clients |
| ZOOKEEPER-32 | CRCs for ZooKeeper data |
| ZOOKEEPER-33 | Better ACL management |
| ZOOKEEPER-203 | fix datadir typo in releasenotes |
| ZOOKEEPER-145 | write detailed release notes for users migrating from 2.x to 3.0 |
| ZOOKEEPER-23 | Auto reset of watches on reconnect |
| ZOOKEEPER-191 | forrest docs for upgrade. |
| ZOOKEEPER-201 | validate magic number when reading snapshot and transaction logs |
| ZOOKEEPER-200 | the magic number for snapshot and log must be different |
| ZOOKEEPER-199 | fix log messages in persistence code |
| ZOOKEEPER-197 | create checksums for snapshots |
| ZOOKEEPER-198 | apache license header missing from FollowerSyncRequest.java |
| ZOOKEEPER-5 | Upgrade Feature in Zookeeper server. |
| ZOOKEEPER-194 | Fix terminology in zookeeperAdmin.xml |
| ZOOKEEPER-151 | Document change to server configuration |
| ZOOKEEPER-193 | update java example doc to compile with latest zookeeper |
| ZOOKEEPER-187 | CreateMode api docs missing |
| ZOOKEEPER-186 | add new "releasenotes.xml" to forrest documentation |
| ZOOKEEPER-190 | Reorg links to docs and navs to docs into related sections |
| ZOOKEEPER-189 | forrest build not validated xml of input documents |
| ZOOKEEPER-188 | Check that election port is present for all servers |
| ZOOKEEPER-185 | Improved version of FLETest |
| ZOOKEEPER-184 | tests: An explicit include derective is needed for the usage of memcpy functions |
| ZOOKEEPER-183 | Array subscript is above array bounds in od_completion, src/cli.c. |
| ZOOKEEPER-182 | zookeeper_init accepts empty host-port string and returns valid pointer to zhandle_t. |
| ZOOKEEPER-17 | zookeeper_init doc needs clarification |
| ZOOKEEPER-181 | Some Source Forge Documents did not get moved over: javaExample, zookeeperTutorial, zookeeperInternals |
| ZOOKEEPER-180 | Placeholder sections needed in document for new topics that the umbrella jira discusses |
| ZOOKEEPER-179 | Programmer's Guide "Basic Operations" section is missing content |
| ZOOKEEPER-178 | FLE test. |
| ZOOKEEPER-159 | Cover two corner cases of leader election |
| ZOOKEEPER-156 | update programmer guide with acl details from old wiki page |
| ZOOKEEPER-154 | reliability graph diagram in overview doc needs context |
| ZOOKEEPER-157 | Peer can't find existing leader |
| ZOOKEEPER-155 | improve "the zookeeper project" section of overview doc |
| ZOOKEEPER-140 | Deadlock in QuorumCnxManager |
| ZOOKEEPER-147 | This is version of the documents with most of the [tbd...] scrubbed out |
| ZOOKEEPER-150 | zookeeper build broken |
| ZOOKEEPER-136 | sync causes hang in all followers of quorum. |
| ZOOKEEPER-134 | findbugs cleanup |
| ZOOKEEPER-133 | hudson tests failing intermittently |
| ZOOKEEPER-144 | add tostring support for watcher event, and enums for event type/state |
| ZOOKEEPER-21 | Improve zk ctor/watcher |
| ZOOKEEPER-142 | Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode |
| ZOOKEEPER-93 | Create Documentation for Zookeeper |
| ZOOKEEPER-117 | threading issues in Leader election |
| ZOOKEEPER-137 | client watcher objects can lose events |
| ZOOKEEPER-131 | Old leader election can elect a dead leader over and over again |
| ZOOKEEPER-130 | update build.xml to support apache release process |
| ZOOKEEPER-118 | findbugs flagged switch statement in followerrequestprocessor.run |
| ZOOKEEPER-115 | Potential NPE in QuorumCnxManager |
| ZOOKEEPER-114 | cleanup ugly event messages in zookeeper client |
| ZOOKEEPER-112 | src/java/main ZooKeeper.java has test code embedded into it. |
| ZOOKEEPER-39 | Use Watcher objects rather than boolean on read operations. |
| ZOOKEEPER-97 | supports optional output directory in code generator. |
| ZOOKEEPER-101 | Integrate ZooKeeper with "violations" feature on hudson |
| ZOOKEEPER-105 | Catch Zookeeper exceptions and print on the stderr. |
| ZOOKEEPER-42 | Change Leader Election to fast tcp. |
| ZOOKEEPER-48 | auth_id now handled correctly when no auth ids present |
| ZOOKEEPER-44 | Create sequence flag children with prefixes of 0's so that they can be lexicographically sorted. |
| ZOOKEEPER-108 | Fix sync operation reordering on a Quorum. |
| ZOOKEEPER-25 | Fuse module for Zookeeper. |
| ZOOKEEPER-58 | Race condition on ClientCnxn.java |
| ZOOKEEPER-56 | Add clover support to build.xml. |
| ZOOKEEPER-75 | register the ZooKeeper mailing lists with nabble.com |
| ZOOKEEPER-54 | remove sleeps in the tests. |
| ZOOKEEPER-55 | build.xml failes to retrieve a release number from SVN and the ant target "dist" fails |
| ZOOKEEPER-89 | invoke WhenOwnerListener.whenNotOwner when the ZK connection fails |
| ZOOKEEPER-90 | invoke WhenOwnerListener.whenNotOwner when the ZK session expires and the znode is the leader |
| ZOOKEEPER-82 | Make the ZooKeeperServer more DI friendly. |
| ZOOKEEPER-110 | Build script relies on svnant, which is not compatible with subversion 1.5 working copies |
| ZOOKEEPER-111 | Significant cleanup of existing tests. |
| ZOOKEEPER-122 | Fix NPE in jute's Utils.toCSVString. |
| ZOOKEEPER-123 | Fix the wrong class is specified for the logger. |
| ZOOKEEPER-2 | Fix synchronization issues in QuorumPeer and FastLeader election. |
| ZOOKEEPER-125 | Remove unwanted class declaration in FastLeaderElection. |
| ZOOKEEPER-61 | Address in client/server test cases. |
| ZOOKEEPER-75 | cleanup the library directory |
| ZOOKEEPER-109 | cleanup of NPE and Resource issue nits found by static analysis |
| ZOOKEEPER-76 | Commit 677109 removed the cobertura library, but not the build targets. |
| ZOOKEEPER-63 | Race condition in client close |
| ZOOKEEPER-70 | Add skeleton forrest doc structure for ZooKeeper |
| ZOOKEEPER-79 | Document jacob's leader election on the wiki recipes page |
| ZOOKEEPER-73 | Move ZK wiki from SourceForge to Apache |
| ZOOKEEPER-72 | Initial creation/setup of ZooKeeper ASF site. |
| ZOOKEEPER-71 | Determine what to do re ZooKeeper Changelog |
| ZOOKEEPER-68 | parseACLs in ZooKeeper.java fails to parse elements of ACL, should be lastIndexOf rather than IndexOf |
| ZOOKEEPER-130 | update build.xml to support apache release process. |
| ZOOKEEPER-131 | Fix Old leader election can elect a dead leader over and over again. |
| ZOOKEEPER-137 | client watcher objects can lose events |
| ZOOKEEPER-117 | threading issues in Leader election |
| ZOOKEEPER-128 | test coverage on async client operations needs to be improved |
| ZOOKEEPER-127 | Use of non-standard election ports in config breaks services |
| ZOOKEEPER-53 | tests failing on solaris. |
| ZOOKEEPER-172 | FLE Test |
| ZOOKEEPER-41 | Sample startup script |
| ZOOKEEPER-33 | Better ACL management |
| ZOOKEEPER-49 | SetACL does not work |
| ZOOKEEPER-20 | Child watches are not triggered when the node is deleted |
| ZOOKEEPER-15 | handle failure better in build.xml:test |
| ZOOKEEPER-11 | ArrayList is used instead of List |
| ZOOKEEPER-45 | Restructure the SVN repository after initial import |
| ZOOKEEPER-1 | Initial ZooKeeper code contribution from Yahoo! |


IFeedContentProvider interface.
IFeedContentProvider interface must be implemented by a feed class who provides feed content.
Located in /Web/Services/TFeedService.php (line 120)
Sets the content type of the feed content to be sent.
Some examples are: RSS 1.0 feed: application/rdf+xml RSS 2.0 feed: application/rss+xml or application/xml or text/xml ATOM feed: application/atom+xml
Initializes the feed content provider.
This method is invoked (before getFeedContent) when the feed provider is requested by a user.
Documentation generated on Fri, 03 Jun 2011 16:24:21 +0200 by phpDocumentor 1.3.0RC4


This is the homepage, here users can add an image & demo the audio (the audio works. ↑try it ↑)
Example: Image 1
This is what the homepage usually looks like when someone uplaods an image
Example: Image 2
This is the final product Here users will listen to the text shown above


Name is required.
Adress is required.
A valid zipcode is required.
City is required.
A valid website url is required.
A valid email adress is required.
A valid phone number is required.


Welcome to Astro-Visualization! This repository/website started as a hack project during AstroHackWeek2020. In here you can find several examples of pretty astronomical plots, and best of all, their source code! If you see a plot you like, just copy the source code and modify it to your convenience. Want to contribute with a pretty plot of your own? Check our Github repository! Feel free to share our website with the rest of the community as well! If you make use of this website in your work, please add us to your Acknowledgements: “This work has made used of the Astro-Visualization website”.
Do you have a pretty plot you would like to share with the rest of the astronomy community? Wonderful! Follow the instructions on our Github repository.


As most developers jokingly put it, “Hello World!” Since most internet attention spans last less than 30 seconds, I’ll try to keep this brief.
I hail from the greater New York area, spending time residing upstate in the Hudson Valley, south in New Jersey and further out in Philadelphia. I like to put down my hometown just as the “Northeast.”
Like 20 something year olds, I hold a wealth of niche interests. I enjoy maintaining a balance of technical, concrete skills along with creative ones.
For years, I studied engineering and ended up in a data analysis position at Verizon after finishing college. On the side though, I enjoy a fulfilling life as an amateur musician, making new creations when I can find the time. If you’d like to hear a sample of my creations, feel free to listen to the embedded Soundcloud player to the right.
Because of this creative/technical balance, I felt studying web development would lead me into a happier career. I believe that when the scientific side meets with the free-thinking creative side, truly great things can occur.


The Cutting Edge
|
|
| G'day Developers! |
|
Collation is a great feature for international companies. However, if you are
not consciously using it then you should have all databases using a consistent
collation.
Collation is the combination of language and sort orders. Back
in SQL Server 7, you could only define the collation at the server level and,
once it was set, you could not change it without rebuilding the master
database. SQL Server 2000 added the ability to have 'Column Level Collation'
which allows you to set it at the database or column level. It is ideal for
those who only want the column name 'FirstName' to be represented in accent
insensitive sort order. If you are not taking notice of collation, one of the
side effects can be that you end up with many different collations on many
different databases .
More Rules to Better SQL Server Databases.
|
|
Cheers until next time,
Adam
SSW Chief Architect and Microsoft Regional Director, Australia
Got a comment for Adam? Email
Adam
|
|
SSW Tech Breakfast Special Offers
|
|
Refer someone new to our Tech Breakfast sessions and you can come along for
free! There are two sessions you can choose from; From Access to the
Enterprise on the 9th of November and eXtreme Programming for
.NET Developers on the 3rd of December. These sessions are
presented by Microsoft Regional Director
Adam Cogan.
You can
register online now or contact Rebecca either via
696e666f72407373772e636f6d2e6175
or on (02) 9953 3000.
|
|
Sydney .NET User Group - The best place to learn
.NET for free in Sydney *(2 weeks late)*
|
|
|
Sydney
.NET User Group 3, November 2004
|
|
This months User Group has been postponed by 2 weeks as Adam is climbing the
Western Breach of Mount Kilimanjaro in Tanzania, Africa - lucky guy!
The content for the User Group will be emailed to you at a later date.
|
|
Wednesday 3rd November. 6:00 pm at Microsoft, 1 Epping Road North Ryde
>See You There!! |
Sorry I can't make it
|
|
Extreme Programming Article - Simon Sharwood
|
|
|
eXtreme Programming has emerged as a grassroots solution to software
development cost blowouts. Simon Sharwood reports on a process thats turning
the developing world upside down.
"In October 2002, NSW treasurer Michael Egan asked his auditor-general to
investigate a software development project at publicly-owned Sydney Water,
Australias largest water services provider."
|
|
SSW .NET Toolkit
|
|
|
Develop
Applications More Efficiently with the SSW .NET Toolkit
The SSW .NET Toolkit is an example of a distributed multi-layer
application based on the Microsoft Northwind database. Designed by Developers
for Developers, the real-world source can be used as a model and basis for
custom-designed applications perfect for small and medium enterprise (SME)
applications. Microsoft's examples like
Duwamish and
IBuySpy
are code intensive and marketed towards architects, not developers. The SSW
.NET Toolkit delivers more functionality using less code.
The .NET Toolkit contains two parts. Part A demonstrates how to
use extended providers for validation, and how to implement searching through
records in a database. Part B shows how to implement SSW Exception Reporter an
extended version of the Configuration Block. More on
SSW .NET Toolkit
|
Tips
|
|
|
I want to generate a script
that updates a column on every table in my database. How do I do this? -
answered by David Klein.
|
|
|
How do I get the type name
of an object using COM Interop? I just get System.__ComObject returned when
using .gettype() - answered by David Klein.
|


Class Auth_Container_ADOdb
Storage driver for fetching login data from a database using ADOdb-PHP.
This storage driver can use all databases which are supported by the ADBdb DB
abstraction layer to fetch login data. See http://php.weblogs.com/adodb for
information on ADOdb. NOTE: The ADOdb directory MUST be in your PHP
include_path!
-
Auth_Container
-
Auth_Container_ADOdb
Methods summary
public
object
|
#
Auth_Container_ADOdb( string $dsn )
Constructor of the container class
Constructor of the container class
Initate connection to the database via PEAR::ADOdb
Parameters
- $dsn
string Connection data or DB object
Returns
object Returns an error object if something went wrong
|
public
mixed
|
#
_connect( string $dsn )
Connect to database by using the given DSN string
Connect to database by using the given DSN string
Parameters
Returns
mixed Object on error, otherwise bool
|
public
mixed
|
#
_prepare( )
Prepare database connection
Prepare database connection
This function checks if we have already opened a connection to the database.
If that's not the case, a new connection is opened.
Returns
mixed True or a DB error object.
|
public
mixed
|
#
query( string $query )
Prepare query to the database
Prepare query to the database
This function checks if we have already opened a connection to the database.
If that's not the case, a new connection is opened. After that the query is
passed to the database.
Parameters
- $query
string Query string
Returns
mixed a DB_result object or DB_OK on success, a DB or PEAR error on failure
|
public
|
|
public
|
#
_parseOptions( array $array )
Parse options passed to the container class
Parse options passed to the container class
Parameters
|
public
mixed
|
#
fetchData( string $username, string $password )
Get user information from database
Get user information from database
This function uses the given username to fetch the corresponding login data
from the database table. If an account that matches the passed username and
password is found, the function returns true. Otherwise it returns false.
Parameters
- $username
string Username
- $password
string Password
Returns
mixed Error object or boolean
|
public
|
|
public
mixed
|
#
addUser( string $username, string $password, mixed $additional = "" )
Add user to the storage container
Add user to the storage container
Parameters
- $username
string Username
- $password
string Password
- $additional
mixed Additional information that are stored in the DB
Returns
mixed True on success, otherwise error object
|
public
mixed
|
#
removeUser( string $username )
Remove user from the storage container
Remove user from the storage container
Parameters
Returns
mixed True on success, otherwise error object
|
Properties summary
public
array
|
$options
|
array() |
#
Additional options for the storage container
Additional options for the storage container
|
public
object
|
$db
|
null |
|
public
string
|
$dsn
|
'' |
|
public
string
|
$activeUser
|
'' |
#
User that is currently selected from the DB.
User that is currently selected from the DB.
|


Aston Villa to swoop for Said Benrahma in January?
Aston Villa are reportedly considering reigniting their interest in Brentford attacker Said Benrahma when the January transfer window opens for business.
by Matt LawDean Smith's side were strongly linked with a move for the Algeria international during the summer and allegedly failed with a number of offers ahead of the 2019-20 campaign.
Benrahma scored 11 times in 45 outings for Brentford last season while he has contributed two goals and two assists in 14 Championship outings this term.
According to Sky Sports News, despite failing to secure his services over the summer, Villa remain interested in a swoop for the 24-year-old ahead of the January transfer window.
The report claims that Brentford still value the attacker in the region of £20m, though, which is a figure that Smith's side were not prepared to pay over the summer.
Villa will resume their Premier League campaign at home to Newcastle United on Monday night.
body check tags ::


{% from 'shared/document_list.html' import document_list with context %}
{% from 'shared/link_list.html' import link_list with context %}
{% from "shared/trumbowyg.html" import trumbowyg %}
{{ trumbowyg(field=design.notes, parent=design, api_url="/design/update", field_name='notes', label='NOTES',
placeholder="Additional design information for helpful reference or that's not covered in elsewhere in the record") }}


Self-Awareness and Self-Confidence
Q: What is the relationship between mindfulness and self awareness?
A: They are basically the same thing. It's like observe your emotion objectively.
Q: Try at least one of the self awareness practices from the chapter (Body Scan, Journaling). What was your experience of it? How did you feel?
A: Tried body scan, I'm able to detect the current status of each part of my body. And when the emotion bring in, I can notice the physical response of my body.
Q: What did you take away from the "My Emotions are Not Me" section?
A: Transform 'I feel angry' to 'I experience anger in my body' is a great solution to control your emotion. But don't go too far, I think it's also a way to get rid of your human side. So balance is important.


The one on one structure
When I first went headfirst into the EM role I must admit, I was winging it. I went from a tech lead position, to an organically found management position, then when the title flipped it suddenly the game changed. Expectations of conducting 1:1’s were not part of my duties. No one mentioned the purpose of a 1:1, let alone what you do in a 1:1. I have to admit, it was mainly just a sync up on what people were working on. I didn’t like it, it felt… awkward.
The awkwardness got to a point where 1:1’s would start to slip off the calendar. It would only be until something had to be said that we would have a “1:1”. Where did that leave me? Well, in a place where a 1:1 would be a thing to dread. I was in a tight space, little mentorship and no pathway out. I reached out to a friend who put me onto the book The Effective Manager.
The book talks about many things. One thing I’ll delve into now from the book is the structure of a 1:1. It helped me effectively use the time in my 1:1’s. By following the structure it made me, and I hope my direct, look forward to 1:1’s.
You talk
A one on one isn’t just you talking to the direct. See a critical component in the employee to manager relationship, is, as you guessed it, trust. You need to build trust, be constantly building it. Too often managers go into one on ones and use it as their venting session, or to just talk about something the direct did wrong. Why would a direct open up to you and confide in you when either a) It’s just you talking or b) you just scold them for something they might of done inadequately. So this first 10mins should be left to your direct to talk.
Open up the 1:1 with something like:
- Tell me what’s going on in your world?
- How’s your week been?
- What are you up to these days?
- How’d you go this week?
- How are you?
Leave it open ended, because really, this 1:1 is mainly about them. If they use the entire time up to speak, then so be it. It’s a great way to build the trust, by showing that this is a safe environment to confide in. Of course try and converse with the individual, prod for more elaboration or provide some additional insight, but this time isn’t yours, it’s all about them.
Now I talk
This part is you to provide insight into what you’re up to. Share your perspective on how the team or individual is going. Provide some background story on the week and share some details that may smooth over some uncertainty. It could be a simple status update as:
- That outage this week was because of the oracle slave server hanging. That caused an outage downstream and we got hit with a deluge of complaints as we’re the client. I think we might have a post-mortem coming up for it.
- I’ve been trying to get some developers from other teams to come over and talk about MVVM with us.
- We’re doing well with recruitment, I want to thank you for your involvement with that.
- Let’s talk about James leaving, how do you think the team is? I’m thinking perhaps we get an API engineer in as a replacement to better purpose the role for a gap in our team skills.
This is another 10mins worth of just you talking. Don’t be detracted if this turns into a conversation and don’t block your direct out. If they want more clarification or details into what you’re discussing, that is a data point in itself. Give them the data and use that to calculate whether or not to open the discussion up wider to the rest of the team.
The future
The last whatever minutes you have are now to discuss goals. Short term and long term goals. Discuss what the next week looks like. Opportunities ahead and how you see that the direct can capitalize on any that are at their disposal. Discuss some areas of weakness you feel that they should concentrate and focus on in the next week. Revisit larger goals and discuss their progress. Keep the eye on the prize.
Sure discussions of promotions may come up in these 1:1’s when you discuss the future. I will do a separate post on how to discuss promotions. For now feel free to discuss that in the realm of long term goals. If that is the most pertinent goal then so be it, but relate it back to pressing matters in the short and long term. Relate it back to the goals you have hopefully setup with them in the past 3 months.
The implementation details
Setup your 1:1’s for a tight feedback loop. Keep your ability to calibrate tight and in-turn with the world that the individual is operating in. Like goals, keep your influence as agile as possible. For this reason I hold my 1:1’s weekly. They’re added to both my direct’s and my own calendars and repeat weekly. I check in with my direct before scheduling to try find a time that works for us both. Once its on the calendar it signifies to the individual that their time is important to me and that I am not above dedicating 30mins a week to them, because I’m not. It’s my job and this is a tool to do my job.
So 30mins for:
- 10 - 30mins for them
- 10mins for me (if there is time)
- 10mins for the future (if there is time)
The Effective Manager
Now there may be push back if you’ve held off for so long to get 1:1’s onto the calendar. “Not another meeting”! is something you may hear. Perhaps you’ve used 1:1’s in the past only for negative feedback and your direct is rejecting the fact they need more of the past. Try and rebuild the trust and run them through the proposed feedback.
I highly recommend reading The Effective Manager. They go into much more detail on what to say in 1:1’s when you’re just starting them up for the first time. How to prove their value, and what to do when a direct flat out says no. Please read it. It seriously changed my approach to management and gave me the confidence needed. It more importantly gave me back one of the most effective management tools in my toolkit.
Post by: RS


{{- block "_head" .}}
Imaginative Go
{{- end}} {{- block "_after_body" .}}


Processing
Processing Processing is done inside the computer in an area called central processing unit (CPU). Processing is the conversion of input to output.


{% extends 'all/base.html'%} {% block content %} Welcome, search your selected images based on the following limited categories: Parks to visit, beaches and places to visit. {% for galleryImage in galleryImages %} {{galleryImage.title}} IMAGE CATEGORY:{{galleryImage.category}} ABOUT THE IMAGE:{{galleryImage.imageDescription}} LOCATION WHERE TAKEN: {{galleryImage.image_location}} UPLOADED ON: {{galleryImage.date_uploaded}} {% endfor %} {% endblock %}
Welcome, search your selected images based on the following limited categories: Parks to visit, beaches and places to visit.
IMAGE CATEGORY:{{galleryImage.category}}
ABOUT THE IMAGE:{{galleryImage.imageDescription}}
LOCATION WHERE TAKEN: {{galleryImage.image_location}}
UPLOADED ON: {{galleryImage.date_uploaded}}


tty
`Prev `__
T
`Next `__
--------------
**tty**: /T·T·Y/, /tit´ee/, n.
The latter pronunciation was primarily ITS, but some Unix people say it
this way as well; this pronunciation is *not* considered to have sexual
undertones.
1. A terminal of the teletype variety, characterized by a noisy
mechanical printer, a very limited character set, and poor print
quality. Usage: antiquated (like the TTYs themselves). See also
`*bit-paired keyboard* <../B/bit-paired-keyboard.html>`__.
2. [especially Unix] Any terminal at all; sometimes used to refer to the
particular terminal controlling a given job.
3. [Unix] Any serial port, whether or not the device connected to it is
a terminal; so called because under Unix such devices have names of the
form tty\*. Ambiguity between senses 2 and 3 is common but seldom
bothersome.
--------------
+--------------------------------+----------------------------+-------------------------+
| `Prev `__ | `Up <../T.html>`__ | `Next `__ |
+--------------------------------+----------------------------+-------------------------+
| true-hacker | `Home <../index.html>`__ | tube |
+--------------------------------+----------------------------+-------------------------+


XRDB(1) XRDB(1) NAME xrdb - X server resource database utility SYNOPSIS xrdb [-option ...] [filename] DESCRIPTION Xrdb is used to get or set the contents of the RESOURCE_MANAGER property on the root window of screen 0, or the SCREEN_RESOURCES property on the root window of any or all screens, or everything combined. You would normally run this program from your X startup file. Most X clients use the RESOURCE_MANAGER and SCREEN_RESOURCES properties to get user preferences about color, fonts, and so on for applications. Having this information in the server (where it is available to all clients) instead of on disk, solves the problem in previous versions of X that required you to maintain defaults files on every machine that you might use. It also allows for dynamic changing of defaults without edit‐ ing files. The RESOURCE_MANAGER property is used for resources that apply to all screens of the display. The SCREEN_RESOURCES property on each screen specifies additional (or overriding) resources to be used for that screen. (When there is only one screen, SCREEN_RESOURCES is normally not used, all resources are just placed in the RESOURCE_MANAGER property.) The file specified by filename (or the contents from standard input if - or no filename is given) is optionally passed through the C preprocessor with the following symbols defined, based on the capabilities of the server being used: SERVERHOST=hostname the hostname portion of the display to which you are connected. SRVR_name the SERVERHOST hostname string turned into a legal identifier. For example, "my-dpy.lcs.mit.edu" becomes SRVR_my_dpy_lcs_mit_edu. HOST=hostname the same as SERVERHOST. DISPLAY_NUM=num the number of the display on the server host. CLIENTHOST=hostname the name of the host on which xrdb is running. CLNT_name the CLIENTHOST hostname string turned into a legal identifier. For example, "expo.lcs.mit.edu" becomes CLNT_expo_lcs_mit_edu. RELEASE=num the vendor release number for the server. The interpretation of this number will vary depending on VENDOR. REVISION=num the X protocol minor version supported by this server (currently 0). VERSION=num the X protocol major version supported by this server (should always be 11). VENDOR="vendor" a string literal specifying the vendor of the server. VNDR_name the VENDOR name string turned into a legal identifier. For exam‐ ple, "MIT X Consortium" becomes VNDR_MIT_X_Consortium. EXT_name A symbol is defined for each protocol extension supported by the server. Each extension string name is turned into a legal iden‐ tifier. For example, "X3D-PEX" becomes EXT_X3D_PEX. NUM_SCREENS=num the total number of screens. SCREEN_NUM=num the number of the current screen (from zero). BITS_PER_RGB=num the number of significant bits in an RGB color specification. This is the log base 2 of the number of distinct shades of each primary that the hardware can generate. Note that it usually is not related to PLANES. CLASS=visualclass one of StaticGray, GrayScale, StaticColor, PseudoColor, True‐ Color, DirectColor. This is the visual class of the root window. CLASS_visualclass=visualid the visual class of the root window in a form you can #ifdef on. The value is the numeric id of the visual. COLOR defined only if CLASS is one of StaticColor, PseudoColor, True‐ Color, or DirectColor. CLASS_visualclass_depth=num A symbol is defined for each visual supported for the screen. The symbol includes the class of the visual and its depth; the value is the numeric id of the visual. (If more than one visual has the same class and depth, the numeric id of the first one reported by the server is used.) HEIGHT=num the height of the root window in pixels. WIDTH=num the width of the root window in pixels. PLANES=num the number of bit planes (the depth) of the root window. X_RESOLUTION=num the x resolution of the screen in pixels per meter. Y_RESOLUTION=num the y resolution of the screen in pixels per meter. SRVR_name, CLNT_name, VNDR_name, and EXT_name identifiers are formed by changing all characters other than letters and digits into underscores (_). Lines that begin with an exclamation mark (!) are ignored and may be used as comments. Note that since xrdb can read from standard input, it can be used to the change the contents of properties directly from a terminal or from a shell script. OPTIONS xrdb program accepts the following options: -help This option (or any unsupported option) will cause a brief description of the allowable options and parameters to be printed. -display display This option specifies the X server to be used; see X(7). It also specifies the screen to use for the -screen option, and it speci‐ fies the screen from which preprocessor symbols are derived for the -global option. -all This option indicates that operation should be performed on the screen-independent resource property (RESOURCE_MANAGER), as well as the screen-specific property (SCREEN_RESOURCES) on every screen of the display. For example, when used in conjunction with -query, the contents of all properties are output. For -load, -override and -merge, the input file is processed once for each screen. The resources which occur in common in the output for every screen are collected, and these are applied as the screen-independent resources. The remaining resources are applied for each individual per-screen property. This the default mode of operation. -global This option indicates that the operation should only be performed on the screen-independent RESOURCE_MANAGER property. -screen This option indicates that the operation should only be performed on the SCREEN_RESOURCES property of the default screen of the display. -screens This option indicates that the operation should be performed on the SCREEN_RESOURCES property of each screen of the display. For -load, -override and -merge, the input file is processed for each screen. -n This option indicates that changes to the specified properties (when used with -load, -override or -merge) or to the resource file (when used with -edit) should be shown on the standard out‐ put, but should not be performed. -quiet This option indicates that warning about duplicate entries should not be displayed. -cpp filename This option specifies the pathname of the C preprocessor program to be used. Although xrdb was designed to use CPP, any program that acts as a filter and accepts the -D, -I, and -U options may be used. -nocpp This option indicates that xrdb should not run the input file through a preprocessor before loading it into properties. -symbols This option indicates that the symbols that are defined for the preprocessor should be printed onto the standard output. -query This option indicates that the current contents of the specified properties should be printed onto the standard output. Note that since preprocessor commands in the input resource file are part of the input file, not part of the property, they won't appear in the output from this option. The -edit option can be used to merge the contents of properties back into the input resource file without damaging preprocessor commands. -load This option indicates that the input should be loaded as the new value of the specified properties, replacing whatever was there (i.e. the old contents are removed). This is the default action. -override This option indicates that the input should be added to, instead of replacing, the current contents of the specified properties. New entries override previous entries. -merge This option indicates that the input should be merged and lexico‐ graphically sorted with, instead of replacing, the current con‐ tents of the specified properties. -remove This option indicates that the specified properties should be removed from the server. -retain This option indicates that the server should be instructed not to reset if xrdb is the first client. This should never be neces‐ sary under normal conditions, since xdm and xinit always act as the first client. -edit filename This option indicates that the contents of the specified proper‐ ties should be edited into the given file, replacing any values already listed there. This allows you to put changes that you have made to your defaults back into your resource file, preserv‐ ing any comments or preprocessor lines. -backup string This option specifies a suffix to be appended to the filename used with -edit to generate a backup file. -Dname[=value] This option is passed through to the preprocessor and is used to define symbols for use with conditionals such as #ifdef. -Uname This option is passed through to the preprocessor and is used to remove any definitions of this symbol. -Idirectory This option is passed through to the preprocessor and is used to specify a directory to search for files that are referenced with #include. FILES Generalizes ~/.Xdefaults files. SEE ALSO X(7), appres(1), listres(1), Xlib Resource Manager documentation, Xt resource documentation ENVIRONMENT DISPLAY to figure out which display to use. BUGS The default for no arguments should be to query, not to overwrite, so that it is consistent with other programs. AUTHORS Bob Scheifler, Phil Karlton, rewritten from the original by Jim Gettys X Version 11 xrdb 1.0.9 XRDB(1)


WITNESS LIST Criminal Jurisprudence Committee March 27, 2001-2:00P HB 314 Registering, but not testifying: For: Granger, J.D. (Tarrant County DA's Office) Lewis, Bill (Mothers Against Drunk Driving) Wilkison, Charley (CLEAT) HB 451 For: Oeller, Carol (Harris County Office of Court Services (Pretrial)) HB 452 For: Hudson, David (Self and Tarrant County District Attorney's Office) Registering, but not testifying: For: Delgado, Joe (Bexar County Pretrial Services Office.) Gilmore, Morriss (Self) Mendez, Mark (Tarrant County Commissioners Court) Oeller, Carol (Harris County Office of Court Services (Pretrial)) HB 512 For: Sauer, Larry (Self and ACLU of Texas) Against: Hudson, David (Self and Tarrant County District Attorney's Office) HB 624 For: Ott, Judge Patricia (Justices of the Peace and Constables Assoc. of Texas, Inc. (J.P. Legislative Committee)) Registering, but not testifying: For: Freeman, Bill (Justice of the Peace and Constables Assn.) Williams, John H. (Justice of the Peace and Constables Assn. of Texas) HB 1102 For: Braddock, Kathy (Harris County DA's Office) Moore, Roger (Bail Agents of Allegheny Casualty Co., International Fidelity Insurance Co.) Welch, Tillmin (Self and Professional Bondsmen of Texas) Against: Davis, Don (Dallas County Commissioners Court) Hudson, David (Self and Tarrant County District Attorney's Office) Registering, but not testifying: For: Cornish, L. G., Jr. (Self) Long, Ronnie (Self) Mason, Marsha (Self) Schuder, Paul (Self) Walstad, Marjorie (Self) Watson, C. E. (Self) HB 1234 For: Boyles, Sherry (Texas Association Against Sexual Assault) Cramer, Christine Yang (Self) Hunter, Linda (Self and Hays-Caldwell Women's Center) Richardson, Roseann (Self) Wall, Matthew T. (Texas Hospital Association) Wolf, Laura (SAFEPLACE) Against: Eddleman, Sonja (Driscoll Children's Hospital CARE Team Doctor's Regional Medical Ctr. - SANE Program) Registering, but not testifying: For: Buchanan, Bree (Texas Council on Family Violence) Lawrence, Kevin F. (Texas Municipal Police Assn) HB 1250 For: Harrell, William (ACLU, NAACP, MALDEF, NCLR, LULAC) Riddering, Hannah (Self and Texas National Organization for Women) Against: DeLord, Ron (CLEAT) Ikner, Michael A. (Self and Arlington Police Department, Chief Theron Bowman, PhD) Registering, but not testifying: For: Green, Paul (Self) Against: Pynes, Jeff (Self) On: Elliston, Randy (DPS) HB 1336 For: Harrell, W. (ACLU, LULAC, MALDEF, NCLR, NAACP) Riddering, Hannah (Self and Texas National Organization for Women) Against: DeLord, Ron (CLEAT) Ikner, Michael A. (Self and Arlington Police Department, Chief Theron Bowman, PhD) Marticheck, Hans (Houston Police Officers' Union) Parnell, James (Dallas Police Association) Registering, but not testifying: For: Green, Paul (Self) Against: Andersen, Cris (San Antonio Police Officers' Association) Pynes, Jeff (Self) On: Elliston, Randy (DPS) HB 1618 On: Bailey Taylor, Shelia (State Office of Administrative Hearings) Blewett, Rebecca (Department of Public Safety - Driver License) HB 1643 For: Harrell, William (ACLU, NAACP, NCLR, LULAC, MALDEF) Riddering, Hannah (Self and Texas National Organization for Women) Against: DeLord, Ron (CLEAT) Registering, but not testifying: For: Green, Paul (Self) Hampton, Keith S. (Texas Criminal Defense Lawyers' Association) Lawrence, Kevin (Texas Municipal Police Association) Against: Andersen, Cris (San Antonio Police Officers' Association) Pynes, Jeff (Self) On: Elliston, Randy (DPS) HB 1848 For: Braddock, Kathleen (Harris County DA's Office) Carr, Sergeant Bruce (Harris County Sheriff Dept.) On: Hudson, David (Self and Tarrant County District Attorney's Office) Registering, but not testifying: For: Welch, Tillman G. (Self and Professional Bondsmen of Texas) HB 1976 Registering, but not testifying: For: DuBois, Doug (Texas Petroleum Marketers/Convenience Store Association) James, Dwain (American Collectors Association of Texas) Kidwell, Dudley (Self and CXS Investments, Inc.; CPA InstaChek) Reagan, Karen (Texas Retailers Association) On: Frazier, Edward James (U.S. Postal Service) HB 2030 Registering, but not testifying: Against: Sauer, Larry (Self and ACLU of Texas) HB 2097 On: DeBottis, Gina (Special Prosecution Unit) HB 2098 On: DeBottis, Gina (Special Prosecution Unit) Registering, but not testifying: Against: Sauer, Larry (Self and ACLU of Texas) HB 2192 For: Braddock, Kathy (Harris County DA's Office) Carr, Sergeant Bruce (Harris County Sheriff) Hudson, David (Self and Tarrant County District Attorney's Office) Moore, Roger (Bail Agents of Allegheny Casualty Co and International Fidelity Insurance Co) Walstad, Marjorie (Self) Welch, Tillmin G. (Self and The Professional Bondsmen of Texas) Registering, but not testifying: For: Cornish, Jr., L.G. (Self) Gilmore, Morriss (Self) Long, Ronnie (Self) Mason, Marsha (Self) Schuder, Paul (Self) Watson, C.E. (Self) Against: Kirk, Chris (Self and Sheriff's Association of Texas) HB 2351 For: Boone, Helen (Monternius & Anthron Smith) Brookins, Sr., Freddie W. (Self) Frazier, Jeff (Texas ACLU) Gardner, Gary O. (Self) Glenn, Bill (NAACP) Harrell, William (ACLU, NAACP, NCLR, LULAC) Henson, Scott (ACLU) Williams, Wanda J. (Cornelius A. Workman) Williamson, Van (Self and ACLU) Workman, Thomas Charles (Corrian Workman) Wyatt, Bradley (Self and 6 Criminal Defendants of Hearne, Robertson County, Texas) Against: Frasier, Margo (Sheriff's Association of Texas) Gottlob, John (Self and Texas Municipal Police Association) Marticheck, Hans (Houston Police Officers' Union) Noll, Chuck (Harris County District Attorney's Office) Registering, but not testifying: For: Brantley, Michelle (Michael Wells) Hampton, Keith S. (Texas Criminal Defense Lawyers' Association) McNeal, Laura (Darius McNeal) Owens, Eva (Texas Criminal Justice Reform Coalition) Ramos, Ph.D., Vincent (Texas LULAC) Against: Andersen, Cris (San Antonio Police Officers' Association) DeLord, Ron (CLEAT) Elkin, Bill (Houston Police Retired Officers Association) Granger, J.D. (Tarrant County DA's Office) Kirk, Chris (Self and Sheriff's Association of Texas) Liu, Livia (Dallas County DA's Office) Pynes, Jeff (Self) On: Johnston, Dennis (Resource Witness - Texas Parks and Wildlife) HB 2352 For: Glenn, Bill (NAACP) Harrell, William (ACLU, NAACP, NCLR, LULAC) Henson, Scott (Self) Williamson, Van (Self and ACLU) Against: Frasier, Margo (Sheriff's Association of Texas) Noll, Chuck (Harris County District Attorney's Office) Registering, but not testifying: For: del Llano, Ann (ACLU of Texas) Hampton, Keith S. (Texas Criminal Defense Lawyer's Association) Owens, Eva (Texas Criminal Justice Reform Coalition) Ramos, Ph.D., Vincent (Texas LULAC) Against: Granger, J.D. (Tarrant County DA's Office) Liu, Livia (Dallas County DA's Office) Murray-Kolb, Elizabeth (Self) Pynes, Jeff (Self) HB 2458 For: Gilstrap, Preston K. (National Black Police Association, Inc. - Southern Region) Glenn, Bill (Self and NAACP) Glover, Thomas L. (Texas Peace Officers Association, Dallas Chapter) Harrell, William (ACLU, NAACP, MALDEF, NCLR, LULAC) Ramos, Ph.D., Vincent (Texas LULAC) Riddering, Hannah (Self and Texas National Organization for Women) Whitley, Marlen D. (Self) Against: Marticheck, Hans (Houston Police Officers' Union) Parnell, James (Dallas Police Association) On: Begley, Kevin (Self and Harris County Area Police Chief's Association) DeLord, Ron (CLEAT) Ikner, Michael A. (Self and Arlington Police Department, Chief Theron Bowman, PhD) Jones, Claude (Texas Police Chiefs Association) Registering, but not testifying: For: Frasier, Margo (Sheriff's Association of Texas) Garcia, Dianne Hardy (Self) Green, Paul (Self) Kirk, Chris (Self and Sheriff's Association of Texas) Lawrence, Kevin (Texas Municipal Police Association) Lyons, Steve (Mayor Brown, Chief Bradford - City of Houston, Houston Police Dept.) Perry, Rosalind (Dallas Police Department, Chief Terrell Bolton) Against: Pynes, Jeff (Self) On: Elliston, Randy (Texas Dept. of Public Safety) HB 2517 For: Garrett, Tony (Self) Harrell, William (ACLU, NCLR, NAACP, LULAC) Sauer, Larry (Self and ACLU of Texas) Against: Gottlob, John W. (Self and Texas Municipal Police Association) Lawrence, Kevin (Texas Municipal Police Association) Registering, but not testifying: For: Ramos, Ph.D., Vincent (Texas LULAC) Riddering, Hannah (Self) Against: Andersen, Cris (San Antonio Police Officers' Association) DeLord, Ron (CLEAT) Elkin, Bill (Houston Police Retired Officers Association) HB 2676 Registering, but not testifying: For: Dahler, Erik T. (University Health System) Mendez, Mark (Tarrant County Commissioners Court) Swenson-Britt, Evelyn (San Antonio Safe Family Coalition) Thornton, MD, Joe E. (Self and San Antonio Safe Family Coalition) On: Ramsey, Michael (Texas Trial Lawyers Assoc.) HB 2856 For: Hudson, David (Self and Tarrant County District Attorney's Office) Mitchell, Seth (Bexar County Bail Bond Board, Bexar County Commissioners Court) On: Vannerson, Rodney (Self and Aaron Bail Bonds) Registering, but not testifying: For: Braddock, Kathleen (Harris Cty. D.A.'s Office) Carr, Bruce, Sergeant (Harris County Sherriff's Dept) Greer, Reagan (Bexar County Bail Bond Board) HB 3531 For: Vannerson, Rodney (Self and Aaron Bail Bonds) Against: Welch, Tillmin (Self and Professional Bondsmen of Texas) On: Braddock, Kathleen (Harris County D.A's Office) Carr, Bruce, Sergeant (Harris County Sherriff's Dept.) Hudson, David (Self and Tarrant County D. A.'s Office) Registering, but not testifying: For: Schwartz, A.R. Bob (Aaron Bail Bonds) SB 164 For: Ott, Judge Patricia (Justices of the Peace & Constables Assoc. of Texas, Inc. - J.P. Legislative Review Committee) Registering, but not testifying: For: Allison, Jim (County Judges and Commissioners Assoc. of Texas) Freeman, Bill (Justices of the Peace and Constables' Assn.) Lee, Donald (Texas Conference of Urban Counties) Williams, John H. (Justice of the Peace and Constable Assn of Texas) SB 515 For: Buchanan, Bree (Texas Council on Family Violence) Dahler, Erik T. (University Health System) Thornton, MD, Joe E. (Self and San Antonio Safe Family Coalition) Registering, but not testifying: For: Murray-Kolb, Elizabeth (Self) Swenson-Britt, Evelyn (San Antonio Safe Family Coalition) On: Ramsey, Michael R. (Texas Trial Lawyers Assoc.)


--- title: 'Basic Economics for Industrial Engineering' author: admin date: '2020-11-03' subtitle: '' summary: '' authors: [IJ] lastmod: '2020-11-03' featured: no image: caption: '' focal_point: '' preview_only: no projects: [] link-citations: yes biblio-style: apalike bibliography: [data/biblio_SABD.bib] \nocite: | @Greene2008,@Greene2009, @McFaddenTrain2000, @Train2009, @Agresti2013, ---
The lessons are organized as a master level class in economics. They are based on readings of textbooks (before the class) and in class presentations of students and discussions of case-studies with lecturers
This course presents the main tools for economics analysis useful for industrial engineers. The aim is to equip students with an understanding of both the demand and the offer side of a market, at the micro and the macro levels. Engineer’s world is facing complex situation, economist tools give a useful and complementary point of view to decide in complex situation. Economics analysis of markets and organizations is fundamental for industrial engineers who aim at participating to industry efficiency in term of value creation and profitability. Analyzing consumption behavior, production strategy and individual / organization interactions are the skills to be developed in this course.
The course is organized in three main topics: Economics of consumption and economics of production and markets analysis. These three parts are complemented with illustrations and case study of industrial engineering facing sustainable problems.
By participating and engaging in this course, students should be better able to analyze, model and solve (when possible) economic problem. Student should be able to propose synthetic survey of problem and to produce models of interactions between economic agents at stake in a problem. They are expected to conduct critical analysis of the hypotheses underlying models and of their results.
Students should be capable of presenting (oral and written) synthetic analysis of a problem, of demonstrating logical argument, of conducting individual and team work.
Introduction: Market, supply and demand
I. Economics of demand
a. Theory of the consumer
b. Consumption decision
II. Economics of production
a. Theory of the firm
b. Firm’s cost and profit
III. Markets Analysis
a. Market demand
b. Market supply
c. Welfare and market efficiency


Downtown Chicago is a series of rooftops, parking lots, roads, sidewalks, and other surfaces that cannot absorb water. When it rains, water flows across these hard surfaces and pours into the Chicago River, Lake Michigan, or city sewers that empty into both during heavy storms.
Stormwater runoff is one of the biggest culprits in lake and river pollution. When it flows into nearby waterways, runoff brings everything with it—from gasoline and trash on city streets to fertilizers and pesticides from lawns. These pollutants degrade water quality, raise water temperatures, and spur algae growth. As you might imagine, pollutants are also bad for fish. They clog gills, decrease resistance to disease, and suffocate eggs and newly hatched larvae. Bacteria carried in runoff can also make swimming in the lake a health risk. Stormwater runoff is behind most of the swim advisories and beach closures that plague the Great Lakes region each summer.
Concerns about stormwater pollution are on the rise as storms get bigger. During 2007-2010, the city’s sanitation district was forced to release 19 billion gallons of contaminated water into Lake Michigan, largely because of two monsoon-like storms that flooded the city in 2008 and 2010.


(Were you looking for PyLogo?)
Here's a little pattern I use quite often in web applications. Like a lot of patterns, it's not tied to any particular environment, or even to any specific application. There's a lot of these kinds of patterns out there that are specific to web applications (in addition to the standard patterns), but they don't seem to be well collected, defined, or named...
Frequently you will need to present out-of-context information to the user. For instance, in a webmail application when sending an email. A page saying "email successfully sent" isn't very interesting. Simply redirecting the user to the email index isn't very friendly either: it's important to give some feedback when a user performs a state-altering action. You want to predict what the user is likely to be most interested in, and direct them there, but you also want to put some notification about what just happened.
In whatever framework I am using (Webware, Zope, PHP), I'll usually add something like this to the template header (Webware here):
class SitePage(Page):... and calling writeMessage somewhere in the SitePage header. In Zope (somewhere in standard_template.pt):
....
def writeMessage(self):
if self.session().value('messages'):
self.write('
%s
' %
'
\n'.join(session.value('messages')))
self.session.setValue('messages', [])
def sendMessage(self, msg):
self.session().setValue('messages',
self.session().value('messages', []) + [msg])

<tal:block repeat="msg request/SESSION/message">

</tal:block>
<tal:block replace="python: request.SESSION.set('message', [])" />

If you haven't seen tal:block before, any tag prefixed with tal: gets removed from the final ZPT output, and any attributes of that tag are treated as TAL attributes. It saves a bit of typing, and anyone using ZPT can use all the help they can get to save typing.
People sometimes implement this in different ways. For instance, they simply invoke the template passing in a message variable.  A common navigation would be to arrive at the index page after sending, view an email, and then you want to go back to the index (using your back button). But you can't, because that index was the result of a POST, and probably isn't cachable. To reload it would resend the email. (In contrast: for the invalid case passing in a variable works well)
invalid_message = validate_email(request) # return None if valid
if invalid_message:
return sendmail_form(message=invalid_message)
sendmail(user.email, request.to, request.subject, request.body)
return mail_index(message='Email to %s sent successfully' %
request.to)
A solution to this is to redirect the user after sending their email. There's a few gotchas here relating to exactly what result code you use (there's a whole set of 3xx result codes), but that's another topic.
People sometimes start passing the messages in GET variables, e.g. redirect('/index?message=Email+sent+successfully'). This is terribly awkard, and it's not worth it to go down this path. Just use sessions, which are perfectly suited for this task. The GET variable is also flawed because that message is forever tied to that page, even after a reload, and even after the message is no longer timely.
Once you integrate this into your templates, you'll find yourself using these messages all the time. You can use it to add quick error messages, where before you might have been too lazy, or just have used some sort of generic "There was an error, hit the back button on your browser and correct it" page. You can notify the user of all sorts of little events which you might otherwise simply imply (e.g., "item deleted from cart", "edits saved", and so on). These updates give the user a clear idea of what they've done, what they need to do next (because they usually are in the middle of some longer set of tasks only they understand), and generally that their efforts are successful.
I very much liked the article.
I've started to use 300 codes in my applications so that I can preserve the Back button, and so that I can use one set of URLs for handling code, before redirecting to the correct page for fetching the results.
I'm sure that there are many other patterns for web development, one that comes to mind is a page which starts a long running search, then reloads itself until it completes (like most travel sites).
Aaron
You have to be careful in Zope when redirecting and using sessions.
If you raise the string 'Redirect' (capital R), it will cause Zope to abort the transaction and thus, abort the session write. There are cases when this is what you want - going along, coming across a problem after some data has already been written, and wanting to alert the user to this fact.
When you use the redirect method on Zope's RESPONSE object, the transaction will commit and the session data will be retained.
In cases like this, I've started using my own API calls such as 'returnWithMessage' which takes, among other parameters, a 'do_raise' argument. If 'do_raise' is true, the Redirect is raised as an error. If false, a regular redirect occurs. I've just added smarts into one of those calls to use a new 'page_messenger' service I wrote, inspired by your post (it's a bit cleaner than calling request.SESSION.set in a template, and has let me retain expections from current code that passes the message in via the request or a template call option).
it does not seems to be 'transactions-aware'. I mean if somebody will request very fast 2 pages, where 1st returning a error, then both of the pages will display same error. may be I am wrong, but it seems to be so.
personally I prefer to drive template from a script in this case, passing variables directly to template. its possible in php, webware, and Zope. Last year I am working with Zope, here is example in script:
errors=[]
if username=='':
errors.append('Please enter your username')
if password=='':
errors.append('Please enter your password')
if len(errors)>0:
request.set('errors', eroors)
return getattr(context,'login.html)(container,request)
so, in the page template I loop over the error list same way as described in the Ian example above.
its also more secure, since 3rd party do not see any particular data into URL GET requests, so both Session, and this example should be good.


I have used the ng-show and ng-hide directives to control the visibility of span elements in the last cell of each row of the table. This is a contrived example because I could achieve the same effect using an in-data binding, but I need an example that demonstrates a particular problem, as will become clear shortly. The ng-show and ng-hide directives control element visibility by adding and removing elements from a class called, confusingly, ng-hide. The ng-hide class applies a CSS style that sets the display property to none, removing the element from view. The difference between ng-show and ng-hide is that ng-show hides elements when its expression evaluates to false and ng-hide hides elements when its expression evaluates to true. This example also contains a check box that sets the complete property of the third to-do item. I added this to demonstrate that ng-show and ng-hide are, like all other directives, wired up to use data bindings and to demonstrate a limitation of the way that these directives work.
| # | Action | Done[With ngShow/Hide] | Done With ngIf | Mark Complete |
|---|---|---|---|---|
| {{$index + 1}} | {{item.action}} | (Incomplete) (Done) | (Incomplete) (Done) |


PROPHECY: Zimbabwe to bring back the US Dollar
by Mandla NdlovuThe government of Zimbabwe will re-introduce the United States dollar after an impending economic collapse, Pastor Ian Ndlovu of Divine Kingdom Baptist Ministries has prophesied.
Speaking during a prophetic service on Sunday, Ndlovu said God showed him two people running side by side. Each person was carrying a flag of their country.
The clergyman said the country has adopted economic policies that are going to lead to suffering of Zimbabweans and the outcome will be the adoption of the United States Dollar to work with the local currency.
The Bulawayo based Prophet who prophesied the introduction of the Zim dollar said there are difficult times coming ahead for the country but because of the prayers of the saints God had shortened the period.
Watch the full prophecy below:


Programming Your Home: Automate with Arduino, Android, and Your Computer (Pragmatic Programmers)
ISBN-13:<PHONE_NUMBER>906
ISBN-10:<PHONE_NUMBER>
Author: Mike Riley
Edition: 1
Binding: Paperback
Publisher: Pragmatic Bookshelf
Published: March 2012
List Price: $33.00
Best Rental Prices |
||||
|---|---|---|---|---|
| #1 |
Free shipping Ready to ship |
Notes |


| TOC |
|
This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 30, 2003.
Copyright (C) The Internet Society (2003). All Rights Reserved.
This memo presents a technique for using XML (Extensible Markup Language) and HTTP (HyperText Transport Protocol) to edit content.
| TOC |
| TOC |
RESTLog is an application level protocol for publishing, and editing web resources. RESTLog unifies many disparate publishing mechanisms into a single, simple, extensible protocol. That protocol at it's core is the HTTP transport of an XML payload. There are only two XML vocabularies for the XML payloads, the RSS 2.0 XML format, and the RESTLog Archive Format.
| TOC |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
| TOC |
As of the writing of this specification there many different and competing specifications for editing a web-site, in particular protocols for editing weblogs. Some of those protocols include the Blogger API, the metaWeblog API, and .
The various implementations of the different APIs are all slightly different and even different implementations of the same API have issues. For example, quoted from the RSD specification: [http://archipelago.phrasewise.com/rsd]
Blogger has "plant.blogger.com", "api/RPC2", and the blogID. The "Path to Service" is case sensitive. If a user enters "/api/rpc2" in their preferences they get an error in html, courtesy of Tomcat, that states "The requested resource (/rpc2) is not available.". The error message is subject to change in format. This same problem could apply to every case.
Moveable Type uses an endpoint of "mt/mt-xmlrpc.cgi", and the domain level of the URL depends on the installation. The site identifier is the blogID number.
Manila and Radio use "rpc2", case insensitive. Manila's domain level URL depends on the installation but it does provide the "sitename" through the ManilaRPC API. Whew! Radio has a consistent siteID (as of this writing).
Conversant has its own API plus support for basic Blogger API. It uses x|x|x identifier where the various flexible elements of Conversant are "x". Familiarity with Conversant is somewhat required. These elements are also required when specifiying a message, so you need a message "number" that looks like this x|x|x|123. Path to service is rpc2, and case insensitive (not tested).
As you can imagine, plenty of folks have struggled to get this information exactly correct for each case. Anything that helps automate the process or gives users up to date information on the specific service their employing would help mitigate this difficulty.
Also, the above specifications are all based on XML-RPC, which is an RPC style protocol that doesn't have any accomodations for extensibility. RESTLog is a 'document' style protocol, where extensibility is enabled via the use of xml namespaces.
| TOC |
This document covers the transfer of RSS 2.0 and RESTLog Archive formatted XML Payloads to accomplish the specific tasks of creating a new weblog post, and editing an old weblog post. This specification also covers the RESTLog Archive Format, but defers to @@XXXX@@, which specifies the RSS 2.0 format.
The protocol is defined primarily to allow remote editing of content on a weblog. The protocol is restricted to editing Entries in a weblog and does not cover editing templates, images, blogrolls, etc.
| TOC |
The entry point to start editing any weblog with the RESTLog API is a set of two URIs. These two URIs, which we shall refer to as "createURI", and "archiveURI", are used for, respectively, creating a new entry and getting a list of the all the Entries on a site. Each of these URI's support some of the HTTP verbs. For example, to create a new Entry, an RSS Item fragment is POSTed to "createURI". The minimum set of verbs that each interface must support is specified. Other HTTP verbs may be supported by each URI, this specification is only concerned with the verbs that must be present, and does not restrict the supported verbs to just those specified. Also note that the URL's used for RESTLog editing need bear no relation to the URIs used to access the HTML version of the content.
To get a list of Entries that already exist, the client does a GET on the "archiveURI". The list of Entries returned may be sufficient for the user, or further retrievals may be required to get the Entries the user is trying to manipulate, see the RESTLog Archive Format for more details, particularly the "more" element.
To create a new Entry on the server, the client POSTs an Entry to the "createURI". For example, if "createURI" were "http://example.com/news", the headers and body of the HTTP request to "example.org" would look like:
POST /news HTTP/1.1 Content-Type: text/xml <?xml version="1.0" encoding='iso-8859-1'?> <item> <title>My First Post</title><EMAIL_ADDRESS><description>This is the content of my first post. I will update this later to be more colorful.</description> </item>
This would create a new weblog Entry with title "My First Post".
| Create New Entry |
To begin the editing process, the URI of the RSS 2.0 item fragment representating the Entry must be found. The "archiveURI" is the place to begin that discovery process, by doing a GET on that URI. The content returned from that request will be an XML document in the RESTLog Archive Format.
For example, if "archiveURI" were "http://example.com/archive", the headers and body of the HTTP request to "example.org" would look like:
GET /archive HTTP/1.1 Accept: text/xml
This would return a list of some of the Entrys on the weblog.
| Retrieving the Archive |
The response from such a request would look like:
HTTP/1.1 200 OK Content-Type: text/xml <?xml version="1.0" encoding='iso-8859-1'?> <archives xmlns="http://www.purl.org/RESTLog/archives/1.0"> <group title="Last Ten Entries"> <res href="http://sample.org/news/100">Most Recent Post</res> <res href="http://sample.org/news/99">Yesterdays</res> . . . <res href="http://sample.org/news/91">Post From The Past</res> </group> <more href="http://sample.org/archive/all">All Items</more> <group title="By Category"> <more href="http://sample.org/archive/technology">Tech</more> <more href="http://sample.org/archive/books">Book Reviews</more> <more href="http://sample.org/archive/personal">Personal</more> </group> </archives>
This would return a list of some of the Entrys on the weblog.
| Response from the Archive |
Now the Entry that the user is looking for may not be in the list and they may need to go further into the archive. For example, if they knew they wanted to edit a Tech Entry that didn't appear in the "Last 10 Entries", then they would retrieve the Archive document that resides at "http://sample.org/archive/technology", which could contain some or all of the Entries in the Tech category. Note that the document at "http://sample.org/archive/technology" could also contain additional "more" elements.
The use of multiple GET's and traversing a web of links allows the server to present the Entries in multiple ways to the user. One alternative to this would be to present a single long list of Entries, maybe with attributes attached. That might be useful, but the document could get quite long and cumbersome to transfer. It also puts the effort onto the RESTLog client to sort, categorize and display the contents of the archive. In addition, adding new attributes would require an update to the client software to take advantage of the new information.
Another approach would be to allow a query syntax that allowed searching for Entries based on Date or keyword. The downfall of this approach is the same, in that the addition of new seach parameters requiring updating the client software.
Once a resource has been chosen the client can do a GET on that resource to get an RSS 2.0 formatted representation of that Entry. Editing of the content or other elements takes place, then the client PUT's the modified Entry back to the same URI to update the Entry.
Once a resource has been chosen the client can do a DELETE on that resource to delete the Entry.
RSD is used as the format to hold both the "createURI" and the "archviveURI". When editing a web site, the RSD file needs to be found before editing can begin. Part of the RSD specification is for Auto-Discovery, the addition of an HTML 'link' tag to a web page that contains the URI of the RSD file. Please see the @@external link?@@ RSD Specification for more details.
@@ What about WSIL? @@
None.
| TOC |
None.
None.
None.
None.
None.
None.
None.
None.
| TOC |
None.
| TOC |
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 (TXT, HTML, XML). |
| TOC |
| Joe Gregorio | |
| BitWorking, Inc | |
| 1002 Heathwood Dairy Rd. | |
| Apex, NC 27502 | |
| US | |
| Phone: | +1<PHONE_NUMBER> |
| EMail: |<EMAIL_ADDRESS>|
| URI: | http://bitworking.com/ |
| TOC |
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.

Funding for the RFC Editor function is currently provided by the Internet Society.


{% extends "base.html" %}
{% block head %}
{{item["text"]}}
{{tale["description"]}}
If you are using Whole Tale or planning to try it, join the our Slack workspace or subscribe to the wholetale email list to hear what other users are doing, ask questions, and listen in on and join the community discussion.
If you would like to suggest new features, or participate in the discussion of implementation issues, please follow the project on GitHub .