text:
Nobody Needs Reliable Messaging
- Share
- |
Read later
Reading List
A received view in SOA and Web Services is the need for reliable messaging. Reliable messaging is the guarantee that a message sent by a sending application is indeed received at the other end, and received only once. One of the most common objections against REST is that REST doesn't offer reliable messaging. Stefan Tilkov writes: 'It's often pointed out that there is no equivalent to WS-ReliableMessaging for RESTful HTTP, and many conclude that because of this, it can't be applied where reliability is an issue (which translates to pretty much every system that has any relevance in business scenarios)'[1]. Tilkov does not agree, of course, and prefers a solution on the application level. Joe Gregorio made a similar point in RESTify DayTrader [2]. Rightly so, the assumption: for business purposes we need reliable messaging, is simply false. The reverse is true: from a business perspective, there is absolutely no need for reliable messaging. If we have well-defined business semantics and business logic, separate reliable messaging is redundant.
Web Services and Reliability
Web Services offer a way of insulating message exchange details from business logic. Basically the idea is we describe our business in terms of services (i.e. 'browse catalog', 'place order', check order status' etc.). The services are implemented by exchanging business documents, which embody the business semantics. If we use Web Services, the business documents are carried in SOAP Envelopes. The SOAP Envelopes also may carry SOAP Headers, which implement pieces of messaging functionality: message security, integrity, addressing, reliability et cetera. Each piece of messaging functionality is independent of the other pieces: i.e. it is possible to do message integrity without reliability, the reverse, neither or both.
The above picture highlights some important features of SOA as implemented using Web Services:
- the business layer is independent of the messaging layer;
- Web Services add independent 'plug & play' pieces of message functionality;
- message headers carry information on required messaging functionality.
Web Services are not always reliable by themselves. The basic problem: if I send a message, say I order a book, and through some netwok glitch the message never arrives, I get no book. Simply resending the message would solve this, as scenario 1 shows.
However, if the message arrives, but the response is lost, resending will not work: if I've ordered a book, I'll receive two books in scenario 2.
Reliable messaging solutions usually solve this problem through acknowledgements, duplicate detection and duplicate removal, as scenario 3 shows.
Web Services offer WS-ReliableMessaging[3] as the standard for reliable messaging. WS-ReliableMessaging can offer several guarantees: that messages sent arrive at least once, at most once, exactly once and/or in order. Since what one usually wants is that messages arrive once and only once, I'll only discuss the 'exactly once' and 'in order' cases. Let's start with in order arrival of messages.
The Right Order
There is a friction between the guarantees of WS-Reliable Messaging and the ordinary processing of messages from a business perspective. A common case where in-order processing is important, is in online banking. If I transfer money from my savings account to my checking account, which is near-zero, and subsequently transfer money from my checking account to a third party, I want the money transfers to be processed in order: otherwise the second transfer might bounce due to insufficient funds. I know this is important: my bank doesn't offer in-order processing, and my transfers regularly bounce when I forget to submit them in two separate sessions...
It seems WS-Reliable Messaging is ideally positioned to cure such situations. However, on further inspection, it's not that crystal-clear. What does WS-Reliable Messaging do to achieve in-order processing? Unsurprisingly, it attaches an incremental sequence number to each message. If the messages arrive out of order (i.e. 2-1-4), the WS-Reliable Messaging software at the receiving end waits till the missing messages arrive, and then submits them to the next layer which contains business logic in-order (i.e. it submits 1 and 2, waits for 3, then submits 3 and 4). The first strange thing is that apparently the order is a property of messages which is important to the business layer. So if it is important to the business layer, why isn't there a sequence number in the business message itself? We have a message, with its own business-level semantics, and the order is important: so why isn't there some element or attribute in the message, on a business level, which indicates the order?
There are two possible answers. First: there is also a sequence number in the payload, with business semantics regarding order attached to it. If there is, why do we need WS-Reliable Messaging? It's doing things twice. Maybe, in a few cases, doing things twice may be the thing to do (say my very fast and efficient WS-Reliable Messaging box can do this really really fast, and then the business layer receives only in-order messages and just checks to make sure) but in general doings things twice makes me wary. It introduces redundancy. If the sequence indicators in the WS-Reliable Messaging headers and in the payload differ, what do I do? How do I make sure the same rules apply to errors in in-order processing in both levels (say a missing message never arrives: do I submit none of the remaining messages, or all with an error condition, or alarm a human to sort things out?). Things will only work if both levels, WS-Reliable Messaging and business, conform to the same logic.
The second answer is: there is no sequence number in the business payload. After all, one might say, we've got WS-Reliable Messaging, so why do we need it? This, frankly, is turning the world upside down. If the order is important on the business level, the business level needs to indicate order, ensure its proper processing and persist it as well. If we make the order, important on a business level, dependent on the order in which messages are shoved into a WS-Reliable Messaging-bus at one side, and the order in which they come out at the other side, we make a permanent feature of the business logic (order) dependent on a transient feature of the message processing: the order in which they come out of a message bus. The WS-ReliableMessaging sequence number is lost after the WS-Reliable Messaging bus has done its work, making any decent logging or auditing impossible. Of course it is possible to attach a new sequence number to the messages, which indicates the order in which the messages came out of the WS-Reliable Messaging box, but still, without logging the entire WS-Reliable Messaging stream this carries little weight for serious auditing purposes. And logging the entire WS-Reliable Messaging stream is certainly possible, but it all seems so much doing things at the wrong places.
Moreover, the in-order processing is not just a feature of the interaction between the WS-Reliable Messaging bus and the business layer. If my bank has resulted from a merger of two banks, and my savings account happens to be in a different database than my checking account, on a different machine in a different location: then just submitting the messages from the WS-Reliable Messaging bus to the business layer in the right order doesn't do the job at all. The business layer needs to make sure the savings software and the checking software do their jobs in the right order too. This example shows how deeply embedded in-order processing may be into the business logic. Implementing this without order indicators in the message payload itself is insanity.
To summarize: if in-order processing of messages is a property of the business we're conducting, we need order indicators in the messages on the business level, with appropriate business semantics and business logic attached. If we follow this simple and sound design guideline, then we don't need WS-Reliable Messaging. Maybe in some cases using WS-ReliableMessaging might be more efficient. From a business perspective, however, functionally there is no need for WS-Reliable Messaging in a properly implemented business layer.
Once, and Only Once
A similar line of reasoning applies to exactly-once delivery. I've got a message for you: and on a business level, it's important that it's delivered once and just once. Say I have a book order: I don't want to receive the same title twice, nor do I want it not at all. Now, if it's important to us, on a business level, that I get my book exactly once, what does the assurance that my message has been received exactly once really bring me? I want to know that your book ordering system has received it. If the WS-Reliable Messaging bus accepts it, and subsequently the book system rejects it because I've entered a wrong client number or a non-existent catalog item, knowing the message has been received brings me preciously little assurance. And even when the message is syntactically and semantically correct, it's no good if the title is out of stock: I want my book, not just the certainty my message has been received well. If the processing of my message once, and exactly once, is important on a business level, I need to confirm the exactly-once processing on a business level. As the figure below shows, the transport acks are pretty meaningless on a business level: we need the business ack.
Some may argue that the WSRM module should do syntax checks on incoming messages as well. And of course a WSRM module could do most of the syntax check, say a schema validation. But look at customer numbers, or catalog items: it is impossible to know whether a certain customer number or catalog item is a valid one without doing a database lookup. And knowing whether a title is in stock isn't possible at all on a syntactical level. There is no way to guarantee that a message will be acceptable to the business level without actually submitting it to the business level. And if the business level may refuse my message, knowing the WSRM module has properly received it is not what I need. I need a business reply, assuring my message has been accepted once, and only once, on a business level. If receiving every message exactly once is important on the business level, the business level should respond with a message saying it has received, and accepted, the message. Again, if this simple design guideline is followed, there is functionally no need for separate reliable messaging from a business point of view.
Let's look at the 'exactly once' requirement in some more detail. Stating that it is important on the business level that every message is received exactly once, like it is in order processing, means that every message constitutes a unique business transaction. Like with in-order processing, WSRM guarantees exactly-once delivery through attaching unique numbers to messages, acknowledging receipt, and possibly resending or duplicate removal. Again, if every message is a unique business transaction, clearly there must be a unique id on the business level: an order id, a reservation number, some unique token. And if we need such a unique token on the business level, the business level should assert it's uniqueness. Uniqueness on the business level should not be dependent on the transient uniqueness on the message level, but must be a persistent feature of the business message, and business semantics must guarantee it.
Idempotency to the Rescue
When the business logic requires in-order processing or exactly once delivery, I clearly need a business reply: the business reply is the only guarantee that, on the business level, my message was received and processed correctly. Simply returning the business reply instead of all the WSRM magic does the trick, and way better than WSRM can do. And what happens if we do implement unique business transaction ids and business acks on the business level? Basically we make every message idempotent on the message transport level. If we have unique business id's, duplicate detection on the business level, and business acks, it is always safe to resend a message on the message level. This makes reliable messaging a no-brainer: if I receive a HTTP 200 OK response (or some other 'success' response) on my message, everything is fine: my message has been received, and if the business response is not sent in the HTTP response, I may wait till I get it. Of course, in implementing the web service, we need to make sure the incoming message is stored on some persistent medium before we respond with '200 OK' - otherwise the message would still be lost if a computer crashes. But with WSRM we would need a similar guarantee, WSRM by itself doesn't offer it. And if I don't receive a '200 OK' through some communication glitch, it is safe to resend the now idempotent message until a response is received.
The Case of Dutch Healthcare
In the Netherlands, we're setting up a national healthcare infrastructure. All healthcare organizations will exchange information through a central Healthcare Information Broker. All healthcare professionals with relevant credentials will be able to access information for their patients through the national exchange. A national standardization organization, Nictiz[4], develops the relevant national standards based on HL7v3, the medical vocabulary and messaging framework, and Web Services.
Originally there was no standard for reliable messaging available: in 2003 and 2004, the turf wars about WS-Reliability versus WS-ReliableMessaging where still going on, and we decided to use a temporary home-grown solution till the dust had settled. In 2008 and 2009 we returned to the reliability issue: since the national exchange was coming up to steam quickly, the temporary solution was no longer viable. We designed a solution based on WS-ReliableMessaging and decided against it. Let's look at some of the details.
In order processing was hardly relevant in our case: exactly once delivery was, or so we thought. We use synchronous communication, SOAP over HTTP, where a message is sent as HTTP request and the business answer is carried over the HTTP response. There are, simplifying a bit, two kinds of transactions:
- queries, such as a query for a patients medication history, where the query response is returned as HTTP response;
- orders, such as a medical prescription, where a business response (usually a HL7v3 acknowledgement) is carried over the HTTP response.
In the first case, queries, there is simply no need for reliable messaging. If, through some communication glitch, the query or the answer is lost, the query can simply be submitted again. Queries are safe: the state of the server is not changed in any way (other than maybe traffic counters and other non-relevant side-effects).
For orders, the case is different. If a GP sends a prescription to a pharmacist, it is important to know that is has been received, and received only once. If all goes well, there is no problem: the GP sends a prescription, the pharmacist's server returns an HTTP '200 OK' response, and the GP's application reports the prescription has arrived. If things do not go well, there is a problem. If the GP's application does not receive a '200 OK' response, what to do? If the prescription never arrived at the pharmacist's server, it should be resent. If it did not arrive, it may not be resent: that might be interpreted as a second prescription, not a duplicate.
However, prescriptions already carry an unique prescription id.
<Prescription> <id extension="0003000201" root="2.16.840.1.1138220.127.116.11.1.6005465.12.1"/>
This XML fragment shows the prescription identifier in HL7v3 format. The 'root' part is an OID, which is assigned to each healthcare provider's application: no two applications will have the same root attribute. The 'extension' part is a local unique key for the prescription: the same number which appears in print on prescriptions as well. Together they constitute a globally unique identifier.
Since the prescription id is unique, we require a receiver to check for double prescriptions, using the prescription id. If a prescription is received twice, an error message is returned. (In some cases, where needed, we also require the receiver to return a duplicate of the original answer, if it contains information which is needed.) What does this do? Since duplicates are removed on the business level, all messages become idempotent: it is always permitted to resend a message in case of doubt about the communication.
Much of the use case for transport level reliable messaging is gone: if no acknowledgement is received, the prescription is simply resent. The error which is received when the first prescription has been received after all, is as much proof of successful transmission as the original acknowledgement. We've tightened our specs a bit on returning and interpreting this specific error condition, and all of a sudden separate reliable messaging is no longer necessary. It's even hardly an effort: since HL7v3 has a prescription id, which must be unique, each healthcare application has to handle duplicate prescription id's anyway. If the acknowledgement carries information which the GP has to receive, we could require the pharmacist to reconstitute the original acknowledgement and return it on receiving a duplicate prescription: the situation doesn't occur too often though, and for simple acks it is not needed. So a bit of tightening of the business rules has removed the case for separate transport reliability: all it would do is add another layer which assigns unique id's and handles duplicates again. Note that it isn't just WS-ReliableMessaging. It may be the main contender, but for alternatives such as ebMXL Messaging or WS-Reliability, the same line of reasoning applies.
WS-ReliableMessaging alone isn't good enough for synchronous messaging either. In cases where the client is behind a firewall, or has an unreliable mobile connection, the client isn't addressable directly by the server. So the server has no way to resend unacknowledged responses to the client if the HTTP connection is closed unexpectedly. Another WS-* specification is needed for this case: WS-MakeConnection, which enables the client to set up a new HTTP connection and poll for potentially waiting response messages. Since all our traffic in Dutch healthcare is synchronous, this addition is necessary. So instead of upgrading all necessary clients with just WS-ReliableMessaging capabilities, the much newer WS-MakeConnection is also needed (and most clients today simply do not have the necessary libraries yet). WS-MakeConnection also basically makes all synchronous traffic asynchronous in case of failure. While this not necessarily a bad thing, it would make the Dutch healthcare specification much more complex. The WS-* mantra is often: the complexity of the specification is hidden from the developer by the software: install your WS-* libraries, and they will do the magic for you! I never believed in this 'complexity-hiding-philosophy'. Any developer worth her salt will want to know what's going on behind the curtains on this level. It's impossible to debug a live session if you do not even understand whether your traffic is synchronous or secretly split up.
In Dutch healthcare, given the complexities of reliable messaging, and given the fact that the use case from a business perspective mostly evaporates, we've decided not to use reliable messaging on the transport level. With a bit further tightening of the business logic, which requires unique prescriptions anyway, we can have a much simpler solution.
To summarize: if reliability is important on the business level, do it on the business level. A Reliable Messaging layer can handle only generic logic, but that's not what we want: we want business-specific logic for in-order and exactly-once processing. WS-Reliable Messaging (or its competitors) may sometimes have some value in optimizing solutions, especially point-to-point. But from a business perspective, a well-designed business solution does not need reliable messaging.
About the Author
Marc is an independent consultant with over 20 years of IT experience. He specializes in cross-enterprise interoperbility and semantics, and is a frequent speaker and author. Marc lives and works in Amsterdam, the Netherlands.
[1] See Stefan Tilkov, Addressing Doubts about REST (http://www.infoq.com/articles/tilkov-rest-doubts) point 7: REST is unreliable for a discussion.
[2] See Joe Gregorio, RESTify DayTrader, http://bitworking.org/news/201/RESTify-DayTrader
[3] See Paul Fremantle, An Introduction to Web Services Reliable Messaging, for a good overview: http://www.infoq.com/articles/fremantle-wsrm-introduction
Rate this Article
Hello stranger!You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered.
Get the most out of the InfoQ experience.
Tell us what you think
Duraid Duraid
See, business logic is hard and expensive to get right and that's why those software standards exists so that we don't have to take care about one more extra thing.
Re: But
James Watson
Re: But
Duraid Duraid
Re: But
James Watson
In a proper REST design, if you attempt to create the same order twice, it has no effect. There is no special coding around this. It's a property of the architecture. It's kind of like a 3-prong outlet. As long as you don't tamper with the design, you can't plug it in the wrong way.
Re: But
Duraid Duraid
Re: But
Stuart Charlton
The original paper, still worth reading, is here: web.mit.edu/Saltzer/www/publications/endtoend/e...
"[Certain functions] in question can completely and correctly be implemented only with the knowledge and help of the application standing at the end points of the communication system. Therefore, providing that questioned function as a feature of the communication system itself is not
possible. (Sometimes an incomplete version of the function provided by
the communication system may be useful as a performance enhancement.)"
You can't guarantee application-level "reliability" in an application by using a lower layer's subsystem, whether WS-* or TCP. At best, providing those qualities at a lower layer is a performance or modularity optimization. And many times, it is neither -- it gets in the way.
TCP is very well designed and configurable (the way TCP is with adjustable windows, NAGLE disabling, backoff, etc.) but for some applications (e.g. video conferencing, some gaming) it makes sense to avoid it and use UDP.
WS-RM doesn't have the field tests that TCP does, I'm sure it adds some modularity value but it isn't "required" to enable application-level message reliability.
Re: But
Marc de Graauw
'in order to achieve careful ... transfer, the
application program that performs the transfer must supply a
... end-to-end reliability guarantee'
Same for duplicate removal, later on.
Re: But
James Watson
What about the TCP example that I brought up. With TCP you don't have to care about the packet ordering because it's taken care for you at the transport level and I believe that's a good thing, isn't it? Isn't WS-* trying to do the same thing?
It's not really meaningful to compare a transport layer protocol with a transaction layer protocol. In my work we use reliable messaging but we would never expose this detail to our service consumers. In my opinion, specs like WS-Reliable violate a number of SOA principles. In practical terms, it's really of no concern to the client how their request is satisfied. And as I think this article makes very clear, if you have a business requirement for ordering, then you must address it at the business layer. The history of computing fads is littered with failed attempts to abstract functional requirements in protocols.
Re: But
Duraid Duraid
Re: But
Stuart Charlton
Re: But
Stuart Charlton
TCP has proven to be a very useful abstraction, hitting the right balance of modularity and configurability for most Internet applications.
One can not say the anything close to the same with regards to WS-RM. Proprietary messaging protocols & subsystems such as MQSeries have had much more field testing and deployment. And as anyone who's used MQ will tell you, it ain't necessarily wonderful out of the box (as TCP is).
Re: But
Duraid Duraid
I agree with you maybe it's hard to get reliability right when the scale is big but maybe there is nothing wrong of doing it in the context of one application or organization and maybe that's the way to go. Don't change the method, reduce the scale.
Re: But
Marc de Graauw
"The article sounded very strong in abolishing all reliability at the transport level" - my point is there is no *functional* need for reliability at the transport level - it should be done at the business level. That does not mean reliability at transport level is always wrong. Also for WSRM, there are cases where it's useful. If your transport is not very reliable, and you're doing a lot of asynchronous messaging, it may make sense to optimize at the transport level. So transport level reliability may be useful as an optimization, but even then, business level acks will still be required.
Do it at the business level?
Paul Fremantle
So the first thing that might motivate people to use reliable messaging is to re-use code that is tested and optimized. However, I think Marc, you make a good argument why it doesn't hurt to think about it in business logic if you can.
Unfortunately, many people using reliable messaging systems (like Apache QPid, WS-RM, IBM MQSeries) are not writing business logic from scratch. They are often integrating with existing systems and CANNOT write Idempotent logic. So for all those people who aren't writing logic from scratch, WS-RM and other reliable messaging systems are very useful - and often essential.
2 reliable messages in 1 transaction?
Peter Verkest
How would you handle the classic example where I want to send 2 messages, one for booking a flight and another one for booking a hotel? Do you propose to implement compensation logic in the business layer (for rolling back the flight boooking) in case the second message (booking the hotel) doesn't return an ACK or returns an error?
Re: Do it at the business level?
Paul Fremantle
One other mistake in your article is to say that WSRM 1.0 doesn't support working through firewalls. The replay model is documented and supported in most WSRM1.0 stacks and works fine. And all stacks that support WSRM 1.2 also support WS-MC as far as I know, so in either case you get reliable messaging through a firewall.
Re: Do it at the business level?
Marc de Graauw
Glad you respond!
"many people using reliable messaging systems ... are not writing business logic from scratch. They are often integrating with existing systems and CANNOT write Idempotent logic."
True. In the Netherlands, the existing HL7 messages weren't always idempotent. Fortunately we can add extra requirements in our national standards. If not, we indeed could not have implemented reliability on the business level.
That's why I stress in my article that a well-designed business solution does not need transport reliability. And I'd argue that those non-idempotent legacy systems without reliability on the business level aren't designed as well as they should have been; still, there are plenty of those around, and yes, in those cases transport reliability does add value.
Re: Do it at the business level?
Marc de Graauw
The Replay Model is indeed a potential solution, but it is not an open standard. So using it means depending on a non-standard extension to an open standard... We considered it, but it didn't make me happy.
As for WSRM 1.2 stacks supporting WSMC, I immediately believe you. However, in Dutch healthcare we're talking about thousands of different software environments, very modern to very old. Fact is we have to be conservative in the what we require, and WSRM 1.2 stacks won't be ubiquitous yet... That the standards and stacks are moving forward is a good thing, and I'd agree that the firewall problem is a temporary thing.
I'm not convinced
George Skalley
Also employing infrastructure that allows Guaranteed Delivery (store and forward) in conjunction with Durable Subscription patterns for infrequent connections should address these issues and keep WS-RM entirely relevant.
This would prevent the prescription being sent repeatedly and treat business acknowledgements as "equally important", something which your example says it expects, but doesn't deliver. Instead you've bypassed this by allowing extra conversations between the servers to take place and re-interpreting the error response as a successful condition.
After the initial success of sending the prescription, that message should be stored and not repeated. Wait for the response to come (as it will be coming if implemented back using WS-RM) before finalising the transaction.
Business obviously understands that reliability is a serious concern, hence the reason for formulating WS-RM in the first place. I'm fully not convinced that the current state of play is one in which RESTful services do cover this subject areas well enough, as it's reliant on interpretations of messaging patterns developed for WS-RM to be abstracted and supplied by development teams using additional business logic.
Given a requirement for high volumes of mission critical transactions over low latency networks I'd advocate open standards that at least attempt to embody the required patterns over an architecture which does not.
Re: But
James Watson
James your statement is very contradictory. You say 'The history of computing fads is littered with failed attempts to abstract functional requirements in protocols' but TCP is a protocol and is not a fad.
TCP doesn't abstract functional requirements. Specifically, it doesn't guarantee delivery. What is does is hide the details of resending dropped packets and determining when a message failed to be sent correctly. REST Web services and WS* are 'always' implemented over TCP but we still need something else to guarantee that our transactions are delivered. The reason is that, ultimately, only the business requirement of the transaction can tell you whether it has succeeded.
Any system can fail, including reliable messaging systems. Therefore the client will always need to have some ability to submit retries. There is no way to abstract that detail away.
Re: I'm not convinced
James Watson
This would prevent the prescription being sent repeatedly and treat business acknowledgements as "equally important", something which your example says it expects, but doesn't deliver. Instead you've bypassed this by allowing extra conversations between the servers to take place and re-interpreting the error response as a successful condition.
I don't see where you get "re-interpreting the error response as a successful condition" from this but I can offer some information about how this actually works from the US perspective (Paul giving a European perspective.)
Pharmacies are 'client' only. They do not run app-servers that can receive responses. Therefore all requests are synchronous.
A large number of claim requests (perhaps most) that I see are rejected and are submitted 2, 3, sometimes there are a hundred attempts to process a single claim. Sometime there is a timeout or other system error requiring that the client resubmit. Each claim request has a unique ID so duplicate requests are never treated as separate requests is a request were to succeed but not get reported back to the client properly.
None of this is done with SOAP, XML, HTTP or any 'reliable messaging'.
Re: I'm not convinced
James Watson
(Paul giving a European perspective.)
Sorry, I should have written 'Marc' instead of 'Paul'.
Re: Nobody Needs Reliable Messaging
ben wilcock
As a retail SOA architect who has designed loads of services, I agree that good idempotency rules and idempotent messages can allow you to create quite a large SOA ecosystem without the need for the WS-* standards. In fact, on my next system I'm going to try and reduce the complexity of the SOAP headers I designed back when I thought that sequence of delivery etc. was important.
Thanks for the write-up and case study. I'll be bookmarking this.
Nice solution
Robert Sullivan
Anyway, there's code involved, admittedly in your situation it's limited, but I will follow Bjarne Stroustrup's philosophy which is that if some functionality is already done in the language, or in this case some other layer, use it.
For example, before the days of web services, and when standards like HTTP-r (I think) and WS-Reliable were in their infancy, MQSeries was used quite heavily for interoperability, and still is, and this feature is built-in, it's only a matter of setting some message properties. It's always interesting to see the newer "silver bullets" come out, much simpler at first since they don't have all the complexity of previous technologies - security, QoS, etc, and then have to frantically add that in, as is the case with WS, and now REST. Then it gets too complicated, and we start all over with the next new new thing.
Re: Nice solution
James Watson
Thanks for the article - it's always interesting to see how typical problems like this are solved. One thing to clarify here is you are doing reliable messaging, not WS-ReliableMessaging. This requires some logic on the server, to send back the duplicate exists error message, and some logic on the client to keep resending.
WS-ReliableMessaging requires this too.
Anyway, there's code involved, admittedly in your situation it's limited, but I will follow Bjarne Stroustrup's philosophy which is that if some functionality is already done in the language, or in this case some other layer, use it.
What code? Do you mean the code that e.g. captures a constraint violation from the DB? You are going to have to do that anyway.
That's the point. a REST architecture already guarantees that duplicates won't be reprocessed. There's no need to build any special message formats or code to do that ala WS-ReliableMessaging.
For example, before the days of web services, and when standards like HTTP-r (I think) and WS-Reliable were in their infancy, MQSeries was used quite heavily for interoperability, and still is, and this feature is built-in, it's only a matter of setting some message properties. It's always interesting to see the newer "silver bullets" come out, much simpler at first since they don't have all the complexity of previous technologies - security, QoS, etc, and then have to frantically add that in, as is the case with WS, and now REST. Then it gets too complicated, and we start all over with the next new new thing.
Who says you can't implement REST using MQ-Series or any other reliable messaging system? We need to be clear that REST is an architectural style. It is not a protocol or technology. Even when we talk about RESTful Webservices (what is really meant by REST here) there is no specific approach that must be followed to satisfy the request. The only thing that REST indicates is the structure of the interface.
Easy to use RESTful resources to help evangelize REST
Juergen Brendel
We have been working on RESTx - an open source project that makes it very simple and straight forward for business users to create new RESTful resources, merely by filling out a form and very easy for developers to write components to implement RESTful services. Maybe by exposing more users to REST and showing how straight forward and simple resources and architectures can be, this project can help to educate user and developer communities so that we don't have to explain the same things over and over when trying to introduce REST as an architectural option.
1 service
Guy Pardon
This all looks very reasonable, and I agree that WS-* is too heavy. But: if you need more than one service to address then you probably need something like TCC: www.atomikos.com/Publications/TryCancelConfirm
Alternative like diversity is a good thing
Arturo Hernandez
So the cost or effort issue is most likely the determining factor but is only assumed here. Complex systems are harder to maintain, so why add more complexity when it we can kill two birds with one stone. We HAVE to do the application level anyway? Even if WS-RealiableTransaction was easy to configure and maintain. The added reliability is questionable.
The question then becomes. How much effort do we place on making every single transaction reliable at the application layer? Keep in mind not only banking applications benefit from it. If the effort is significant, then we can ask this next question. How much more reliability will we gain from application level reliability, if we have WS-ReliableTransaction? Even if it may be more sound, do we really NEED reliability at the application level?
I guess the answer still depends on the application domain and effort. Others here say they have done it before without WS-RM. In that case they already have reusable code, and they are familiar with it. So it is less effort for them. But for a newbie like me, I don't really have a good idea of how difficult it is to implement
Silly Rant
Chuck Farley
Re: Silly Rant
Arbenz Guido
the article is trying to say that reliability on a lower level can never guarantee reliability on any higher level. Look for example at TCP. Even though it is reliable - that's the whole point of TCP - why do higher level protocols that sit on top of TCP (be it via HTTP or SMTP etc.) like WS-RM try to add "more reliability"? Isn't the lower level guarantee enough?
The reason is that the lower layer cannot guarantee that there are no errors on higher levels, or the interface between lower and higher levels. There will always be potential points of failure between those levels. Say an application crashes. Now although TCP reliably transported a number of bytes - did the application, before crashing, manage to process (and e.g. store in a database) those bytes or did it not? How is TCP expected to know that? It cannot, and so the higher layer has to ensure that.
The same that I said about TCP and the higher layer is true for any lower level / higher level scenario. Reliability can be guaranteed on a level, but not across levels. And WS-RM is lower level than your application that uses it.
Re: Silly Rant
Arturo Hernandez
Let's stay with simpler examples. Say I have a known set of files to transfer via ftp. My code could be written to transfer any non-transfered file in my known set. Would that eliminate the benefit of a reliable FTP? That depends on the Reliable FTP implementation, it may very well be that a reliable FTP could recover much quicker than an application level retry.
So in a way the author is making two arguments, a generic flawed argument of reliability at different application levels. And how WS-Reliable may not have worked in particular cases. At the end it did not give me the information I was expecting.
Better and simpler
Ad Gerrits
Wonderful analysis, but...
Rupinder Gill
Sharp analysis, wonderfully presented! bravo.
and Thank You.


text:
Sorry, the items you are viewing are either out of stock or removed.
As an alternative, you can:
- Modify the key words in the search bar on top.
- Try other pages: Home > OTC medicines / medical devices / lenses / planning supplies > Contact lens / care solution > Color contact lenses

subset: commoncrawl


text:
Analyst: Facebook's HTC Android Screen a Good Move
Facebook will unveil an HTC smartphone that deeply integrates the social network via the home screen. It's a good move and critical for Facebook's future growth. Ovum chief telecom analyst Jan Dawson joins Markets Hub. Photo: Getty Images.
This transcript has been automatically generated and may not be 100% accurate.
... I ... you'll you'll be watching ... mind Facebook fall ... all my When until one pm exactly today when Facebook unveiled the pot you see what it is seen as really a bomb is just ... what is the isthe into your phone ... morning Evelyn welcome to markets of mine Paul vignette ... we were joined today by ... chief telecoms analyst at ovum research and consulting firm ... E on Dawson ... toward filling a Jersey resident that's right so glad to have the on here today ... I hope it sort of Facebook one pm today they're going to unveil what what's being called the Facebook phone ... but he is not necessarily a phone is ... right there probably will be a fun and bright but all these reasons yet the reason is just an ETF's Minnesota's off on yet ... but the whole concept of from what we seen in the dream isn't someone is ... listening to be installed on any Android phone ... bill BMO insurer and screen you can use to replace the standard and going home screen a new device ... and it could be installed on existing Android devices is open said ... not a single front of the party will show a time like the from HTC today ... that will be running this out of the box just to show enough respect Ospel Brandon for Facebook bulls and talk about mobile it though the website body is in no way that these were sort ... of mobile advance of the gross thing I had some stumbles getting to that ... is this a major push for them or is this on my Inaer experimental with what exactly were looking for I think is best kept rises in experiment at this point in trying something new something goes deeper than just installing an app for these are installing out on a device ... to take over the Times claims that in the seventies taken goal centric experience on the phone with Gene Allen and the consensus from Santa ... Facebook says his enemy everywhere Facebook pages and any day ... the ability to place a status updates to upload a pic said to start the video voice that would send a message ... the reason things in the front and center on the device and that's with the need ... to test a big deal but is an experiment may visas don't want that and the communities is done right so that's the risky alright that's the thing right I mean how many people ... and also that the numbers Monday how much money they make office or title but every day you know you ... can cancel like Active User versus people who live on Facebook and that the current balance the interest rate with this right but when you have an advertising based revenue stream a subpoena more people use your services ... the more as they get exposed to the more money made from them so they want to increase that so this is an attempt to increasing gauge with Facebook platform ... of course anyone to finance about more advertising on about it and so ... on in the ads on the home screen where the ads can show up the Guinea get more eyeballs on its hands ... and of course this Olsen be the potential for tracking mortgage activity on the device ... that is peaceful the Facebook but again for me is a perspective do you really want that to answer that's the other risk is that no one wanted is this the company because it's a software product essentially to contain ... just cut up all for this out there let people cut taken up on their own or do they have to partner with phone companies ... to get the software in the Android system ... they don't have the owner and comes as is the great Aunt Susie had noted in some dialects with a one two years of working with Apple defining it the right options that he can be simple stuff like he's Lee Shane status on Facebook from my phone ... with Android ... whoever wants can build something like this and it can take of the whole phoning people doesn't have to say ... anything about it until nicely do it aam which is good because people has its own assessment within ... the country would be Leckie on Facebook taking her ... to ... do you do you think this is going to ... tell speculation and I haven't seen the thing yeah right my twenty oh I tell myself you sort of excited about it as analysis of EA's Houston since the potential of this ... odd inside and out because it's new and different opinion of Facebook applications and around for ages now they increase the functionality over time so with this pre get to know the desktop ... but this is going beyond that Mrs is he doing things that one possible who like ... making voice calling a messaging and keep on the phone interface ... Robinson is to dip into and out of the beat I mean we use ... to Allert the VC lot of our take on this house and BP would be before the copycat calm me to Facebook and do this sort of payment ... other platforms to try to run a serious but postponed already launches an on screen the place was out there to the NEB for the hackers and thinkers out there rather than the mainstream system in the first mainstream one ... we can take and Foursquare one awesome of a case ... by owning the summing Samoa ... on Sunday that can be quite awful is them on the platform once in a speech in a place to trail ... is ... our ... Eon Dawson think you're a much enjoyed the


text:
LAS VEGAS -- Federal officials say a medical spinal implants and surgery products company incorporated in Nevada has agreed to pay $30 million to settle allegations that a subsidiary paid illegal kickbacks to physicians to use its products.
The Justice Department announced Friday that Orthofix International NV agreed to resolve claims that Blackstone Medical Inc., provided surgeons with travel and entertainment and sham consulting, royalty and research deals.
The publicly traded company put the settlement amount at $32 million. President and chief executive Robert Vaters issued a statement in Leesville, Texas, saying he's pleased with the settlement.
It resolves a civil lawsuit filed in September 2006 in U.S. District Court in Massachusetts stemming from a whistleblower complaint by Susan Hutcheson of Florida. The Justice Department says she'll receive $8 million from the settlement.


text:
The Oregon Department of Agriculture announced six fines totaling $2,886 in connection with incidents last summer in which thousands of bumblebees were killed by pesticide applicators.
Three of the civil penalties stemmed from the largest incident, in Wilsonville. An estimated 50,000 bumblebees died after European linden trees were sprayed with dinotefuran. Landscapers intending to control aphids sprayed the trees in a Target store parking lot and wiped out bees foraging in the trees. Smaller bee kills happened in Hillsboro, West Linn and downtown Portland.
Collier Arbor Care of Clackamas, a licensed commercial pesticide company, was fined $555 for applying pesticide in a faulty, careless or negligent manner in the Wilsonville case, the agriculture department said. Two applicators, Mark McMullen of Beaverton and Sean Rinault of Woodburn, also were fined $555. The ag department said the pesticide label states the product is hazardous to bees when applied to flowering trees.
Collier Arbor Care was fined $407 for the downtown Portland incident. The applicators, Sean Rinault and Ray Duval of Estacada, were each issued civil penalties also in the amount of $407.
The fines are a followup to action announced in November, when the department said it will require an unusual state-specific label on the use of pesticides containing the active ingredients dinotefuran and imidacloprid. The state action bans the pesticide use on linden and basswood trees, which are among the Tilia species.


text:
EZ Bundle 4-in-1 Baby System
A reader tipped us off to this multipurpose product which she saw on Unclutterer. In theory we love the idea of both a space-saving and money-saving ($150) product that can be used through birth as a seat or swing and then as an infant and toddler high chair and finally as a chair. But we wonder if this is a case of the whole being less than the sum of all parts?
Don't get us wrong - we applaud innovative attempts to problem solve for space-pressed parents and we're very interested to know what you think of this product (we haven't come across any personal reviews yet). It seems to us that the newborn seat (which doesn't bounce) and infant swing might cancel each other out since they're both intended to be used from 0 to 6 months. And the toddler chair doesn't look particularly comfortable to us (akin to sitting in a legless high chair all day).
Has anyone purchased this and can give us a review? What do you think - an answer to your small-space prayers or do you prefer to choose more feature-heavy individual pieces?
You can learn more about the EZ Bundle 4-in-1 Baby System at Fisher-Price.
Thanks Emi!
(Via Unclutterer)


text:
BAMBU WEST COVINA, 989 S Glendora Ave, West Covina, CA, USA
Location: BAMBU WEST COVINA, 989 S Glendora Ave, West Covina, CA, USA
Report Type: Temporary Closure - related to food safety
Closure Date: Aug 24
Details: Vermin Infestation - California Health and Safety Code Section 114259.1
Reported By: Iwaspoisoned.com User
More incidents from: Other | United States | California | West Covina |Comments
Number of reports: 1
No comments. Be the first to comment.
Recent Reports
Nov 17 4:40pm
Anson Road, Café 2000, Singapore
Symptoms: Diarrhea Nausea Vomiting
Report Type: Food Poisoning
International seafood. Oysters and sashimi. Both my husband and me have diarrhoea after the lunch buffet. Read More
Nov 17 5:19am
Hyderabad Chefs, APHB Colony, Andhra Pradesh Housing Board Phase-IV, Indira Nagar, Gachibowli, Hyderabad, Telangana, India
Symptoms: Diarrhea Nausea Vomiting
Report Type: Food Poisoning
Nov 16 11:44pm
Akira Ramen & Izakaya, Rockville Pike, Rockville, MD, USA
Symptoms: Diarrhea Nausea
Report Type: Food Poisoning
They used cans of Butane with a torch attachment to cook the meat - ir may I say chard the outside of the pork leaving it raw - in order to speed up how they expedited the high volume of orders. The food was full of chemicals My partner and I got sick right away. Now the second day and it was awful. Read More
Nov 16 8:15pm
Sibling Soul Food, South Ashland Avenue, Chicago, IL, USA
Symptoms: Diarrhea Vomiting
Report Type: Food Poisoning
Country fried chicken. Vomiting, diarrhea Read More
Nov 16 8:45am
Joy Teriyaki, 6th Avenue, Tacoma, WA, USA
Symptoms: Diarrhea Fever Nausea Vomiting
Report Type: Food Poisoning
I ordered to go on 11/14/28 in the evening, ordered Chicken Katsu with brown Rice and side egg roll. I ate almost half the Katsu and sauce, most of the side Salad and my egg roll. Only a few bites of the brown Rice as it was extremely dry. I woke in the middle of the night with severe stomach cramps, fever and sweat dripping off my head and passed out on bathroom floor. Finally was able to pass watery stools and threw up several times. Won't be going back to this restaurant. Read More
Nov 14 10:58pm
Fabiani's Bakery and Pizzeria, East Lipoa Street, Kihei, HI, USA
Symptoms: Diarrhea Fever Nausea Vomiting
Report Type: Food Poisoning
Nov 14 9:22pm
Kneaders Bakery & Cafe, Sergeant Jon Stiles Drive, Highlands Ranch, CO, USA
Symptoms: Vomiting
Report Type: Food Poisoning
My son and I both became sick within several hours after each eating an iced sugar Cookie the night of 11/13. This is the only commonality in what we ate that day, and no one else in our family became ill. By the time I became sick, the only thing left in my stomach was the orange icing of the cookie. Read More
Nov 14 9:12pm
Milo's Hamburgers
Report Type: Food Safety
Nov 14 8:36am
Agave's Mexican Grill Maysville, Maysville Road, Fort Wayne, IN, USA
Symptoms: Diarrhea Fever Nausea Vomiting
Report Type: Food Poisoning
I got Chicken fajitas and was sick the next day, within 24 hours. Horrible diarrhea, vomiting, stomach pains, shakes, body pains and a fever. My son, 18, then had my left overs and was sick within 12 hours with the exact same symptoms. I have not been seen by a doctor so I can not confirm food poisoning, but the symptoms lend to food poisoning and not the flu. Read More
Nov 14 7:36am
Joyride Taco House East, North Gilbert Road, Gilbert, AZ, USA
Symptoms: Diarrhea Nausea Vomiting
Report Type: Food Poisoning
Yesterday my girlfriend and I went to joyride tacos in Gilbert, AZ. We ordered an assortment of different tacos on the menu including carnitas, carne asada, and the standard taco. Within 30 min of completeing our dinner my gf began to feel extremely sick. She began to feel nauseous and sick. Within a hour or two all hell broke loose. She was throwing up every 10-20 min through the night. The throwing up didn't subside till roughly 3am. Right as hers ended, mine began. I've been experiencing diarrhea, and nausea horribly for the last hour. Read More


text:
2 Jun 2015 09:40:08 AM
Martial Arts Fail of the Week: Steven Seagal's Russian "Masterclass" Is a Gift From Above
(Looking like a little more than a glimmer these days, eh Sensei?)
Before we get into this, the glorious return of the Martial Arts Fail of the Week, I'd like to make a couple things clear:
1.) Yes, we here at CagePotato are aware of our long, oft-vitriolic history regarding action movie star, part time police officer/school shooting survival expert, unofficial American ambassador to Russia, tax cheat, and perpetual boil on the ass of MMA, Steven Seagal. We've made fun of him a lot, basically — from his weight gain over the years (see above) to his rambling, hallucinatory, endlessly quotable interview snippets to that time Judo Gene made him sh*t his pants – but can you really blame us? THE MAN CLAIMS TO HAVE INVENTED THE FRONT KICK, FOR GOD'S SAKE.
2.) Despite all we've said about Seagal, we are not too big to overlook the man's well-documented skills and well-earned accolades regarding said skills. He may be a literal shadow of his former self (seriously, has anyone seen him donning anything but black since, like, 2006?), but the fact remains that Seagal is one lethal sumbitch who could probably lay waste to the entire CagePotato staff without (barely) breaking a sweat.
Now that we've gotten all that out of the way, holy shit, you guys, you NEED to see this video of Seagal's recent "martial arts masterclass" held in Russia.Read More DIGG THIS


