text:
Posted on 12/16/2013 10:52:52 AM PST by Theoria
New evidence suggests that Noah's Ark was round, made from reeds and the length of six double-decker buses.
For years, archaeologists have scoured the world for factual evidence for the Bible story of Noah's flood, but due to scant documentation, many believe the fable to be an Old Testament myth.
Now, however, a new book claims that Noah's Ark was a round coracle and looked very different from its traditional image.
In The Ark Before: Decoding the Story of the Flood by Irving Finkel, there are claims that the vessel had two decks with cabins for the animals.
British Museum expert Dr Irving Finkel reveals how decoding the symbols on a 4,000-year-old piece of clay enabled a new interpretation of the Noah's Ark myth.
The evidence comes from a 4,700-year-old tablet of clay covered in cuneiform writing, which contains "detailed instruction manual for building an ark," says Finkel, an assistant keeper of the ancient Mesopotamian script, languages and cultures department at the British Museum.
Finkel, an expert in deciphering ancient cuneiform script, discovered the text contained instructions for building a round coracle 65 metres in diameter, with walls six metres high. It was apparently made from ropes and rushes waterproofed with bitumen, and the animals were loaded "two by two", according to the Sunday Times.
The tablet was originally found in the Middle East by Leonard Simmons, who served in the RAF from 1945-48. However, the ancient artefact wasn't subject to any research until Simmons's son Douglas took it to the British Museum in 2008.
(Excerpt) Read more at ibtimes.co.uk ...
Noah's Ark is a story to scare followers
Kon Tiki!!!
I will stick with the detailed instructions described in the Book that God gave to us.
Genesis 6:14-16 Make thee an ark of gopher wood; rooms shalt thou make in the ark, and shalt pitch it within and without with pitch. And this is the fashion which thou shalt make it of: The length of the ark shall be three hundred cubits, the breadth of it fifty cubits, and the height of it thirty cubits. A window shalt thou make to the ark, and in a cubit shalt thou finish it above; and the door of the ark shalt thou set in the side thereof; with lower, second, and third stories shalt thou make it.
Ya....everyone knows there are no consequences for their behavior!
So, you're going with the "we descended from apes" thing?
"Noahs Ark is a story to scare followers"
Never scared me. Never scared anyone that I know of. Maybe you scare easy?
...and yet every major culture has a Flood myth.
Like it was a common part of everyone's oral tradition or something.
Good point,
el cid.
why get caught chasing down a dream?
Or, Noah's Coracle Was a Massive Double-Decker Ark.
I love how some people still try to pawn off the flood as a mere story, an allegory. If the flood was a fable then why is there fossilized evidence of sea life all along the top of the Himalayas, including at the Mt. Everest? Why have marine life, such as entire whale skeletons been uncovered in the middle of the desert?
There are none so blind as those who refuse to see.
What's a cubit?
And it worked. In those days "Noah moved with fear in preparing the ark" and those who shinned on the story drowned.
Odd that over 100 cultures scattered throughout the World (Australia, the South Pacific, North America, Europe, Asia, Africa, South America, etc) have a similar story: Mankind wiped out due to a flood, with only a handful of people surviving on a boat/ark/log.
It is a story based on fact. And given that the promise after-wards was that the world would never again be destroyed in a Flood (Genesis 8:21b And the LORD smelled a sweet savour; and the LORD said in his heart, I will not again curse the ground any more for man's sake; for the imagination of man's heart is evil from his youth; neither will I again smite any more every thing living, as I have done)-- what is the 'scare' aspect?
'Hell' is the story that you may have wanted to reference as a scare tactic. In this case, reasonably based fear (e.g., 'I am afraid to jump in that blazing fire. It might hurt a bit').
Length between a man's bird finger and his elbow
Does it matter?
Do you plan on building an Ark? Our Ark is the Lord Jesus Christ -- you need to be in Him if you want to be safe.
Most people estimate a cubit at one and half feet - but no one knows for sure.
Classic Bill Cosby. :-)
How long can you tread water?
He was quoting Bill Cosby. It's okay.
it strikes me as rather matter of fact that there would be MANY so called myths about the REAL FLOOD..and yet....those who need to dismiss the Biblical account seem to miss that every time they go on about it
Because the rocks presently at the top of the Himalayas were underwater for various periods till the Indian tectonic plate drove under the Eurasian plate, pushing up the Himalayas?
They're still going up, BTW. About 5 mm a year, or about 16 feet per century.
Just remember that Noah saved the animals so we could keep eating meat later.
Noah. The original prepper.
You're kidding, right? Google "Nicolas Steno". Better yet, read "The Seashell on the Mountaintop".
Interesting point - eating meat wasn't "allowed" until AFTER the flood...
2 of every animal... so they make meat babies
Very true!
Whenever I go into Home Depot and ask for a fifty cubit tape measure, they just look at me funny.
That sounds familiar...
Oh, yeah... liberals. And Satan.
you will not surely die
I;ve always given credence to the idea that the breach of the bosporus at the end of the last ice age (possibly in reaction to the collapse of the land bridge connecting britain and france) and the subsequent inrushing of water into the Black Sea basin was a pretty good basis for the origins of the biblical flood story, that has so many resonances around the mythologies of the ancient world. For better or worse, the Bible does attempt to be a history of the world, and over the tellings of millenia, details will have changed, but the physical evidence for massive movements of water courses when the ice age ended are really strong.
That goes waaay back... I vaguely recall that skit from the mid-1960s (I think). After re-reading the post -- it does sound like Cosby.
I don't think that's true
Scientists Discover Massive Freshwater Reserves Underneath The Ocean Floor
As far as Noah's ark....apparently Noah didn't survive. No Noah = no one to tell the story.
In the previous verse, God tells Noah that the animals will now fear man, also implying that they didn't before.
You can eat them now, but I'm not going to make it easy!
How did a Christian mocking, Hillary Clinton lover wind up on Free Republic?
and bacon and eggs...
so so true
The Mediterranean Sea filling back up was a big flood.
The Flood story is repeated across many civilizations, and the Mediterranean was once a lowland that flooded as sea levels rose. I can see the basic story being true, I think the guy was a prepper and took farm animals on the boat...when all you see is water on the horizon, to you the whole world IS flooded, but really you're just the first cruise ship on the Mediterranean.
did Noah also save all the veggies?
I was thinking that the animals deemed "clean" that were brought on the earth were also for food. That is, people were eating animals before the flood. That was why Noah brought seven of those kinds on board with him.
Have ya looked in the bottom of the ark? Who's gonna clean up that mess down there???
You must read and watch the videos. The story of Ron's live and how he was let to discover not just the ARK but many other biblical archaeological sites is truly amazing!
Never mind the size of the Ark - how did he keep the animals from killing each other & the humans? And where did the waste go? That must have been a full-time job right there.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.