text:
The U.S. Equal Employment Opportunity Commission
Insurance Giant Deprives Employees of Equal Opportunity, Says EEOC in Lawsuit
PHILADELPHIA - In a significant decision, the federal court here has ruled that Allstate Insurance Company unlawfully retaliated against approximately 6,200 of its employees by requiring them to give up their workplace discrimination claims in order to continue to work as agents with the Northbrook, Ill.-based insurance giant. The EEOC's lawsuit charges Allstate with violating the non-retaliation requirements of several federal laws prohibiting employment discrimination, including Title VII of the Civil Rights Act of 1964, the Age Discrimination in Employment Act of 1967 (ADEA), and the Americans with Disabilities Act of 1990 (ADA).
EEOC's suit alleges that Allstate implemented a mandatory policy at all of its U.S. facilities requiring employees to sign a release waiving all workplace discrimination charges against the company in order to be retained as independent-contractor agents. The effect of the policy, the EEOC says, has been to deprive Allstate employees of equal employment opportunities by attempting to prevent their participation in activity protected under federal anti-discrimination laws. The EEOC also contends that the alleged discriminatory policy was carried out with malice or with reckless indifference to the federally protected rights of Allstate employees who worked as insurance agents in violation of the Civil Rights Act of 1991.
The EEOC's suit was consolidated with Romero v. Allstate, Case No. 01-3894 a private lawsuit which also addresses the issue of retaliation as well as numerous other challenges to company reorganization actions. The Court's ruling also addressed other claims in the Romero case.
In its ruling, the Court held: "It is illegal to either retaliate, or threaten to retaliate, against an employee to prevent him from exercising rights under the EEOC, Title VII, ADEA, ADA, etc. Those employees who did not sign releases were in fact treated less favorably than those who did sign, and the signers had all been threatened with such an outcome if they exercised their right to refuse to sign the proposed release."
"The Court's decision here is monumental," said EEOC Regional Attorney Robert G. Johnson. "It guarantees that employees cannot be coerced by the threatened termination of their employment into giving up their rights under the nation's employment discrimination laws. This decision is crucial to the continued effectiveness of those laws. It sends a strong message to other employers not to try a similar scheme."
"This decision has nationwide significance for virtually all working men and women," said C. Felix Miller, the EEOC's lead attorney on the case. "Had Allstate been allowed to get away with its plan, it would have gutted our country's employment discrimination statutes. The Court by this ruling has told Allstate that it must obey the law. It cannot threaten its employees with the loss of their jobs for refusing to give up their rights."
The EEOC enforces Title VII of the Civil Rights Act of 1964, as amended, which prohibits employment discrimination based on race, color, religion, sex, or national origin; the Age Discrimination in Employment Act, which protects workers 40 years of age and older; the Equal Pay Act; prohibitions against discrimination affecting individuals with disabilities in the federal sector; sections of the Civil Rights Act of 1991; and Title I of the Americans with Disabilities Act, which prohibits discrimination against people with disabilities in the private sector and state and local governments. Further information about EEOC is available on its web site at www.eeoc.gov.
This page was last modified on April 2, 2004.
Return to Home Page


text:
Chestnut Hill, Mass. (April 15, 2010) - An increase in the release of monocytes from bone marrow into the bloodstream predicts how rapidly
AIDS develops in monkeys and the magnitude of monocyte turnover correlates with the severity of brain disease in AIDS, Boston College researchers report in the
current edition of the online journal PLoS Pathogens.
The researchers report the first observation within AIDS of a marker in blood or plasma exclusive to monocytes, which underscores the relationship between innate immune response and the devastating effects of AIDS within the brain. The findings also suggest a potential clinical use of the marker to monitor HIV disease activity, according to Boston College Professor of Biology Kenneth Williams, co-author of the study.
The findings advance the understanding of the role that seemingly protective monocytes play in the deadly progression of HIV and AIDS
in the brain, which is an increasingly critical issue. While mortality rates from AIDS have declined thanks to antiretroviral drugs, AIDS-related dementia
remains just as prevalent, particularly as AIDS patients live longer.
White blood cells that play a critical role in the immune system's response to sickness, monocytes migrate from bone marrow to blood
and, in the case of HIV infection, cross the blood-brain barrier, which normally keeps monocyte levels low in the brains of health individuals. Williams and
his lab study monocytes and their more aggressive infection-fighting form, macrophages.
Williams and his co-authors tracked the journey of monocytes by chemically marking the cells to better follow their movement in primates infected with
simian immunodeficiency virus (SIV).
The study found that the monocytes that were labeled in the bone marrow, and trafficked through the blood, were found in the brain within SIV lesions.
All of the cells with the marker were of a particular subtype of monocyte and macrophage known to be important in amplifying immune responses.
Williams' BC colleague and lead author , Researcher Patricia Burdo, said the study showed the magnitude of cells leaving the bone marrow as seen as marked
monocytes predicted which animals would succumb to AIDS rapidly and at death correlated with the severity of SIV brain disease.
Correspondingly, the research also revealed the presence of a protein, soluble CD163, that is only made by monocytes, linked to monocyte expansion
and therefore predicted disease progression. Burdo said marked monocytes were found in brain lesions, offering further evidence that these infection-fighting
blood cells play a role in the damage AIDS does to the brain.
Contact: Ed Hayward
Boston College
Source: EurekAlert!
...positive attitudes are not simply 'moods'
Site Map
Contact Bradford McIntyre.
Web Design by Trevor
Copyright © 2003-2018 Bradford McIntyre. All rights reserved.