text:
. Please
1 Hour
1 Day
1 Week
1 Month
Login with username, password and session length
The Briefing Room
General Category
National News/Current Events
Report: agencies failing at FOIA
« previous
next »
Send this topic
Pages: [
Go Down
Topic: Report: agencies failing at FOIA (Read 182 times)
0 Members and 1 Guest are viewing this topic.
America defending Veteran
TBR Contributor
Hero Member
Posts: 57,025
"It's easier to fool people than to convince them
Report: agencies failing at FOIA
March 12, 2014, 07:03:57 AM »
Report: Agencies Failing at FOIA
Half of federal agencies have failed to meet transparency obligations
BY: CJ Ciaramella Follow @cjciaramella
March 11, 2014 4:00 pm
Half of the federal agencies handling the bulk of Freedom of Information Act (FOIA) requests are failing at their transparency obligations, a government watchdog group reported Monday.
The Center for Effective Government surveyed the 15 federal agencies handling 90 percent of FOIA requests and found none of them were performing well.
No agency earned an overall "A" grade, and seven received failing grades.
"The fact that no agency achieved a top grade across all three areas illustrates the difficulty agencies are having with implementation overall," Katherine McFate, president of the Center for Effective Government, told McClatchyDC. "Agencies face a variety of challenges, depending on their request loads, the kind of information they manage, and the manpower they have available to do the job. But there is clearly much room for improvement."
The Center for Effective Government measured agencies' performance in three areas: processing requests, establishing rules, and creating user-friendly websites.
The report was cited in a Senate Judiciary Committee hearing Tuesday on reforming the Freedom of Information Act.
"We are moving in the right direction, but stubborn impediments to the FOIA process remain in place and progress has come much too slow," Judiciary chairman Patrick Leahy (D., Vt.) said. "I am concerned that the growing trend towards relying upon FOIA exemptions to withhold large swaths of government information is hindering the public's right to know."
However, testifying before the Judiciary Committee, the director of the Justice Department's Office of Information Policy, Melanie Pustay, said federal agencies had improved their FOIA performance.
"Based on our initial review of those reports for 2014 and our review of agency Annual FOIA Reports for Fiscal Year 2013, it is clear that agencies have persevered through a difficult year of limited resources and tough fiscal times to meet the ever-increasing demands of their FOIA administration and to continue to improve public access to information," Pustay said.
Pustay said agencies continued to decrease their backlog of FOIA requests and improve their websites.
Pustay also said that, in addition to the Obama administration's two-year "Open Government National Action Plan," the Justice Department is working with agencies to modernize their FOIA offices and establish the best practices across the federal government.
President Barack Obama pledged to run "the most transparent administration" in history when he took office, and has often repeated this line throughout his time in office, but transparency advocates say Obama's reforms have fallen flat.
Daniel Metcalfe, a law professor and executive director of the Collaboration on Government Secrecy at the American University Washington College of Law, told the Judiciary Committee that the transparency community "has been disappointed by the surprising inadequacies of the Obama Administration's implementation of new FOIA policy."
The House unanimously passed a bipartisan FOIA reform bill last month introduced by Oversight Committee leaders Darrell Issa (R., Calif.) and Elijah Cummings (D., Md.).
There is currently no Senate version of the bill.
Last Edit: March 12, 2014, 07:04:49 AM by rangerrebew
There is danger from all men. The only maxim of a free government ought to be to trust no man living with power to endanger the public liberty.
Public virtue cannot exist in a nation without private, and public virtue is the only foundation of republics. There must be a positive passion for the public good, the public interest, honour, power and glory, established in the minds of the people, or there can be no republican government, nor any real liberty: and this public passion must be superior to all private passions. John Adams
Send this topic
Pages: [
Go Up
« previous
next »
Share me
The Briefing Room
General Category
National News/Current Events
Report: agencies failing at FOIA

subset: commoncrawl


text:
Challenging economic times present opportunities for those who know how to take advantage of them. Executives and planners looking for the best ways to motivate employees and run an incentive program during the recession will want to pick up Incentive's Complete Recession Survival Guide, now available on Incentive's Digital Mall.
This extensive, four-volume Guide is an expanded version of Incentive's February 2009 issue, which includes not only all of the expert insight, strategies and research from that special print edition, but a wide range of additional exclusives not available in print or online.
The Complete Recession Survival Guide includes:
Volume I: The Road to Recovery
* An illustrated map of how we got into this financial mess, in 16 steps
* Strategies for executives running dealer sales, engagement and consumer incentive programs
* Examination of each of the seven major industries utilizing incentives and what smart executives are doing to make their programs succeed
* Expanded responses from the members of Incentive's Editorial Advisory Board, discussing what they're advising their clients to do and how the industry as a whole can turn these challenges into opportunities
*And much more
Volume II: Strategies
* Christi Gibson's suggestions on how to tame the tusks of that recession elephant in the room
* A look at the latest incentive research—the unpleasant and the reassuring
* James Feldman's take on the "Nature versus Nurture" debate and what it means for incentives
* An interview with experts from Rideau Recognition Solutions and the Human Capital Institute on why money matters less than you think when it comes to boosting morale
*Chester Elton's look at how great leaders use recognition as a way to build confidence, focus employees on the right behaviors, and retain and engage their key people
* And much more
Volume III: Management, Sales and Marketing
* David Johnston offers five goals for creating a better and more successful sales compensation strategy—and positioning yourself for growth in 2010
* Jim Dittman has a different take on the effects of the recession, arguing that weeding out the incompetent helps the strong survive
* Author Arupa Tesolin on how the recession offers the chance to seed innovation that will allow your business to better position itself for when things turn around
* Paul Hebert discusses how recessions can challenge, but they are the ideal time to get a step or two ahead of the other guys
* Giving Back is the new face of incentives, according to Incentive's corporate social responsibility columnist, Geraldine Gatehouse
* And much more
Volume IV: Travel, Awards and Gift Cards
* How to make incentive travel work, from redefining the "open bar" to getting executives more involved in the trip
* Brian Martenis on travel's new challenges and timeless value as an award
* Gift cards prove to still be a top choice, as Incentive speaks with industry members
* Ley Borlo discusses how, in some ways, the philosophy of why and how to motivate performance has not changed much, but the technology has
* A look at the rise in short-term sales incentives, and how merchandise is helping companies achieve success in small steps
* And much more
The Complete Recession Survival Guide serves as a powerful reference for executives and planners seeking to survive and thrive during tough times, and position themselves for greater success for both the short and long term.
Visit the Incentive Digital Mall to learn more and purchase a copy of the complete guide.
Please send comments and questions to email@example.com.


text:
wikiHow to Treat Poison Ivy and Poison Oak
Three Methods:Taking Immediate Care of Your SkinTreating the Itch Caused by the PoisonPreventing Future ExposureCommunity Q&A
Poison ivy, oak, and sumac are a great way to ruin a day in the outdoors. Coming in contact with their toxic leaves, stems, and roots can give you an itchy rash that lasts for 1-3 weeks. Although the only way to completely remove the rash is time, there are several means of reducing the pain and itching involved with exposure to poison ivy.
Taking Immediate Care of Your Skin
1Remove and wash your clothes. Take off your clothes and place them in a plastic garbage bag, if possible. Wash your clothes separately from anything else as soon as possible.
2Apply rubbing alcohol. You can apply rubbing alcohol to your skin to dissolve the poison ivy or poison oak oils. Because the toxic oil from the plant seeps into your skin gradually, adding rubbing alcohol to the area will prevent the further spread. It won't provide immediate relief, but it will stem the spread. You can also use an over-the-counter cleanser like Tecnu or Zanfel.
3Rinse the area with cool water. Never use warm or hot water, as this will open your pores and allow more of the toxins to sink in. If you're able, keep the affected area under cold running water for 10-15 minutes. If you're outdoors in the woods when you're exposed to poison ivy or poison oak, then you can rinse your body off in a running stream.[1]
4Completely clean the area. Regardless of the location on your body, make sure that it was thoroughly rinsed with water. If you touched the area on your body at all or the poison affected your hands, scrub under your fingernails with a toothbrush in case any oil from the plants was deposited beneath them. Throw the toothbrush away after you're done.
- Use a dish soap that is used for oil removal to rinse the area of your rash. Because the toxins have been transferred to your skin in the form of an oil, using an oil-obliterating dish soap may help to reduce the spread of the rash.
- If you use a towel to dry yourself after washing the affected area, be sure to wash the towel with the rest of your exposed clothes immediately after use.
5Don't scratch the rash. Even though the rash is not contagious, you could break the skin and allow bacteria to enter the wound. Don't touch or pop any blisters that may form, even if they are weeping. If necessary, cut your nails short and cover the area to keep yourself from scratching it.
6Cool off the exposed area. Apply cold compresses or apply an icepack for 10 to 15 minutes. Make sure that you don't apply ice directly to your skin; always wrap your ice pack or compress in a towel before application. Also, allow the area to air dry instead of rubbing it with a towel if you get your rash wet.
Treating the Itch Caused by the Poison
1Apply topical creams or lotions. Calamine lotion, capsaicin cream or hydrocortisone cream can provide some relief from itching. Don't do this immediately after contact with the plant (as rubbing the lotion could spread the oils), but after a few hours or days when the itching feeling begins. Capsaicin cream, usually sold in drugstores labeled for arthritis pain relief, burns a bit at first but suppresses itching for hours.
2Take antihistamines. Antihistamines are medications that treat for allergies, and since poison oak and ivy cause allergic reactions on contact, taking these drugs may offer minor relief. Antihistamines generally offer only mild relief from the symptoms of poison ivy, but if you take oral medications before bedtime, their combination of anti-itch and drowsiness-inducing effects can help you get some rest. Only take these orally, and do not apply the creams to your poison ivy as this can worsen your rash.
3Take an oatmeal bath. Use an oatmeal bath product or an aluminum acetate soak. If you need a quick fix without running to the store, blend a cup of oatmeal in a food processor or blender and add it to your warm bathwater. Avoid using water that is very hot, especially right after being exposed to the poison as this will open your pores,[2]
4Try an acorn broth. Crack acorns and boil them in water. Strain out the nuts, cool the liquid and apply it to your rash with a cotton pad. Although this method hasn't been studied, it has shown to reduce the itchy feelings of poison ivy rash.
5Use baking soda. Make a paste consisting of 3 parts baking soda to 1 part water. Apply the paste to your rash to pull the fluid out of the blisters. Leave the baking soda paste to dry, and allow it to crack or flake off. Reapply this paste every few hours for the best results.
6Try using dairy. Use buttermilk or yogurt to apply to your skin, unless you have a dairy allergy. When you apply buttermilk or yogurt to your rash, the proteins will draw out fluid from your blisters.
7Treat your rash with tea.Fill a bathtub with water and add 12 tea bags; use chamomile tea for its anti-inflammatory properties. Soak in your tea bath for 20 minutes to help reduce the itchiness and uncomfortable feeling. You can also brew very strong tea and dab it onto your rash with a cotton ball every few hours.
8Use chilled fruit rinds. Press a cold watermelon rind or banana peel against your rash. The watermelon rind acts as a cold compress, and the juice helps to dry out blisters. On the other hand, using a banana peel helps to cool and soothe the area.
9Dab on cold coffee. If you have a bit of leftover dark-brewed coffee, use a cotton pad to dab it onto your rash. You can also brew a fresh cup, but allow the coffee to cool in the fridge before applying it. Coffee contains chlorogenic acid, which is a natural anti-inflammatory.
10Rinse with apple cider vinegar. Among the many medical treatments apple cider vinegar can be used for, expediting the healing process of poison ivy exposure is one of them. Use a cotton pad to gently apply the vinegar to the area, or rinse it with a mixture of equal parts vinegar and water.
11Apply aloe vera. Aloe vera is a cactus-like plant that excretes a cooling gel from its leaves. You can use a real aloe vera plant by snapping off leaves and applying the gel directly to your rash, or use a processed bottled form. If you buy a bottle from the store, make sure that it is at least 95% real aloe vera.[3]
Preventing Future Exposure
1Learn to identify poison plants. Avoid plants that have the following characteristics:
Poison ivy has 3 shiny green leaves and a red stem. It grows as a vine, typically along riverbanks or lake shores. It can also be found in woods or forests. As a common rule of thumb remember this simple rhyme: "Leaves of three, leave it be."
Poison oak grows as a shrub and has 3 leaves like poison ivy. Poison oak is typically found on the West Coast of the U.S.
Poison sumac is a woody shrub with 7 to 13 leaves arranged in pairs. It grows abundantly along the Mississippi River.
Poison ivy has 3 shiny green leaves and a red stem. It grows as a vine, typically along riverbanks or lake shores. It can also be found in woods or forests. As a common rule of thumb remember this simple rhyme: "Leaves of three, leave it be."
2Bathe your pets if they have been exposed to the plants. Pets aren't sensitive to poison ivy or poison oak, but if the oils are trapped on their fur, then they could cause an allergic reaction in anyone who pets them. Use pet shampoo and wear rubber gloves while you're giving them a bath.
3Bring preventative measures. If you are taking a hike or are camping in an area that grows poison ivy, bring extra bottles of cold water and rubbing alcohol. If you apply both of these immediately after coming in contact, you will greatly decrease the spread and pain associated with exposure.
4Dress appropriately if you're going into an area where you think you may find poison ivy or poison oak. Wear long sleeved-shirts, long pants and socks. Make sure that you wear closed-toe shoes, and always bring a spare change of clothes just in case of an accident.
Community Q&A
Does poison oak get hard before it heals?The inflammation from the rash can cause swelling, which can make the skin feel "hard". Also, scratching will cause the skin to thicken and feel "hard". This will resolve once the rash heals. The less you scratch, the faster your skin will heal.
How long does it take for the rash to show?On average it takes 2 to 4 days for the rash to appear, but it can be longer or shorter depending on your prior exposure.
How would I kill the plant?wikiHow ContributorRemove the plant using pruning shears. Be sure to wear gloves and long sleeves. Never burn the plant, as the smoke coming up from the plant can be fatal.
The area around my eye is very swollen-in addition to the poison ivy rash on my cheek -what can I do to soothe and reduce the swelling?wikiHow ContributorApple cider vinegar may help to heal the skin near the eye. Be careful not to get any in your eyes. If the whites of your eyes turn pink, then see a doctor for steroid eye drops.
Why do I get a rash when I don't even touch the plant?wikiHow ContributorYou might have touched something or someone that came in contact with the plant. Some people are not allergic to poison ivy, but they can still "spread" it.
Will taking a salt bath help me?wikiHow ContributorYou could try, but it would do nothing for the inflammation. It also won't be very soothing. Try a topical cream such as, Caladril or Aloe Vera gel.
What if I have poison ivy on my mouth?wikiHow ContributorDo not apply an anti-itch topical cream on your mouth. The best thing to do is visit your local doctor as soon as possible.
How long does it take for the rash to show up after being exposed?wikiHow ContributorOn average, the rash appears 2-4 days after coming in contact with the plant, but it could come sooner or later depending on your prior exposure.
Do poison oak rashes get hard before they heal?wikiHow ContributorThis can happen due to inflammation and swelling or if you are scratching the rash a lot. The less you scratch, the faster it will heal. If you're really worried, there's no harm in consulting your physician.
How can I stop poison oak from growing even though I cut it with shears in my backyard?wikiHow ContributorKeep regular mowing and trimming to prevent the growth.
- If a child gets into poison ivy, oak, or sumac, cut his or her fingernails very short to minimize skin damage from scratching.
- Don't skip the step of washing your clothes and tools or bathing your pet. Poison ivy and poison oak resins can stay on objects for up to 5 years, which could cause you to have another allergic reaction when your skin comes into contact with them.
- Put spray-on deodorant on your arms and legs before going outside. It stops up your pores and the oil of the poison ivy does not get in your skin.
- Poison ivy and oak are related to the mango tree. People who have a history of poison ivy or poison oak dermatitis will often develop the same rash on their hands, extremities or corners of their mouth if they are exposed to mango skin or sticky mango sap while picking fruit from a tree or eating it. If you have a history of poison ivy/oak rashes, let someone else pick the mangoes and prepare them so that you can enjoy the flavor without an itchy, weeping red rash.
- Eliminate poison ivy or poison oak in your yard by digging up small plants or cutting larger plants back to ground level. You can also spray them with herbicides containing glyphosate or triclopyr (not recommended due to dangers of herbicide vapors around pets and children). Make sure that you wear long-sleeved shirts and gloves when you work with poison plants.[4]
- You can get Oral Ivy at your local drugstore. You put it in water and drink it. It has no taste and works fast. If you use it before exposure it stops the rash. If you have the rash already, it stops the itch and speeds the healing.
- You can use Caladryl clear for poison ivy.
- If you are gardening, always remember to wear gardening gloves to prevent any contact with poison ivy, poison oak, and poison sumac.
- Do not soak in tub after exposure. The oils float on top of the H2O and spread rash.
- If you have a rash in your eyes, mouth, nose or genital area, or if the rash covers more than 1/4 of your body, then you should consult your doctor. Also, see your doctor if the rash doesn't improve in a few days, if it gets worse or if it keeps you awake at night. Your physician may prescribe corticosteroids to help relieve the itching.
- Call 9-1-1 if you are having difficulty breathing or severe swelling. If you have been exposed to smoke from burning poison plants, then you should seek emergency care.
- Never burn poison ivy, poison oak or poison sumac to get rid of it. The oil is vaporized and the resins can float downwind in the smoke and can cause severe allergic reactions for anyone who may inhale it. This can cause the rash on lung tissue resulting in respiratory failure in extreme cases. Either way, it's very dangerous.
- If you have a fever over 100 F (38 C), if you see yellow scabs or pus, or if you develop tenderness on the rash, then you should see your doctor immediately about the possibility that you may have an infection.[5]
Sources and Citations
- ↑ http://www.webmd.com/allergies/guide/poison-ivy-oak-sumac?page=3
- ↑ http://www.nlm.nih.gov/medlineplus/ency/article/000027.htm
- ↑ http://health.howstuffworks.com/wellness/natural-medicine/home-remedies/home-remedies-for-poison-ivy2.htm
- ↑ http://www.clemson.edu/extension/hgic/pests/weeds/hgic2307.html
- ↑ http://www.fda.gov/forconsumers/consumerupdates/ucm049342.htm
Article Info
Categories: Skin Inflammation and Rashes
In other languages:
Español: tratar una hiedra venenosa y un roble venenoso, Italiano: Curare l'Esposizione a Edera Velenosa o Quercia Velenosa, Português: Tratar Alergias a Heras Venenosas e Carvalhos Venenosos, Deutsch: Ausschlag von Giftefeu oder Gifteiche behandeln, Français: traiter un contact avec le sumac grimpant ou le sumac de l'Ouest, 中文: 治疗毒漆藤皮疹, Čeština: Jak vyléčit vyrážku od břečťanu, العربية: معالجة اللبلاب والبلوط السام, Nederlands: Gifsumak en poison oak behandelen, Tiếng Việt: Chữa trị Nhiễm độc từ cây Sồi và Thường xuân, 한국어: 옻이 올랐을 때 치료법
Thanks to all authors for creating a page that has been read 3,351,518 times.


text:
It's been a while since we've heard from Jason Molina. After releasing the hauntingly great 2009 album, Molina and Johnson, with Centro-matic's Will Johnson, Molina cancelled the tour that was supposed to follow, and since then there hasn't been much news from him.
Well, it turns out he needs our help. According to the Secretly Canadian website, Molina has spent the past two years in and out of hospitals and rehab centers dealing with some serious health concerns. And while Molina and those around him seem hopeful that he can fully recover and return to music soon, like so many of us Jason Molina has no health insurance. So, as if being very sick weren't bad enough, he has accrued some substantial medical bills and is reaching out for help.
A page has been set up for people to make donations to help Molina out, and if you do you'll be rewarded with a full Magnolia Electric Co. album, recorded at Cat's Cradle in Carrboro, North Carolina in 2007. So in care you weren't just into helping a guy in need, now you've got some seriously excellent live music as incentive to donate.
Head over to Bandcamp now to sample the live album, or just go right to the donation site. There you can read the full statement from Molina's family and, hopefully, send a few extra bucks his way if you've got them to spare.
And, in case you need reminding of how good those guys are live:
Ponytail - Ponytail Announces Split | Guided By Voices Original Lineup Of Guided By Voices Announce New Album |


text:
Streaming Audio
Listen online to a full-length recording of this work.
performed by Sydney Symphony, Nathan Waks (cello), Richard Gill (conductor)
Access to this recording is courtesy of the ABC's classic amp website.
Selected products featuring this work — Display all products (2 more)
In memoriam : concerto for amplified cello and orchestra / by Matthew Hindson
Library shelf no. Q 784.274186/HIN 1 [Available for loan]
Display all products featuring this work (2 more)
Work Details
Year: 2000
Instrumentation: Piccolo, flute, 2 oboes (2nd doubling cor anglais), clarinet in B flat, bass clarinet, bassoon, contra-bassoon, 4 horns in F, 2 trumpets in C, 2 trombones, bass trombone, tuba, timpani, percussion (5 players), bass drum, harp, piano/celeste, solo amplified cello, strings.
Duration: 30 min.
Difficulty: Medium — Professional
Contents note: I. Lament (i. Introduction ; ii. Cadenza ; iii. Cor anglais solo ; iv. Lament) -- II. Celebration.
Dedication note: Dedicated to my cousins, Robert Hopkins and Hargret Davis.
Commission note: Commissioned by Sydney Symphony.. Commissioned for 2001 Sydney Symphony Meet the Music series.
First performance: by Nathan Waks, Sydney Symphony, Richard Gill — 4 Apr 01. Sydney Opera House Concert Hall, Australia.
Program note: Matthew Hindso's "In Memoriam"
by Symphony Services
Book: 2001 Philips Meet the Music Australian composition resource kit / Sydney Symphony.
Book: Compositions by Matthew Hindson : volume I, introductory essay / Matthew Hindson.
- In the form/style of: Concertos
Performances of this work
27 Mar 2016: at Four Winds: Sound Shell Sunday (Four Winds Sound Shell). Featuring Liwei Qin.
6 Apr 01: featuring Richard Gill, Nathan Waks, Sydney Symphony.
5 Apr 01: Sydney Opera House, Concert Hall. Featuring Richard Gill, Sydney Symphony, Nathan Waks.
4 Apr 01: Sydney Opera House Concert Hall, Australia.. Featuring Nathan Waks, Richard Gill, Sydney Symphony.
User reviews
Be the first to share your thoughts, opinions and insights about this work.
To post a comment please login.


text:
Kingdom | Phylum | Class | Order | Family |
Animalia | Chordata | Amphibia | Anura | Alytidae |
Scientific Name: | Discoglossus jeanneae | ||||||
Species Authority: | Busack, 1986 | ||||||
Common Name(s):
Taxonomic Notes: | This taxon is closely related to D. galganoi, and some authors consider them to be conspecific. |
Red List Category & Criteria: | Near Threatened ver 3.1 |
Year Published: | 2009 |
Date Assessed: | 2008-12-14 |
Assessor(s): | Jaime Bosch, Miguel Tejedo, Miguel Lizana, Iñigo Martínez-Solano, Alfredo Salvador, Mario García-París, Ernesto Recuero Gil, Carmen Diaz Paniagua, Valentin Pérez-Mellado, Rafael Marquez |
Reviewer(s): | Cox, N. and Temple, H.J. (Global Amphibian Assessment) |
Justification: Listed as Near Threatened because this species is probably in significant decline (but probably at a rate of less than 30% over ten years) because its habitat is being degraded due to drought through most of its range, thus making the species close to qualifying for Vulnerable. |
Previously published Red List assessments: |
Range Description: | This species is endemic to isolated areas in southern, eastern and north-eastern Spain, from sea level to around 2,050m asl (in Granada). | ||
Countries occurrence: | Native: Spain | ||
Additional data: |
| ||
Range Map: | Click here to open the map viewer and explore range. |
Population: | It is generally more abundant in the south of its range, and is considered to be scarce in the north, although further surveys are required. Its occurrence is very patchy within its overall range, and it is believed to be in decline, principally due to increased aridity within its range. It is likely that isolated populations have recently become extinct along the Mediterranean coast. | ||
Current Population Trend: | Decreasing | ||
Additional data: |
Habitat and Ecology: | An inhabitant of open areas, pine groves and shrubland associated with limestone or gypsum soils. This is a very aquatic species found in shallow pools, streams, springs, ponds and artificial water sources, such as drinking troughs and drainage channels. Breeding and larval development takes place within the aquatic habitats. It can be present in traditionally farmed areas. |
Systems: | Terrestrial; Freshwater |
Major Threat(s): | The major threat to this species is continued loss of habitat as a result of increased aridity throughout its range. It is also threatened by loss of suitable habitat (including fragmentation) to agricultural and infrastructure development. The species is particularly impacted by the loss, or contamination, of aquatic habitats (such as drinking troughs), and introductions of predatory fish and crustaceans, in particular the Louisiana Crayfish (Procambarus clarkii). Its populations are now fragmented in many parts of its range. |
Conservation Actions: | The species has been recorded from Parque Nacional de Sierra Nevada. It is listed on Appendix II of the Bern Convention and on Annexes II and IV of the EU Habitats Directive. It is recorded in the national Red Data Book of Spain and is protected by national legislation. There is a need to further clarify the distribution of this species. |
Citation: | Jaime Bosch, Miguel Tejedo, Miguel Lizana, Iñigo Martínez-Solano, Alfredo Salvador, Mario García-París, Ernesto Recuero Gil, Carmen Diaz Paniagua, Valentin Pérez-Mellado, Rafael Marquez. 2009. Discoglossus jeanneae. The IUCN Red List of Threatened Species 2009: e.T6713A12798514. . Downloaded on 28 March 2017. |
Disclaimer: | To make use of this information, please check the <Terms of Use>. |
Feedback: | If you see any errors or have any questions or suggestions on what is shown on this page, please provide us with feedback so that we can correct or extend the information provided |


text:
Evoke D4 Mio with Bluetooth is a portable DAB digital and FM radio, featuring leather effect casing. The included remote control makes it easy to select radio stations and adjust the volume, while built-in Bluetooth turns your radio into a great wireless speaker . The Evoke D4 Mio is perfect for anywhere in your home, including the bedroom with its two quick access alarm buttons and SnoozeHandle for effortless snoozing. Other features include a remote control, 30 presets (with four quick access buttons) and a kitchen timer. Theres also a stereo headphone socket and aux-in for your iPod or MP3 player. Evoke D4 Mio also takes a Pure ChargePAK F1 rechargeable battery pack (Sold separately) for portable listening.
Check stock and price


text:
Publication number | US7073170 B2 |
Publication type | Grant |
Application number | US 11/085,673 |
Publication date | Jul 4, 2006 |
Filing date | Mar 21, 2005 |
Priority date | Apr 24, 2000 |
Fee status | Paid |
Also published as | US6871344, US20020100017, US20050166196 |
Publication number | 085673, 11085673, US 7073170 B2, US 7073170B2, US-B2-7073170, US7073170 B2, US7073170B2 |
Inventors | Michael J. Grier, Sanjay G. Shenoy, RoseMarie FitzSimons, David D'Souza, Srivatsan Parthasarathy, Michael Dunn, Alan Shi |
Original Assignee | Microsoft Corporation |
Export Citation | BiBTeX, EndNote, RefMan |
Patent Citations (3), Referenced by (35), Classifications (9), Legal Events (4) | |
External Links: USPTO, USPTO Assignment, Espacenet | |
This is a continuation of U.S. patent application Ser. No. 09/842,278 filed Apr. 24, 2001 now U.S. Pat. No. 6,871,344, which claims priority to United States Provisional Patent Application Ser. No. 60/199,227, filed Apr. 24, 2000.
The present invention is generally directed to computer systems, and more particularly to executable computer code such as application programs that utilize shared assemblies.
At one time, computer applications were monolithic blocks of executable code and data, although some of their data such as variable settings could be maintained in separate files. This made tasks like moving or replacing the application simple. In contrast, contemporary computer applications and other executable code (such as an operating system component) bind to and make use of shared components, wherein in general a component is a self-contained software entity, offering a set of functions that can be used by a variety of applications. Such components include dynamic link libraries (DLLs) and objects such as OLE (Object Linking and Embedding) components and COM (Component Object Model) components, including ActiveX� controls. In turn, some of these shared components depend on other shared components.
On any given machine, at present there is one version of each of these components shared by applications, such as the most-recently installed version, although some mechanisms are known that replace an installed component only when an available replacement component has a higher version number. The metadata maintained for using these components is generally maintained in the system registry, and the application has the names of the needed components compiled into its binary code. Because in general the application does not change as components change, to function properly, global component sharing requires that any shared component function exactly like previous other versions of that component with respect to what an application expects. In practice, however, perfect backwards compatibility is difficult if not impossible to achieve, among other reasons because it is impractical to test the many configurations in which the shared component may be used. For example, both newer and older applications end up sharing the same component, whereby over time, fixing and improving the component becomes increasingly difficult. Moreover, the practical functionality of a component is not easily defined. For example, some applications may utilize unintended side effects in a component that are not considered part of the core function of the component, e.g., an application may become dependent on a bug in a component, and when the component publisher chooses to fix that bug, the application fails. Of course, on the other side, application writers cannot test future versions of components.
As a result, problems occur when a component is updated to its newer version, such as when a new application or operating system service pack is installed with updated copies of components, as the newly installed component versions become the ones used by other applications and components on the system. The sheer volume of applications and components that rely on other components magnifies this problem, which is sometimes referred to as "DLL Hell."
One mechanism that provided sharing for some applications while enhancing the stability of other applications was provided in Microsoft Corporation's Windows� 2000 and Windows� 98, Second Edition, operating systems. In general, this mechanism provided a way for an application to be bound to a local copy of a component instead of a shared copy. However, with this solution, a component needed to be isolated per application, which resulted in multiple copies of the same component version having to be maintained on the system. Additionally COM data was not isolated, limiting this mechanism's usefulness with COM objects.
At the same time, even if it was possible to permanently bind an application to one version of a shared component, it is not always desirable to do so. For example, a critical security fix may be made to a component, but if an existing application were permanently bound to an earlier version of that component, the application would not be protected by the security fix. In sum, the existing models for sharing components have many problems and shortcomings.
Briefly, the present invention provides a method, system and infrastructure that allow an application to run with specified versions of components bound thereto, while allowing the application author and/or component publisher to change the version as desired. In an alternative mode, an administrator may also have input (e.g., the final decision) as to specifying the version to be used. A component is often packaged with other components as an assembly, wherein an assembly is set of one or more component files that are versioned and ship as a unit, and thus as used herein a set of one or more components are also referred to as an assembly, and a component publisher an assembly publisher.
Each assembly may exist and run side-by-side on the system with other versions of the same assembly being used by other applications. To this end, the application provides an application manifest to specify any desired assembly versions. The application author may also provide (e.g., at a later time) an application configuration that overrides the binding information in the application manifest. The present invention also allows an assembly publisher to provide a publisher configuration that may similarly control which assembly version will be used. In a first alternative mode, the application configuration (when present) is applied after any publisher configuration is applied and thus overrides the publisher configuration's binding information. In a second alternative mode, the order of applying the configurations is reversed, whereby the publisher configuration may change the application configuration's binding override information. In this second alternative mode, the application configuration may have a setting therein that bypasses the publisher configuration, in a "safe" mode of operation. Lastly, (preferably also in this second alternative mode), an administrator configuration may be present that is capable of overriding the other configuration version binding information. Some or all of the various configuration data structures (e.g., the publisher configurations) themselves may wrapped as assemblies, thereby benefiting from the characteristics of assemblies, including versioning of configurations, strong naming of configurations, and so on.
In this manner, the present invention enables applications to explicitly use different versions of assemblies from what the application as originally shipped had specified. This allows for exact management and control of assemblies during the lifecycle of the application. To determine the correct version, at runtime, in the first mode, the present invention first interprets the application manifest (e.g., released with the application), followed by a publisher configuration, if present, that may redirect (re-map) any assembly versions specified in the application manifest to other assembly versions. Then, if an application configuration is present, the application configuration is interpreted to redirect some or all of the current binding information, e.g., for the current assembly version to another assembly version, as specified therein.
In the second alternative mode, the present invention first interprets the application manifest (e.g., released with the application), followed by the application configuration, if present, that may redirect (re-map) any versions specified in the application manifest to other versions. Then, if a publisher configuration is present, and the application configuration does not bypass the publisher configuration via a special safe mode, the publisher configuration is interpreted to (possibly) redirect the current binding information, e.g., for that assembly version to another assembly version, as specified therein. Lastly, any administrator configuration is interpreted to (possibly again) change the bindings to assembly versions.
For efficiency, the present invention may build tables in an activation context in a pre-execution initialization phase to maintain the version mapping information, rather than interpreting the manifest and any configurations each time an assembly is needed, (i.e., per-request file mapping including adjusting for configurations is straightforward to implement, but less efficient). The activation context tables provide fast mapping from assembly names provided by the application, including version-independent names, to the correct versions as specified in the manifest (normally fully-named assemblies) and altered by any configurations. Once built, the tables may be cached, e.g., such as in the first alternative mode for the time that the application instance runs (lifetime of the process), whereby the information therein is available as needed. In an alternative mode such as the second alternative mode, the tables or other binding data may be dynamically recalculated.
To use the tables, in the pre-application execution phase when creating a new process, the operating system checks for an application manifest in same file system directory as the calling executable. In the first alternative mode, when an application manifest exists, the operating system checks for an activation context for the application that was built from the manifest and configurations. If the activation context does not exist (for example this is the first time application has been executed), or it exists but is not coherent with current configuration, a new activation context is created via the application manifest and configurations.
At runtime, when a program requests creation of a global object, the operating system automatically consults the activation context built from the application and configurations to locate and load the appropriate assembly version. The operating system also maps any uses of this named object to the appropriate version to allow for multiple versions of the code module to run simultaneously without interfering with each other. By the activation context built from the application manifest and the configurations, an application may be efficiently bound to specific assembly versions and thereby be isolated from assembly version changes. At the same time, changes to the bindings are enabled via the configurations.
Other objects and advantages will become apparent from the following detailed description when taken in conjunction with the drawings, in which:
The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and so forth, that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
With reference to
The computer 110 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer 110 and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by the computer 110. Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media, discussed above and illustrated in
The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in
Isolating and Binding Assembly Versions
The present invention is generally directed to binding application programs to configuration (also referred to as policy) determined, isolated versions of components, (including code and/or data), per-application program or the like, in a manner that allows multiple versions of the same component to exist and operate side-by-side on a system. For practical purposes, components are often collected into an assembly, which, when referring to items such as a component, is the lowest unit of storage packaged for activation, distribution and versioning. Rather than deal with individual components, of which there may be a relatively large number, many of the actions regarding components that are grouped together can be handled by referring to their assembly. For example, rather than list in the manifest 204 the dependencies on a large number of individual components that are packaged together in a component assembly, the manifest may simply list a dependency on the assembly. As used herein, the term "assembly" will refer to one or more components, whether referring to a single component (e.g., one contiguous DLL) or to a plurality of components grouped together.
Assemblies can be shared, such as when more than one application or the like needs an instance of the assembly's code. To provide significant flexibility while being transparent to existing and newly-developed applications, the present invention has been implemented in an operating system, with applications being run via the operating system. As will be understood, however, the present invention is not limited to applications and/or an operating system implementation, but rather is capable of being implemented by virtually any mechanism internal or external to executable code (e.g., an application) that needs or wants to use a specific version of an assembly. Note that as used herein, an application program is not limited to any particular type of software product, but includes any executable code such as operating system components, drivers and so on that in turn use other assemblies. Notwithstanding, the present invention will be primarily described with an application that uses assemblies such as DLLs and objects.
In general, an application manifest is an XML (extensible Markup Language) formatted file or other suitable file that comprises metadata (e.g., 206) describing an application's dependencies on shareable assembly versions, (sometimes referred to as side-by-side assemblies), and also includes metadata to describe any privatized assemblies (described below). For example, the application manifest 204 specifies in its dependency data 206 a dependency on a particular version (e.g., v188.8.131.52) of a shared assembly, assemblyx 208 1, as represented in
Two types of assemblies are possible, those having strong names, e.g., including a public key signature or the like such that any two different assemblies can be unambiguously identified, and those having a simple name, which may be ambiguous in the system, and, for example, do not contain a public key. To provide isolation, any simply-named assemblies on which an application manifest specifies a dependency are treated as privatized assemblies 210 of
The application, manifest and assemblies, both privatized and global, are installed to their appropriate file system locations at the time the application or assembly is installed. In general, the application, application manifest and privatized assemblies (those not strongly named) are copied to the application folder, while strongly named assemblies may be copied to the global assembly cache 212 (e.g., one or more folders). Note that to provide side-by-side existence of assembly versions, any existing assembly versions are not overwritten in the assembly cache 212 when another version is installed, (although a version can be removed by other means, at the risk of breaking an application that depends on that version). The assembly cache can be hidden and/or access controlled to prevent assemblies from being easily removed. The installation and general usage of manifests and assemblies are further described in the aforementioned United States Patent Application entitled "Isolating Assembly Versions for Binding to Application Programs."
Example manifests in XML format are set forth in the tables below, wherein TABLE1 is an example of a simple application manifest where the application depends on a side-by-side version of COMCTL32:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
<description>Your app description here</description>
TABLE2 is an example of an application manifest where the application depends on a side-by-side version of COMCTL32 and an assembly is privatized to the application:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
<description>Your app description here</description>
<!-- Privatized assembly -->
<file name="mypaint.dll">
<comClass description="Font Property Page"
<comClass description="Color Property Page"
<comClass description="Picture Property Page"
<file name="mydraw.dll"/>
<file name="testctl32.dll">
description="SxSTestObject Class"
description="SxS_COM 1.0 Type Library"
Assemblies may be dependent on other assemblies, which in turn are dependent on other assemblies, and so on. To ensure the proper versions of dependent assemblies, one or more of the assemblies (e.g., assembly 208 1) each have an assembly manifest (e.g., 214 1) associated therewith that specifies its corresponding assembly's dependencies. To this end, assembly authors that create a side-by-side assembly may also author an assembly manifest, which is copied to the assembly cache 212 with the corresponding assembly at the time of installation, whereby that assembly manifest will be interpreted for proper version dependencies. Note that although not directly identified in
Each assembly manifest describes the assembly and includes information about its individual assemblies, including, for example, the name and version of the assembly, the items (program files, resources) that make up the assembly, and the binding path to items within the assembly (e.g., for Win32 DLLs this is the location of the DLL relative to the root of the assembly, whereas for COM Servers this is the CLSID (class identifier), ProgID (programmatic identifier) and other COM metadata). The assembly manifest may also include any dependencies on other assemblies, object classes and global names.
A sample assembly manifest is set forth in TABLE3 below:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
<assemblyIdentity type="win32"
version="188.8.131.52" processorArchitecture="x86"
<file name="mfc42u.dll"
<comClass description="Font Property Page"
<comClass description="Color Property Page"
<comClass description="Picture Property Page"
<file name="mfc42.dll"
<file name="atl.dll"
<comClass description="Registrar Class"
<interface iid="{B6EA2051-048A-11D1-82B9-
00C04FB9942E}" name="IAxWinAmbientDispatch"
<typelib tlbid="{44EC0535-400F-11D0-9DCD-
00A0C90391D3}" version="1.0" helpdir=""/>
<file name="msvcrt.dll"
<file name="msvcirt.dll"
<file name="msvcp60.dll"
Although the application manifest 204 lists its dependencies on assembly versions, it should be noted that technically, the application 200 is only dependent on the manifest-specified assemblies themselves, not necessarily the exact versions that are specified. Instead, the specified versions are only those tested with the application and known to work.
In accordance with one aspect of the present invention, the operating system (e.g., including an assembly loading mechanism) can bind the application to another version of a needed assembly in place of one specified in the application manifest 204. To this end, configuration information that is separate from the shared assembly may be interpreted to determine which version to bind. Note that a configuration is separate from the shared assembly or assemblies to which it refers, for example, in that it is a separable entity therefrom, normally contained as a file, that can be added to or removed from a system at a later time, and so on.
In a first alternative mode, as shown in
The publisher configuration enables an assembly publisher to effectively replace one assembly version with another version, such as when a service pack is installed. As described herein, in a first alternative mode, the assembly publisher configuration is interpreted after the manifest is interpreted, and thus can change an assembly initially specified by the application author. For example, in
As also represented in
In a second alternative mode, the order of applying configurations is modified, and also at least one other configuration may be applied. More particularly, as shown in
As also represented in
Lastly, in this second mode, an administrator configuration 224 and its version data 226 may have the final decision as to which version of an assembly an application (any application on the machine) will be bound. For example, in
Although complete compatibility of a shared assembly should be thoroughly tested, even the smallest change to a shared assembly's code may cause an incompatibility with some applications that consume them. In such an event, in the second alternative mode wherein the publisher configuration data can override the application configuration data, the application configuration file may specify that "safe mode" binding should be applied to the specified assembly. In the safe mode, the publisher configuration resolution stage is avoided, whereby the application operates with no publisher configuration overrides. To use the safe mode, the application configuration 218 (or other system setting, e.g., set by an administrator) can explicitly instruct the operating system to bypass the interpretation of the publisher configuration 220, whereby the application author (or an administrator) controls the version that is bound to the application. In
It should be noted that the safe mode bypasses publisher configuration in the second alternative mode, which may affect the version that is used even when the administrator configuration includes an instruction related to a version of that assembly. By way of an example, as shown in
Note that while two alternative modes are primarily described herein, it can be readily appreciated that other such modes are feasible. For example, it is feasible to have a third alternative mode similar to the first alternative mode described above wherein a publisher configuration is interpreted before an application configuration, but the further including an administrator configuration as in the second alternative mode. Indeed, the present invention is not limited to any particular ordering, number and types of configurations, and so on, but rather contemplates any such combinations and permutations.
As described above, binding starts with a reference, for example, that at least contains the name or other identifier of the assembly. A fully-specified assembly reference (e.g., in the manifest and/or configurations) contains the information necessary to disambiguate one assembly from another. Dependent assembly references, which are constructed at link time, are fully-specified assembly references. However, under some circumstances, it may be desirable to provide only a subset of the assembly identity information, yet still issue a bind. For example, a partially-specified assembly reference may be missing public key, and/or version fields.
Because partially-specified references are ambiguous, the binding process can employ special logic to locate and bind to these assemblies. More particularly, a first step to resolving a partial-specified assembly bind is to search for an assembly in the application directory that satisfies the specified fields in the assembly reference. The application directory is probed first, (as opposed to immediately searching for a matching assembly in the global assembly cache 212), to provide an application author/deployer with some control over the assembly that is finally retrieved through a partially specified bind request. In other words, because the global assembly cache 212 is a global install location, which can be used by all applications, searching the global assembly cache 212 first may result in an assembly being returned that was not intended by the original author/deployer.
Should the binding process be unable to locate a matching assembly in the application directory, a lookup in the global assembly cache 212 may be performed to attempt to find a matching assembly, (e.g. for strongly-named files in the first alternative mode). If a match is not found in the global assembly cache 212, the assembly bind may be failed (e.g., in the first alternative mode), or a download can be attempted (e.g., in the second alternative mode). If a matching assembly has been located, the binding process (e.g., the binding/initialization mechanism) reads the manifest data for the assembly and constructs a new, fully-specified assembly reference from this data. Because the assembly reference is now fully-specified, binding configuration can be applied on this reference, as described above, that is, the bind proceeds as if the original assembly reference was fully-specified, with the above-described logic used to specify one assembly file that, if located, satisfies the bind request.
Although it is possible to dynamically interpret the manifest and/or configurations to locate the appropriate version of an assembly each time an assembly is requested, assemblies are requested frequently, and thus it is more efficient to cache the information once. To this end, the activation APIs 300 cause an activation context 302 for that program 200 to be constructed if a valid one does not already exist for the application 300, (for example, when the application is being run for the first time or the activation context 302 exists but its information is invalid). Once created, the activation context 302 is maintained in a persistable binary form for caching. In general, there is an activation context for each application that has an expressed assembly dependency, and each activation context includes one or more mapping tables preferably hashed for quick lookup. As described below, the operating system (a runtime version matching mechanism therein) uses the activation context 302 to determine where to retrieve the version.
To construct the activation context 302, the activation APIs call (or otherwise include) a binding/initialization mechanism 304, wherein the call is generally represented in
As represented in
In one implementation, a publisher configuration assembly has the same name as the assembly it affects, but with a further extension appended to the name, (e.g., ".config"). This publisher configuration assembly has a module reference to an XML configuration file that stores the actual binding redirect information. Moreover, because assembly metadata contains a hash for the XML configuration file, it is possible to validate the integrity of the configuration file.
A publisher configuration assembly is created by authoring an XML configuration file (which may have any name), and using an assembly linker tool or the like to create the assembly. For example, as set forth below, a publisher configuration file, version 220.127.116.11, for an assembly named "test" is created, e.g., having an XML configuration file named
where major and minor vary with the version.
Publisher configuration assemblies normally will be obtained directly from the publisher as part of a service-pack style update, intended to affect all applications on the system. Because there is no direct link between the publisher configuration and the applications it affects, version redirects specified by the publisher configuration file may contain a codebase to the targeted version in the configuration file, otherwise the operating system will not necessarily be able to locate the intended files. Another option is to install the redirected version of the assembly on the machine. Similarly, assemblies targeted by administrator configuration can either be installed into the global assembly cache 212, advertised to the user, or located through a codebase provided in the administrator configuration file.
In this first mode, the second stage of configuration resolution, after any publisher configuration is applied, comprises resolving any application configuration. As represented in
For example, in an ".exe" runtime scenario, the file is named with the same name as the executable, but with a ".config" extension appended thereto, (e.g., "appname.exe.config"). An application author and/or deployer may choose to provide such a configuration file, thereby specifying version redirects for particular assemblies. For example, a configuration file may be written by an application author to specify that references to a common shared-assembly, whether directly provided by the application, or indirectly from a dependent assembly's dependency, should use a particular version. As another example, once an application deployer is confident that the application works with a newer version of a shared assembly, the deployer can choose to change the application configuration file to automatically use the new version instead of the version set forth in the application manifest. When interpreting the configuration, if a relevant binding redirect statement is found in the application configuration file, the version of the assembly from the original reference is modified accordingly.
Whenever a binding configuration statement is made in a configuration file, it is the responsibility of the author of the configuration file to ensure that the assembly targeted by the redirect can be found. In the case of the application configuration file, the application author/deployer may choose to package the files (e.g., binaries) for the target assembly with the application, or alternatively provide information (sometimes referred to as a "codebase") in the configuration file to tell the operating system where the files can be found. Another option is to install the redirected version of the assembly on the machine. Note that for privatized assemblies, e.g., in the second alternative mode, by attempting to locate the referenced assembly by consistently looking in the application directory, an application author may simply copy newer privatized assemblies into the application directory, and know that the newer assemblies will be automatically used by the application.
As generally described above, a second alternative mode is provided, in which the order of applying configurations is different, a safe mode is available for bypassing publisher configuration, and an administrator configuration may be present and if so is interpreted to override other configuration binding data. More particularly, in this second mode, the first stage of policy resolution comprises resolving any application policy. As represented in
In this second mode, a third stage in the bind configuration resolution process is administrator configuration, represented in
Once the configurations have been handled for a given assembly to which an application wants to bind, only one version of that assembly remains. This information may be cached in the activation context 302 (the arrow labeled eight (8) in
By way of example,
For persisted activation contexts, because the configurations that may change the dependency information may change over time, (e.g., publisher configurations may be wrapped as assemblies which can be versioned, new application configurations may be downloaded and so on), in the first alternative mode the activation context 302 includes a cache coherency section 402. The cache coherency section is used to detect whether a saved activation context 302 is valid, wherein when the activation context 302 is not coherent with current configuration, it is recomputed. A section per API that implements version-specific binding is maintained.
To map the application's requests to the proper assembly versions, the activation context 302 includes a DLL redirector section 404 and an object class redirector section 406. The DLL redirector section 404 includes a record or the like for each DLL dependency that includes fields (e.g., 408 1 and 409 1) that relate the DLL name used by an application to the exact pathname of the version determined following the above-described configuration-resolution process. The object class redirector section 406 includes a record or the like for each object class (e.g., Windows� object class) on which an application depends, wherein each record includes fields (e.g., 412 1, 413 1 and 414 1) that relate the object class name used by an application to the DLL file it is in and a version specific name. Note that the fields are arranged in a manner that optimizes lookup, e.g., the application-provided request data corresponds to the search key, and the records may be arranged in any way (e.g., alphabetically, by frequency, linearly, binary or so on) to speed searches.
Via the activation context, during runtime as described below, an application's requests for assemblies can be efficiently satisfied with the correct version of that assembly. If a given assembly is not found in the activation context data, the default assembly is used. To summarize, when an application first runs, the activation context built from the manifest data is cached, whereby the global, version-independent named objects requested by an application are mapped to version-dependent named objects as specified in the manifest and redirected by any configurations. As the application executes and requests a named object via one of the activation APIs, the version-independent named objects are applied in a version-specific fashion by accessing the application context, whereby the application gets the correct version.
When the application API 300 1 receive the request, the request data (e.g., the application provided name) is passed to a runtime version-matching mechanism 500 (the arrow labeled two (2)). The runtime version-matching mechanism 500 locates the correct activation context 302 (from among a store 502 or the like of those maintained) for the calling application 200, and accesses the records therein to determine the correct version of the requested assembly (the arrows labeled three (3) and four (4)). Via the tables in the activation context 302, the runtime version-matching mechanism 500 will either return (e.g., as a return parameter, with the arrow labeled five (5)) the path and filename of the version-specific assembly, or a not-found status or the like (and/or the path and filename of the default file) to the activation API that called it, in which case the activation API will load the default assembly. As represented in
Turning to an explanation of the operation of the present invention with particular reference to the flow diagrams of
When step 600 determines that an application manifest exists, the binding/initialization mechanism 304 (
In the event that the initialization process continues to step 610 to create the activation context, step 610 represents obtaining the binding information from the application manifest. Steps 610, 612, 614 and 616 of
By way of example,
At step 700, a test is performed to determine whether the assembly has a publisher configuration associated therewith, e.g., in the global assembly cache. If not, step 700 branches ahead to test for an application configuration at step 706, described below. If a publisher configuration is found at step 700, step 700 branches to step 702 wherein the publisher configuration is interpreted to determine whether there is an instruction therein for replacing the assembly version that is currently under evaluation, i.e., the one currently selected in the dependency graph either as originally specified in the manifest. If a replacement instruction is found, step 702 branches to step 704 wherein a dependency graph is altered to reflect the replacement, otherwise step 702 effectively bypasses step 704. By way of example,
At step 706, a test is performed to determine whether the application has an application configuration associated therewith, e.g., in the application directory. If an application configuration is found at step 706, step 706 branches to step 708 wherein the application configuration is interpreted to determine whether there is an instruction therein for replacing the assembly version that is currently under evaluation, i.e., currently selected in the dependency graph by identification in the manifest or as overridden by the publisher policy. If such a relevant replacement instruction is found, step 708 branches to step 710 wherein the dependency graph is altered to reflect the replacement.
At this time, the appropriate assembly version is known, as specified in the manifest and as altered via any configuration instructions, as described above. Step 712 enumerates any dependencies in the assembly manifest that corresponds to this appropriate assembly, e.g., to add dependent nodes to the dependency graph. Note that if an assembly representation (node) is already in the graph for a given assembly, a pointer from the node may be added to show the dependency rather than place a new node in the dependency graph. Step 714 marks the current node representing the assembly as having been handled, and the process returns to step 614 of
Note that to avoid problems, each configuration resolution stage is only evaluated once. For example, if a subsequent version redirect occurs as a result of any later configuration resolutions, the previous stages are not re-consulted to re-apply configuration. Re-applying configuration after other forms of configuration are applied may result in circular/infinite configuration redirects, and add unnecessary complexity to the binding process. Notwithstanding, in an alternative implementation, the process may, for example, loop back to handle a situation in which a replacement assembly may have another configuration associated therewith that can cause replacement of the currently selected assembly, and so on. Note that other safeguards against an infinite loop may be implemented to prevent a situation wherein versions have circular dependencies.
Beginning at step 900 the activation API receives the application request including the version-independent assembly name, not the version specific name, and passes it as a parameter or the like to the runtime version matching mechanism, where it is received at step 902. If an entry for the name is in the activation context at step 904, the runtime version matching mechanism returns the version specific information (e.g., including the path and filename of the correct version) based on the manifest at step 906. If an entry for the name is not found in the activation context at step 904, at step 908 the runtime version matching mechanism returns a not found status, (or alternatively can determine and return the path and filename of the default version). At step 910, the activation API loads the appropriate version, and returns a loading status or the like. The operating system also maps any uses of this named object to the appropriate version to allow for multiple versions of the code module to run simultaneously without interfering with each other, whereby, for example COM object data is isolated per object. At this time, the correct version as specified in the manifests is loaded, even though the application's executable code did not specify any version. Indeed, by providing an associated manifest that can be stored into the application's directory, an already existing application (e.g., written and installed before the present invention) can benefit from the present invention. In this manner, the application runs with a controlled set of assemblies bound thereto.
Turning to the second alternative mode,
When step 1000 determines that an application manifest exists, it is interpreted as represented by step 1004. Then, in this second mode, step 1006 tests whether an application configuration exists for this application, e.g., in the application directory. If not, step 1006 branches ahead to
If the safe mode is not specified at step 1100, step 1100 branches to step 1102 to test for a publisher configuration. If a publisher configuration is found at step 1102, step 1102 branches to step 1104 wherein the publisher configuration is interpreted to determine whether there is an instruction therein for replacing the assembly version that is currently under evaluation, either as originally specified in the manifest or as replaced by application configuration (as described above with respect to step 1010). If a replacement instruction is found at step 1104, step 1104 branches to step 1106 wherein the replacement is made, otherwise step 1104 effectively bypasses step 1106.
The process continues to step 1108, which represents the start of the second mode's third phase of the configuration resolution process, wherein a test is performed to determine whether the system has an administrator configuration, e.g., in the system directory. If not, step 1114 is executed, as described below. If so, step 1108 branches to step 1110 wherein the administrator configuration is interpreted to determine whether there is an instruction therein for replacing the current assembly version with another version. If a replacement instruction is found, step 1110 branches to step 1112 wherein the replacement is made, otherwise there is nothing to replace and step 1110 bypasses any replacement. In any event, the process continues to step 1114.
At this time, the appropriate assembly version is known, as specified in the manifest and as altered via any configuration instructions, as described above. Step 1114 enumerates any dependencies in the assembly manifest that corresponds to this appropriate assembly for handling in a similar manner. These and other identified assemblies may be handled in a similar manner so that the correct versions as specified in the configurations are bound to the application.
As can be seen from the foregoing detailed description, there is provided a method, system and infrastructure to version globally named objects in the system. Application authors may create safe, isolated applications by simply creating a declarative manifest that describes dependencies on these shared objects, without needing to be concerned with coding the application to adjust to the version of the assembly being used. By the present invention, assemblies can be safely shared and applications can be more completely isolated.
While the invention is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the invention to the specific form or forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention.
Cited Patent | Filing date | Publication date | Applicant | Title |
US4809170 * | Apr 22, 1987 | Feb 28, 1989 | Apollo Computer, Inc. | Computer device for aiding in the development of software system |
US5805899 * | Jul 6, 1995 | Sep 8, 1998 | Sun Microsystems, Inc. | Method and apparatus for internal versioning of objects using a mapfile |
US6560614 * | Nov 12, 1999 | May 6, 2003 | Xosoft Inc. | Nonintrusive update of files |
Citing Patent | Filing date | Publication date | Applicant | Title |
US7322025 * | Jul 17, 2003 | Jan 22, 2008 | Tata Consultancy Services Limited | Method and apparatus for versioning and configuration management of object models |
US7571442 | Feb 20, 2001 | Aug 4, 2009 | Worldwide Objects International Limited | Systems and methods for application programming using persistent objects |
US8104049 * | Aug 2, 2007 | Jan 24, 2012 | International Business Machines Corporation | Accessing a compatible library for an executable |
US8250530 * | May 27, 2009 | Aug 21, 2012 | Microsoft Corporation | Composite values for declarative language applications |
US8276121 | Jun 19, 2007 | Sep 25, 2012 | Microsoft Corporation | Selection of versioned resource among multiple compatible versions |
US8291401 * | Aug 7, 2008 | Oct 16, 2012 | International Business Machines Corporation | Processing symbols associated with shared assemblies |
US8291483 * | Apr 30, 2007 | Oct 16, 2012 | Hewlett-Packard Development Company, L.P. | Remote network device with security policy failsafe |
US8321852 * | Oct 19, 2010 | Nov 27, 2012 | Research In Motion Limited | System and method for extending a component-based application platform with custom services |
US8359572 * | Jan 8, 2008 | Jan 22, 2013 | Microsoft Corporation | Self-describing re-usable software components |
US8407666 * | Sep 20, 2010 | Mar 26, 2013 | Research In Motion Limited | System and method for generating component based applications |
US8776097 | Sep 14, 2011 | Jul 8, 2014 | Myspace, Llc | Dynamic native binding for managed assemblies |
US9009693 * | May 8, 2013 | Apr 14, 2015 | Microsoft Corporation | Out-of-band framework libraries within applications |
US9052968 * | Jan 17, 2011 | Jun 9, 2015 | International Business Machines Corporation | Methods and systems for linking objects across a mixed computer environment |
US9235458 | Jan 6, 2011 | Jan 12, 2016 | International Business Machines Corporation | Methods and systems for delegating work objects across a mixed computer environment |
US9417931 | Jun 24, 2008 | Aug 16, 2016 | Microsoft Technology Licensing, Llc | Unified metadata for external components |
US9542175 * | Jun 23, 2006 | Jan 10, 2017 | Oracle International Corporation | Continuous deployment |
US20030023769 * | Feb 20, 2001 | Jan 30, 2003 | Van Der Spuy Johannes C. | Application programming system and method of operation thereof |
US20040103393 * | Jul 17, 2003 | May 27, 2004 | Reddy Sreedhar Sannareddy | Method and apparatus for versioning and configuration management of object models |
US20070250574 * | Jun 23, 2006 | Oct 25, 2007 | Tseitlin Ariel D | Continuous deployment |
US20080065688 * | Sep 7, 2006 | Mar 13, 2008 | Research In Motion Limited | Mediated plug-in registration of client applications and content providers with push content delivery system |
US20080126988 * | Nov 19, 2007 | May 29, 2008 | Jayprakash Mudaliar | Application management tool |
US20080256514 * | Apr 10, 2007 | Oct 16, 2008 | Microsoft Corporation | Side-by-side application manifests for single-purpose applications |
US20080271135 * | Apr 30, 2007 | Oct 30, 2008 | Sherry Krell | Remote network device with security policy failsafe |
US20090037933 * | Aug 2, 2007 | Feb 5, 2009 | Shajith Chandran | Method and apparatus for accessing a compatible library for an executable |
US20090178026 * | Jan 8, 2008 | Jul 9, 2009 | Microsoft Corporation | Self-describing re-usable software components |
US20090319554 * | Jun 24, 2008 | Dec 24, 2009 | Microsoft Corporation | Unified metadata for external components |
US20090320007 * | Jun 24, 2008 | Dec 24, 2009 | Microsoft Corporation | Local metadata for external components |
US20100037208 * | Aug 7, 2008 | Feb 11, 2010 | International Business Machines Corporation | handle based method for side-by-side assemblies in a unix environment |
US20100306740 * | May 27, 2009 | Dec 2, 2010 | Microsoft Corporation | Composite values for declarative language applications |
US20110023013 * | Sep 20, 2010 | Jan 27, 2011 | Research In Motion Limited | System and Method For Generating Component Based Applications |
US20110035742 * | Oct 19, 2010 | Feb 10, 2011 | Research In Motion Limited | System and method for extending a component-based application platform with custom services |
US20120185837 * | Jan 17, 2011 | Jul 19, 2012 | International Business Machines Corporation | Methods and systems for linking objects across a mixed computer environment |
US20140337824 * | May 8, 2013 | Nov 13, 2014 | Microsoft Corporation | Out-of-band framework libraries within applications |
US20140380341 * | Jun 20, 2013 | Dec 25, 2014 | Microsoft Corporation | Application activation using decoupled versioning |
WO2012037270A1 * | Sep 14, 2011 | Mar 22, 2012 | Myspace, Inc. | Dynamic native binding for managed assemblies |
U.S. Classification | 717/162, 717/167, 717/164 |
International Classification | G06F9/44 |
Cooperative Classification | G06F9/44536, G06F8/71, G06F8/54 |
European Classification | G06F8/54, G06F8/71 |
Date | Code | Event | Description |
Dec 2, 2009 | FPAY | Fee payment | Year of fee payment: 4 |
Mar 30, 2010 | CC | Certificate of correction | |
Dec 30, 2013 | FPAY | Fee payment | Year of fee payment: 8 |
Dec 9, 2014 | AS | Assignment | Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034543/0001 Effective date: 20141014 |


text:
Project: Maplecroft
Deadline: October 15, 2013
New words written: 1550
Present total word count: 83,895 words
Things accomplished in fiction: Emma's had it up to HERE, y'all. But there's nowhere to go, and something awful is headed her way. She needs a better plan than "sit here and wait for what will come."
Next up: Not 100% confident which section goes next. Will sleep on it.
Things accomplished in real life: Daily jaunt around the neighborhood with the dog; tried to empty my inbox; worked on the yard a little, because it's about to storm - so I battened down the hatches, so to speak; put away the last of the laundry; did the dishes; took forever to get dressed.
Other: Heard from the nice lady at the historic zoning office. Looks like things are okay re: the new roof, so I ought to have all the right approvals within a couple of days. Honestly, it wasn't a big deal. The worse deal will be two days of men with scrapers and hammers and the like. (I say that, assuming nothing new and wacky will happen between now and me getting my Certificate of Appropriateness. Knock on wood.)
Bride of Other: Another somewhat early day, but like I said - needed to get out ahead of this afternoon's storm, and besides, there's a guy coming to measure for the garage door in a few minutes (in the storm? MAYBE), so I wanted to wrap up first. Besides, I'm kind of dragging today. Hellooooo allergy season. Woke up miserable, but am successfully medicated now.
Number of fiction words so far this year: 79,769


text:
yeah, im not doubting the kid at all...hes a beast, i was just puzzled by that award
I could see the questions here about receiving highschool accolades,
Meh, after paying attention a bit, you realize that those awards are given to big name guys. Beckwith was going to win it regardless of the season he had.
I always thought someone would give him a scholly to play QB though. He's such a playmaker, you have wonder what he'd do with the ball at the next level.
Is Beckwith the next Manti Teo?
quote:Riley played OLB at 245 lbs, and Beckwith looks like an even better athlete than he was.
But he's already listed at 225 before even getting to school. Has there been many OLB's @ LSU that's weighed 240-250?
Bama uses them because they can play that DE/LB hybrid, but in a 4-3, that's usually pushing the MLB range.
quote:Are you leery over Melvin Jones, as well?
No, because he's played QB most of his HS career. I understand he's played defense as well, but most of the time it was QB.
That's not a normal switch. But to each their own. If you guys see it, then I'm obviously missing it.
quote:Te'o may not be all he's hyped up to be but he's far from average.
The next average LB who takes advantage of great DT play?
Are you leery over Melvin Jones, as well?
What's that got to do with anything?
You people
He still hasn't canceled his official visit to LSU.
Advertising Info
Privacy Policy
Where to Watch LSU
Contact Us
© 2017 TigerDroppings.com. All Rights Reserved |


text:
Tropical Fish Keeping - Aquarium fish care and resources
- Beginner Planted Aquarium
- - Best Low Light Plants
Best Low Light Plants I have a 29 gallon blackwater tank with 2 Marineland double bright LEDs running 12 hours per day. i had my entire tank covered in live plants but half of them died off. i believe they died off because they were not supplied with enough light. the plants that did survive were the java ferns. because the tank is a blackwater tank, the lights are not as bright as they could be. what other types of low light plants would fit well in my tank? thank you for your help. |
anubias plants would do well in a low light system as well as floating plants. |
Can't spell plant names correctly, but I'll try to tell you low light plants :) Any of the crypts, anubias are great, amazon sword, wisteria, water sprite and anachreis. Under fish profiles there is a section for freshwater plants, click on that and scroll through profiles of plants there, and see what you come up with. Gwen |
It mayhave been light, but we shuld explore the entire setup just in case. Java Fern is notorious for surviving when other plants cannot. What is the substrate, and what nutrient fertilizers are being added and how often? One comment on the Wisteria, this will not do well if your light is the issue. I cannot grow Wisteria planted in the substrate in my tanks due to light. Same for all the Hygrophila species. Byron. |
i am using eco complete plant substrate mixed with flourite. then i use flora pride as a supplement. does that seem okay? |
I don't think this is the issue here, but when the Flora-Pride is gone, I would get hold of Seachem's Flourish Comprehensive Supplement. If is the only product known to me that is widely available and contains all essential nutrients [FP has only iron and potassium]. The enriched substrates obviously help, but this has no benefit for floating plants, non-substrate rooted plants (Java Fern, Anubias, moss, etc) and even some stem plants. Flourish Comp may seem expensive, but so little is used that it lasts a long time. In your 29g for instance, as little as 1/2 a teaspoon once a week is the recommended dose. So back to the original question, it may have been the light. You don't mention the plants that failed, but if stem plants were among them this would be logical as any fast growing plant (such as stem plants) require more light. Red-leaf plants also. I have never tried the LED light systems, but I have seen them in a local store and they seemed to be providing good light over smallish tanks (shallower than your 29g) so this may be an issue. The Anubias, some swords, and crypts already mentioned should manage. Water Sprite floating will, though this will block some light from reaching the lower plants. But floating plants are so useful and natural to forest fish that I always include them in my tanks. Byron. |
I would try mosses, crypts, vallisneria, dwarf sag (will grow tall, more like a vallisneria in low light),anubias... If you don't mind the plant only surviving for a year or two, then dwarf lilies, Crinum sp, and aponogetons would be great. (They have bulbs where they store their starch reserves) |
I knew following 3: Anubias congensis Anubias minima Aponogeton ulvaceus |
All times are GMT -5. The time now is 10:52 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
vBulletin Security provided by
vBSecurity v2.2.2 (Pro) -
vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
User Alert System provided by
Advanced User Tagging (Pro) -
vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.


text:
Minnesota Twins pitcher Trevor Plouffe went hiking recently and reported that the view is so wonderful that it brings a tear to his eye.
Allow Mr. Plouffe to introduce you to his wife, Olivia – helping him enjoy the "scenery" since their January wedding.
These mountains bring a tear to my eye. pic.twitter.com/xzGHKLd2Fv
— Trevor Plouffe (@TPlouffe24) October 22, 2013
[H/T: The Big Lead]


text: Guacamelee!'s New DLC Challenges Are Hard As HellSteve Marinconz7/25/13 12:45pmFiled to: GuacameleeWatch ThisPs3Kotakucore401EditPromoteShare to KinjaToggle Conversation toolsGo to permalinkThe Diablo's Domain DLC was released Tuesday, and it adds a new area, El Infierno. Guacamelee's hell zone adds a series of challenge rooms and is also filled with well-dressed skeletons desperate for some paperwork to do, and more of the game's many easter eggs. Check out the video above for a look at the trip through Desierto Caliente, and a taste of the challenges that await in El Infierno. Reply40 repliesLeave a reply