text:
The only win for the Cobras came from Esteban Teran at the No.3 singles spot. He won winning two close sets 7-5, 7-5.
The Cobras next match comes on Monday when they host Lees-McRae at 1:00 p.m. on Senior Day.
Munn/Elsborg (LC) def. James Schroeder/ Esteban Teran (CC) 8-6
Warnholtz/Beanuelos (LC) def. Dustin Yager/
Hogan/ Jacobs (LC) def. Tim Morton/
Munn (LC) def.
Hogan (LC) def. Tim Morton (CC) 6-3, 6-3
Teran (CC) def. Elsborg (LC) 7-5, 7-5
Banuelos (LC) def. Schroeder (CC) 6-2, 7-5
Ross da Silva (LC) def. Hunter Batts (CC) 6-2, 6-1
Jacobs (LC) def. Dustin Yager (CC) 6-2, 6-2


text:
Report No. 11:FC178
Field evaluation of maturity group V late RoundUp Ready soybean cultivars to Cercospora leaf blight, frogeye leaf spot, Septoria brown spot, and target spot in east MS, 2016.
First Author: W.L. Solomon
Additional Authors: T.W. Allen, B.A. Burgess
Section: Field Crops
Geographical location: Mississippi, United States
Products Tested:
Active chemical(s):
Biological Control:
Biorational Product:
Manufacturer(s): Cultivar trial
Publication date: August 4, 2017
© The American Phytopathological Society


text:
James and the Giant Peach: Special Edition (US - BD)
Gabe revisits Henry Selick's film version of Roald Dahl's beloved children's book...
James Henry Trotter (Paul Terry) lives a loving life with his wonderful parents, until they're eaten by a demonic rhino, and he's forced to live with his evil aunts, Sponge (Miriam Margolyes) and Spiker (Joanna Lumley). Sponge and Spiker lock James in the attic and use him as their personal slave. James dreams of escaping to New York City, where his parents were planning on moving before their untimely deaths, and his dreams attract the attention of a mysterious traveller, who gives him a bag of magical alligator tongues. James spills the tongues at the base of a dying peach tree, which causes a single peach to grow to enormous size. One night, while cleaning the giant peach James reveals a magical entrance into the peach, where he meets a group of man-sized insects who were also affected by the magical tongues. Together they journey to the magical land of New York City.
In 1996, when James and the Giant Peach was released in theatres to unfair expectations from a young(ish) Gabe Powers. The original Roald Dahl story was a childhood favourite (as were most of Dahl's books), and director Henry Selick's previous film with Tim Burton as producer, The Nightmare Before Christmas, had reinvigorated the stop motion animation format, and become a rather unique cult item. I now realize director Henry Selick and his screenwriters didn't actually have that much to work with, and that perhaps nostalgia had rose-tinted my memories of the actual story, which is actually one of Dahl's lesser efforts comparatively speaking. The author adapts a handful of overused fairy-tale motifs without ever quite putting his personal stamp on them, and never really finds a proper climax. James and the Giant Peach was one of Dahl's first children's books, and looking over his resume it's evident that he would recycle many of the book's themes in latter stories like Charlie and the Chocolate Factory and Matilda. As an early crack at the formal James and the Giant Peach is just fine, but it isn't the best example of a top author in top form. For better and worse Selick is reasonably true to the material, including its episodic format, which makes it less of a unravelling narrative and more of a series of short adventures that would probably play quite well in the now popular eleven minute animated television format (a James and the Giant Peach series would actually work quite well among Cartoon Network and Nickelodeon's oddball line-ups).
It's hard not to appreciate the film as a work of animation art, both in terms of design and the incredibly detailed attention paid to the animation process itself. Dahl's already surreal story is actually made more idiosyncratic when re-enacted in plastic thanks to Selick and company's non-literal take on the characters. Besides the angled, anthropomorphized insects, I'm most taken aback by the shark design. In Dahl's book, if I recall correctly, the sharks that attack the peach are literally sharks, but in the film there is a single giant shark made up of anachronistic machine parts. There's no reason for Selick to do this outside of unadulterated imagination. Literalists could take these flourishes as clues to the entire film being nothing by James' depressed, escapist fantasy, but I've decided to be a little more optimistic in my reading. The animation doesn't improve much on The Nightmare Before Christmas technically, but there wasn't really a lot of time between productions, and there wasn't a lot of room for improvement anyway. The puppets used don't feature the most expressive faces, but their range of motion is quite expressive. The musical sequences in particular feature some great technical animation. The live action sequences are so Tim Burton-esque it almost burns, and have a vague made-for-television air about them. Dividing the live action and animated elements is respectable, and the Cabinet of Dr. Caligari inspired flat sets are a clever way to deal with a low budget, I just wish Selick would've taken greater pains to make the look his own, like he did with Coraline.
The film's musical properties are probably the most concrete disappointment, whether we're comparing them to tradition Disney animated fair, or Danny Elfman's more unusual work on Nightmare Before Christmas. Perhaps all the songs are too indelibly Randy Newman for my taste, but I cannot recall a single ditty by heart even after half a dozen lifetime viewings. Newman clearly put some effort into his work, but his lyrics are too wordy and literal, his melodies are difficult to anticipate, and nothing he offers connects outside the exact moment they play. I'm frankly kind of shocked Newman got an Oscar nomination out of such mediocre work in retrospect.
It's been too long since I've seen James and the Giant Peach on the big screen, but I don't recall the early scenes being quite this grainy. I recall an image contrast between the 'real world' and the animated world, but nothing quite this extreme. This scenes feature generally more detail than the DVD version, especially in the white faces of James' evil aunts, but the thick grain and depressing darkness keep things pretty muddied. More often than not this 1080p transfer looks more like a blown-up 16mm print than an untouched 35mm print. The disparity between these and the animated sequences aren't exactly cavernous, but fans will likely be more satisfied with the purely stop motion stuff overall. Grain is a constant issue (and we're talking grain here, not compression noise, or digital artefacts), as is overall softness, both of which I'm assuming are inherent in the source material. Certain sequences are sharper than others, and feature higher contrast, but details are generally sharp (look at all the little hairs on that peach) without any unfortunate artefacts. The colour palette changes a lot throughout the film, including some close to monochromatic chunks. Most of the colours are kind of dull, unfortunately, though the poppiest bits stick out nicely against the dirt, grain and general softness, specifically the neon green alligator tongue things.
As per the Disney norm these days James and the Giant Peach comes fitted with a lossless DTS-HD Master Audio 5.1 soundtrack. This is not one of the studio's finest catalogue release efforts, but doesn't feature any humungous problems worth skipping the release over either. The centre channel on this track is inconsistent in terms of volume, specifically where dialogue is concerned. The dialogue is also generally too loud on the mix in comparison to the other elements, and features some minor distortion on the highest levels. The stereo and surround channels get in on the action more often than I expected. There aren't many ambient sounds during dialogue heavy sequences, but the action heavy set pieces feature plenty of aggressive directional and immersive qualities. Prime examples include the scene where the peach rolls down the hill and into the ocean, the shark attack (which ends in a pretty massive boom), the pirate fight (which features characters being thrust across screen, and plenty of underwater echoes), and the effects heavy storm-rhino attack. Randy Newman's music is a nearly unflappable aural element, filling just about every ounce of the overall soundtrack, and standing in for natural ambience at every turn. The sung moments are reasonably balanced (though the dialogue volume levels continue to be inconsistent), but the bulk of the score is presented rather softly in the stereo channels.
The only new extra offered up for this 'Special Edition' Blu-ray release is the 'Spike the Aunts Game', which is based on the brief post credit gag. The object of the game is to spike the evil aunts in the bottom with a metal rhino. Each spike makes them spin faster and the better the player measures the time between button-mashing the stronger the spike will be. It's not very fun, and each game only lasts thirty seconds. The original DVD features are included on their own sub menu, and include a brief production featurette/EPK (04:30, SD), 'Good News' music video (02:30, SD), a still gallery, and the original theatrical trailer.
James and the Giant Peach is an artistic achievement, like all of Henry Selick's films are on some level (yes, even, shudder, Monkey Bone), and is a fun film to revisit every once and a while, but isn't magical, and is woefully easy to forget. Videophiles will likely be disappointed with this grainy, soft, and occasionally flat out dirty looking transfer, but I can't honestly say it isn't the intended look, at least partially. The DTS-HD track suffers some minor inconsistencies all its own, but is generally pretty impressive. Despite the special edition title the extras don't amount to much more than the original DVD's EPK, a music video, trailers, and the added fun of a not very fun game.
* Note: The above images are taken from the Blu-ray release and resized for the page. Full-resolution captures are available by clicking individual images, but due to .jpg compression they are not necessarily representative of the quality of the transfer. Thanks to Troy at Andersonvision.com for the screen-caps.
Review by Gabriel Powers
Existing Posts
This was a good movie. God it's been a while since I saw this.
Some material may not be suitable for children
Disc Details
Release Date: 3rd August 2010
Discs: 2
Disc Type: Blu-ray Disc
RCE: No
Video: 1080p
Aspect: 1.66:1
Anamorphic: No
Colour: Yes
Audio: DTS-HD Master Audio 5.1 English, Dolby Digital 5.1 French and Spanish
Subtitles: English SDH, French, Spanish
Extras: Spike the Aunts Game, Behind the Scenes, Good News Music Video, Trailer, DVD Copy
Easter Egg: No
Feature Details
Director: Henry Selick
Cast: Paul Terry, Simon Callow, Richard Dreyfuss, Susan Sarandon, Jane Leeves, Miriam Margolyes, David Thewlis, Joanna Lumley
Genre: Adventure, Animation and Musical
Length: 79 minutes
6Review Guide
Follow our updates
Hot Interviews
David Hayter US - DVD R1 | BD RA Tim Lucas DVD Ricky Gervais Part One DVD Mark Rance DVD Lancelot Narayan DVD
Unseen Reviews
Doctor Who: Scream of the Shalka UK - DVD R2 Stuff, The UK - BD RB Body Double UK - DVD | BD Capricorn One UK - BD RB Fog, The UK - BD RB
Past Reviews
Cary Grant: 4-Disc Collector's Set US - DVD R1 Miami Vice: Season One US - DVD R1 Two Weeks Notice US - DVD R1 Stanley Kubrick: Visionary Filmmaker Collection Technical Review UK - BD Venture Bros. Season 4 US - BD RA
Most Talked About
A Simple Favor US - DVD R1 | BD RA All the Colors of the Dark US - DVD R1 | BD RA Reign of the Supermen US - DVD R1 | BD RA Kino Lorber Studio Classics January US - DVD R1 | BD RA Columbo Season 1 UK - BD RB


text:
Upon entering Peninsula Counseling Center's "The Club," at St. Joseph's Church in Hewlett, three women talk amongst themselves as they wait patiently for their husbands, who are busy dancing down the hall to Van Morrison's,"Brown Eyed Girl."
Patricia Crowley is waiting to greet her husband, Richard, who has suffered from dementia since 2006 when he had his first stroke, and another in 2010. She's been bringing him to "The Club," a social day-program for men and women, age 60 and over, who are frail due to mental or physical difficulties, for the past seven years. "It's my only salvation; it gives me five hours of peace two times a week," the Valley Stream resident said. "He loves it, even though he has no idea where he's going."
The group, which meets Mondays and Wednesdays for women and Tuesdays and Thursdays for men, has been around since 1984 and is funded through the Nassau County and New York State offices for the aging, according to Director Ellen Tolle. "It gives participants the opportunity to interact with each other, play cards, exercise, sing and dance," she said.
Aside from entertaining the participants for the day, Tolle said families attend monthly support meetings. "We offer individual counseling and do home visits to perform a safety check," she said. "We're here to make sure they can do everything and can succeed."
Talking to those who are going through the same thing, according to Crowley, is special, as most people don't understand what the families of those suffering from mental illnesses go through. "We get to talk about what's going on and we're able to meet others who are experiencing the same problems," she said.
Lorraine Nordlund, a Long Beach resident and social worker at "The Club," facilitates the monthly support group meetings. "It's important for caregivers to have emotional support, a shoulder to cry on and someone to rant and rave to," she said. "No one understands what they're going through unless they're in their shoes."
Merrick resident Ramona Grimm has been taking her husband, Allan, to "The Club" for the past three months after she read about the program in the Nassau County Senior Directory. "I love it, for him and me," she said. "Allan won't get off the couch and get dressed most days but he'll come here."


text:
driven by our passion for travel, the agoda team works hard to bring you the cheapest prices on hotels, resorts, unique homes, vacation rentals, and more. our huge selection of accommodations will let you plan the perfect trip. from adventure travel and backpacking to honeymoons and family vacations, we"ve got you covered.
find the perfect place to stay. read honest reviews from the agoda travel community.
nobody works harder to get you the best price. and if you find one lower, we"ll refund you the difference.
available in 17 languages. all day, every day, we"re here to help you.
agoda consistently finds the most lodging options and lowest prices, especially internationally.


text:
The Ravens made it official, signing 14 undrafted rookies to contracts.
They also waived running back Lonyae Miller and officially announced six rookie contracts previously reported by The Baltimore Sun: fourth-round fullback Kyle Juszczyk (Harvard), fifth-round offensive tackle Rick Wagner (Wisconsin), sixth-round defensive end Kapron Lewis-Moore, sixth-round center Ryan Jensen (Colorado State-Pueblo), seventh-round wide receiver Aaron Mellette (Elon) and seventh-round cornerback Marc Anthony (Cal).
All of the draft picks are signed to four-year deals with the following values: Juszczyk ($2.46 million total, $300,584 signing bonus), Wagner ($2.304 million total, $144,560 signing bonus), Lewis-Moore ($2.248 million total, $88,232 signing bonus), Jensen ($2.238 million total, $78,680 signing bonus), Mellette ($2.205 million total, $45,896 signing bonus) and Anthony ($2.205 million, $45,896 signing bonus).
They've now spent $2.605 million, 47 percent of of their allotted $5.517 million rookie pool. That leaves $2.911 million remaining to sign first-round safety Matt Elam, second-round linebacker Arthur Brown, third-round defensive tackle Brandon Williams and fourth-round outside linebacker John Simon.
Here are the undrafted free agents: offensive guard Jeff Braun (West Virginia, Winters Mill), cornerback Jose Cheeseborough (Florida International), outside linebacker Brandon Copeland (Penn, Gilman), offensive tackle Jordan Devey (Memphis), tight end Matt Furstenburg (Maryland), offensive tackle Rogers Gaines (Tennessee State), wide receiver Omarius Hines (Florida), running back Ray Holley (Louisiana Tech), tight end Murphy Holloway (Ole Miss), defensive end Will Pericak (Colorado), wide receiver Gerrard Sheppard (Towson, McDonogh), quarterback Nathan Stanley (Southeast Louisiana), Troy safety Bryden Trawick and offensive tackle Joe Unga (Midwestern State).


text:
Water System
Wright State University operates its own public drinking water system that draws water from the Mad River Buried Valley Aquifer. The Water Treatment Plant has been supplying drinking water to the university since 1977. Wright State meets and usually exceeds the requirements of the Environmental Protection Agency. A report about the water quality titled the Drinking Water Consumer Confidence Report is created and disseminated annually to the campus community. This report contains general health information, water quality test results, potential sources of drinking water contamination, and persons to contact regarding the Wright State water system. This report is required by the 1996 amendments to the Safe Drinking Water Act. Regulations governing the content and other requirements for this report can be found in Federal rule 40 CFR 141.151 through 155. We have a current, unconditional license to operate our water system.
Water drawn from the wells is treated at the Water Treatment Plant by aeration, iron and manganese filtration, water softening, and chlorine disinfection. The Water Supply Plant is operated and maintained by university employees certified by the Environmental Protection Agency. The Wright State University Department of Environmental Health and Safety oversees the required sampling and analysis of the drinking water. In 2009 the Water Supply Plant produced 78.8 million gallons of potable water for the university. The Water Supply Plant supplies drinking water to Wright State main campus buildings, Hamilton Hall, and the Rockafield House. Forest Lane and other student resident apartments receive their water from the City of Fairborn.
Wright State University is required to conduct sampling for certain bacteria, inorganic, synthetic organic, volatile organic and radiological contaminants as set forth by the EPA. Over the last five years (the required reporting time frame of this report) samples were collected for over 105 different contaminants (some more than once), most of which were not detected in the drinking water supply. Over 794 water samples were taken in 2009. The EPA also requires certain operational data to be monitored by water plant personnel. This includes water volume production rates, hardness levels, iron and manganese levels, and levels of chlorine in the water for disinfection. Information on operational data can be obtained by contacting the Facilities Operations Department.
Wright State University has an emergency connection with the City of Fairborn for use during emergency conditions and only after approval from the city. Such emergencies include, but are not limited to: power failures, fires, maintenance or repairs, and severe drought. On average this connection is used three times a year with each use usually less than eight hours in duration. This report does not include information on the water supplied from the City of Fairborn. A copy of Fairborn's Consumer Confidence Report can be obtained by contacting the Fairborn Water Department at (937) 754-3097.


text:
Best Acoustic Guitars on a Budget
Best Budget Acoustic Guitars
Are you after a simple and traditional instrument for someone special this year... no amps or leads necessary? Then one of these traditional acoustic guitars might be just what you need.
All of these guitars are in stock now!
Order Today for FREE Next Day Delivery!*
Yamaha FG700S Acoustic Guitar
One of the best, and most affordable acoustic guitars we have to offer is the Yamaha FG700S, which is available to purchase alone, or with either a stand or a gigbag. See here.
The Yamaha FG700S is a superb beginners instrument, it features a dreadnought body and folk style gloss finish giving it a real acoustic feel. The FG700S also features die cast tuners and, like some high end instruments on the market, has been given a spruce top and rosewood fretboard for a beautifully rich tone.
Many mightn't think that a guitar's finish would affect the sound... but they'd be wrong. The FG700S boasts a high gloss finish on its top, back and sides, which actually creates a rounder, more mellow tone. This combination of top quality materials give the Yamaha FG700S a warmer sound than you're average acoustic, making it ideal for rhythmic playing styles.
Eastcoast SS-63 Acoustic Guitar
If you're looking for a less costly guitar still, then maybe take some time to look at the Eastcoast SS-63. The Eastcoast brand produces some of our best selling entry level instruments. So if it's a nice sounding, easily playable great value for money guitar that you're after, then look no further than the SS-63. Available in the traditional acoustic natural finish, this guitar features a rosewood fretboard and bridge for a warm, smooth sound.
There are a couple of bundle packages available for this guitar. If you're interested in getting a few accessories with your guitar. A capo, a strap or string winder for example... Take a look at our SS-63 bundles here.
Ibanez AW250 Dreadnought Acoustic Guitar
Plucked from the Artwood Series, this beauty is a real chameleon, suitable for both pros and beginners alike. This dreadnought acoustic has been crafted with traditional looks at the top of Ibanez's agenda. While still incorporating modern features and innovations, Ibanez have managed to retain the rich heritage of the acoustic guitar.
You will find an attractive combination of iconic characteristics in each model of the Artwood Series. See the Artwood Series here.
Epiphone Hummingbird Pro Acoustic Guitar
Being one of the best-selling guitar brands for the pro's, you maybe didn't expect to see this guy in our best budget acoustics list. The Epiphone Hummingbird is an exquisite work of the luthier's art in every respect. From tone and playability to it's striking appearance the Hummingbird couldn't disappoint if it tried.
The Epiphone Hummingbird's select mahogany body with a solid spruce top projects rich tone that improves with age, and the bound rosewood fretboard is delicately crafted for effortless chording and soloing, and as for the pickguard, the artistry simply speaks for itself.
More Value Guitar Buying Guides
Budget Electro-Acoustic Guitar & Amplifier bundles
Guitar Starter Packages for Christmas
The Most Affordable Les Paul Guitars from Gibson & Epiphone
*FREE Delivery is available during Mon-Fri on orders placed before 3pm. Available with in-stock products only. Free Delivery is to UK mainland only on orders under 32kg. All orders placed outside of UK Mainland are exempt from free delivery. Terms & Conditions here.
Related Products
Eastcoast SS-63 Acoustic Guitar - Natural
Includes D'Addario Brand Strings Eastcoast SS-63 Solid Top Acoustic Guitar Package Specifications: Top: Solid Spruce Back & Sides: Mahogany Neck: Nato Fingerboard: Rosewood Bridge: Rosewood Neck & Body Binding: Black Headstock Veneer: Mahogany Soundhole: White pearloid inlay Machine Heads: Diecast nickel w/ white pearloid button Pickguard: Brown Finish:…
Web Price:139.00
Availability:Call 0844 815 0888


text:
So here's a list of the QBs in the playoffs this year.
Peyton Manning, 15th season
Tom Brady, 13th season
Matt Shaub, 9th season
Aaron Rodgers, 8th season
Joe Flacco, 5th season
Matt Ryan, 5th season
Andy Dalton, 2nd season
Colin Kaepernick, 2nd season
Christian Ponder, 2nd season
Robert Griffin III, 1st season
Andrew Luck, 1st season
Russell Wilson, 1st season
Half of the starting QBs in this year's playoffs are in their first or second season. That amazes me.


text:
After the Bruins lost to Pittsburgh Saturday at TD Garden, coach Claude Julien commended his team's effort and lamented the club's inability to once again score enough goals to make the performance result in two points.
Julien also took exception to the play of a couple Penguins who've been getting under the Bruins' skin for years now.
Late in the second period, Penguins forward Matt Cooke — who's mostly made his name for his hobbling hit on Marc Savard and several suspensions against for acts against other teams over the years — hit Adam McQuaid low in the neutral zone on a dump-in. Cooke turned his back as his made contact with McQuaid's leg. The Boston defenseman left the game and returned to play the third period. Zdeno Chara picked up a roughing penalty for going after Cooke.
The Penguins took the lead on a Jarome Iginla power-play goal after Brad Marchand was called for roughing. Marchand tried to fight Jussi Jokinen, but all the Boston wing accomplished was pulling Jokinen's sweater over his head because the Penguins forward wouldn't accept the fight invitation.
For the game, the Bruins allowed two goals on six Pittsburgh power plays. Julien didn't fault his team's penalties in the above-mentioned situations.
"We took some penalties," Julien said. "But it's pretty obvious that it's a cheap shot from Cooke. The typical, same guy, he's got to go low, get a guy right around the knee area and turns his back. And the same thing, Jokinen's been having his stick high all game and the guys eventually get it. You always hope you have people that will see those kind of things and call it right. And that's not in our control."


text:
Have you ever had to rush to the restroom to keep from wetting your pants? We think of this as a child's problem, but adults also can suffer from what doctors call urinary urgency.
Have you ever had to rush to the restroom to keep from wetting your pants? We think of this as a child's problem, but adults also can suffer from what doctors call urinary urgency.
Urgency, leaks and frequency together make up overactive bladder (OAB) syndrome. These symptoms overlap with those signaling conditions like urinary-tract infections or interstitial cystitis that call for medical attention.
Drug companies have made OAB into a household word, however. TV commercials for prescription drugs like Detrol feature people who need a pee break in the most embarrassing situations.
The Food and Drug Administration recently decided that symptoms of overactive bladder could be treated without a prescription. The agency approved a drug called Oxytrol. The active ingredient, oxybutynin, has been sold by prescription as Ditropan. Oxytrol will be a patch rather than a pill.
Most people like the idea of easy access to drugs that were once prescription-only. Add to that the embarrassment factor for OAB, and it is likely that Oxytrol will sell well.
There are problems with such switches, however. People often assume that nonprescription drugs don't have serious side effects, but that can be a dangerous assumption.
We are surprised and dismayed that the FDA decided to approve nonprescription oxybutynin. Common side effects include dry mouth, dizziness, constipation, drowsiness, nausea, headache, blurred vision, difficult urination, upset stomach, jitteriness, dry eyes and insomnia.
Oxybutynin also could cause some really dangerous reactions, including hallucinations, psychotic reactions, seizures and heart-rhythm disturbances. In addition, the drug may raise blood pressure and increase the risk of glaucoma.
The consequence that worries us the most, however, is confusion. Oxybutynin and similar medications work by blocking a nerve-messenger chemical called acetylcholine. Scientists call them anticholinergic drugs. They can cause mental fogginess in susceptible people. While the elderly are especially vulnerable, you don't have to be old to experience cognitive problems.
One reader wrote: "I am a 49-year-old female who has been on Ditropan for a few years. I had my family doctor refer me to a psychiatrist because I was having much more trouble remembering things.
"On my first visit to the specialist, I gave her a list of all the medications I was on. (I was taking six medications and had to write them down, as I could never remember them.) As soon as she saw the Ditropan, she told me that confusion is a side effect.
"I never even tied the two together. The bladder and the head are rather far apart! I immediately stopped taking the Ditropan and felt much better right away. I was attributing my depression and confusion to menopause. It worries me that there could be thousands of people suffering and not making the connection."
We are concerned about OTC availability of oxybutynin. Memory loss and confusion are hardly a fair trade for fewer trips to the bathroom.
Write Joe Graedon and Teresa Graedon via their Web site: www.PeoplesPharmacy.com.


text:
SYCAMORE – In 2001, Greg Howells went to Bolivia with his sons, Jacob and Joel. It was a trip he wouldn't soon forget.
"That was the first I experienced severe poverty," Howells said of his trip, the first of many. "It has an impact on you when you see it, smell it, feel it, experience it."
His experience eventually inspired Howells and his wife, Sherri, to organize the first Feed My Starving Children event at Cornerstone Christian Academy at 355 N. Cross St. in Sycamore in 2010.
Among the people who helped out during "Make a Difference 2K10" was Tim Suter, the president and CEO of The Suter Company, a food manufacturing company in Sycamore. Suter reached out to Howells, telling him that if he ever planned to do the event again, he could do so at his company's facility at 1015 Bethany Road.
"I knew our facility would have the perfect layout," Suter said.
Enter Make a Difference 2K12: a four-day weekend in which over 3,700 people will donate their time and energy to pack at least 750,000 meals to feed starving children in 70 countries.
Suter expressed hope that they would pack at least 800,000 meals; the event's Thursday night projection of 187,500 meals packed was exceeded by at least 17,000.
On Friday, two shifts of 320 people gathered onto the main floor of The Suter Company in Sycamore, hoping to pack at least 125,000 meals in four hours. Each meal, said Heidi Wright, vice president of marketing and sales at The Suter Company, feeds six children.
A Christian nonprofit organization, Feed My Starving Children has permanent sites in the Midwest, but volunteer organizers like the Howellses set up mobile pack sites for the agency.
"We're providing meals to kids who, without these meals, would die," Howellis said.
By 5 p.m. Sunday, volunteers at the DeKalb-Sycamore FMSC events will have packed at least 2.1 million meals since the event's inception in 2010. They also will have raised over $500,000 for it as well, Howells said.
"As long as there are starving children in the world, our fundraising efforts will never end," Howells said.
Getting volunteers for the event is easy. Howells said the event "sold out" within the first day. The volunteers are divided into groups of 10 to 12, and each person is given a specific job at their station. Some will pack in rice and soy, while others seal the meal packs.
Wright said each meal pack contains rice, soy, vegetables and a veggie powder loaded with vitamins and nutrients.
"These meals have the ability to dramatically reduce malnutrition," Wright said. "All they need to do is boil water."
Jasmine Maclin, a freshman elementary education major at Northern Illinois University, scooped a certain amount of rice and soy into the many meal packs they had. Each group works an assembly line with everyone doing their own part.
"Some people lose sight of the greater things we have in life," Maclin said. "It's good to step up and realize people have much less than you."
Maclin was one of 43 people from NIU's track and field team to volunteer at FMSC, said head coach Connie Teaberry. Teaberry said events like these are "about being helpful, being humble and giving back."
"Our team, our staff agreed that we don't want anyone to be hungry," Teaberry said.
That desire to help others is what lead 12-year-old Nolan Govig and 13-year-old Allie Schneider to volunteer for Feed My Starving Children twice this weekend. In addition to their Friday night shifts, Govig said he volunteered Thursday, while Schneider said she will volunteer again Sunday.
"I feel like this is where we should be helping starving children," Govig said.


text:
Posted Sun April 28th, 2013 - 11:08 AM PDT
Michael Buble was spotted at LAX in a black leather jacket. The crooner was quickly surrounded by autograph seekers and fans hoping to get a photo with him.
©2018 X17 Inc., All Rights Reserved
Help us to improve! Send us your suggestions


text: What a wonderful place. The villas are beautiful, (we stayed in Palm 2) and everything from the rooms to the gardens is perfectly kept. The location is also perfect. You could completely avoid the rat-race should you choose the villas are perfect & quiet, however you're just around the corner from the heart of Seminyak's trendy shops and delicious restaurants.... More


text:
Best sellers list of Cushion massager is one of the trusted and recommended list to check out for before buying any Cushion massager.
The list presents most popular choices people are making while selecting one for them and can be trusted by you as well.
When you have no idea of what to select from the available list of different brands and various products then this is the list which you should trust on while buying any item.
Here is the best selling Cushion massager to buy from online in India which could help you with your selection process.


text:
The Representative APR is 10.5%
(fixed) so if you borrow £7,500 over 4 years at a rate of 10.5% p.a. (fixed)
you will repay £190.31 per month and repay £9134.88 in total.
CarFinance 247 Limited is acting as an independent credit broker.
This advert is for an Audi A4, click
Audi A4 in Beauly
to see more cars like this in the local area.
Want to search further afield? Click
Audi A4 in Inverness
to search for similar cars in the wider Inverness area.


text:
Express Checkout
We know your time is valuable, and now you can save more of it! As a registered member, all your information is stored for you so you can click through checkout with ease!
Promotions & Offers
You will have the option to receive information about our special offers and promotions. Our emails and catalogs will keep you updated on great deals for what's new and what's hot!
Receive 25 Free Reward Point
Receive 25 reward point™ FREE just for registering! Every purchase earns you rewards and every items is worth different amount of reward point. So, remember, the more you shop, the more you earn.
Fischer Flowers deliver sympathy flowers to Lowenstein's Funeral Home 7 days a week. Sending Sympathy Flowers and gifts during such a difficult time is a wonderful gesture of your thoughts and feelings. Take your time and view the many items we offer or call for more personalized assistance, our floral designers are standing by for you now. Flowers can convey what words cannot...allow us at Fsicher flowers to assist you express your ever caring thoughts.
Browse our latest selection of floral designs for the casket. We've added a new selections of...
Time tested, beautiful funeral and sympathy flowers for the home.
Funeral flower arrangements for a friend or loved one.
Parsels Funeral Home Flower Delivery |
Florist Greenidge Funeral Home | Gormley Funeral Home | Mikal's Funeral Parlor | Roth-Goldstein's Memorial Chapel
AtlantiCare Regional Medical Center, City Campus
Gallaway and Crane Funeral Home
Gardner Funeral Home | Underwood Memorial Hospital
Our Lady of Lourdes Medical Center
Our Lady of Lourdes Medical Center
Flower Delivery Lowenstein's Funeral Home | Wimberg Funeral Home
AtlantiCare Regional Medical Center – Mainland Campus
Bayview Cottage Flower Delivery
Our Lady of Lourdes Medical Center
Adams-Perfect Funeral Home | Jeffries and Keates Funeral Home |
Middleton Stroble & Zale Funeral Home
Langley Loveland Funeral Home | Underwood Memorial Hospital


text:
Legal Question in Criminal Law in Mississippi
I retained a criminal attorney 2 months ago. I paid the agreed retainer fee by check. For 2 months, he updated me with details from the DA's office. Less than 1 month before the actual trial date, he has informed me that he will no longer work my case. He decided to quit after he informed me of some legal misconduct regarding my case. When I asked him to report the conduct, he decided to quit. He says he doesn't want anything to do with my case and he will not be reporting the misconduct because legally he does not have to. He says he does not have to officially withdraw from my case, because it's my tough luck that he never filed a notice of appearance. What can I do at this late date?
1 Answer from Attorneys
You should immediately take steps to hire alternate counsel. Ask his advice concerning the prospect of obtaining a partial refund from the first Attorney and ask his advice concerning the nature of the alleged "illegal conduct" discovered in the case. You did not explain in enough detail the nature of the illegal conduct nor did you identify the actors allegedly involved therewith thus it is impossible to render an accurate opinion on that issue.
Related Questions & Answers
Can you have charges placed upon you after being released by police Asked 6/16/13, 10:02 pm in United States Mississippi Criminal Law
Iwas violated for nothing the courts never stated how I violated what can I do Asked 6/13/13, 3:12 am in United States Mississippi Criminal Law