text:
Mary Ann Stockberger Retires from The Farmers Bank

Mary Ann Stockberger retired from The Farmers Bank, effective Tuesday, January 2, 2018.  Mary Ann began her employment at the bank in August 1976 in the bookkeeping department.  She has provided over 35 years of dedicated service to The Farmers Bank serving in many different roles and departments.  Mary Ann most recently served as Merchant Services Manager.

Mary Ann and her husband, Ron reside in Frankfort.  They have two children, Kristy (Dan) Miller and Kreg Stockberger.  In her spare time, she enjoys spending time with her family, traveling, walking, and being outdoors.  Congratulations Mary Ann, you will be missed!

The Farmers Bank is a $550 million asset organization chartered in 1876 with headquarters in Frankfort, IN.  The Farmers Bank is locally owned and operated with 9 banking offices located in Central Indiana providing retail, business, trust & asset management, investment, mortgage, and electronic banking services.  Member FDIC, Equal Housing Lender.


Content-Type: application/http; msgtype=response

WARC-Identified-Payload-Type: text/html

WARC-Type: response

text:
Smart Use of Antibiotics Leads to Best Care

Each year in the United States, at least 2 million people become infected with bacteria that are resistant to antibiotics, and at least 35,000 people die as a direct result, according to the Centers for Disease Control and Prevention (CDC). Many more die of complications from antibiotic-resistant infections.

Antibiotics save lives and are critical tools for treating a number of common and more serious bacterial infections, but improper use of these medications can lead to drug resistance that can be life-threatening.

U.S. Antibiotics Awareness Week, which runs from Nov. 18 to 24, is an opportunity to learn about good antibiotic prescribing practices and use. Antibiotic resistance occurs when bacteria develop the ability to defeat the drugs designed to kill them. The CDC states that antibiotic resistance is one of the most urgent threats to the public’s health.

“Antibiotics are an essential part of combatting a number of common infections, including pneumonia and sepsis,” said State Health Commissioner Kris Box, M.D., FACOG. “But when antibiotics aren’t needed, the side effects could still cause harm.”

The CDC says at least 30 percent of the antibiotics in outpatient settings nationwide are prescribed unnecessarily. Improving the way healthcare professionals prescribe antibiotics, and the way patients use antibiotics, will help keep Hoosiers healthy, prevent fight antibiotic resistance, and ensure that these lifesaving medications will be available for future generations.

The best ways to help prevent the spread of antibiotic resistance are to:

  • Talk to your healthcare provider about measures to relieve symptoms without using antibiotics.
  • Take prescribed antibiotics exactly as directed by your healthcare provider.
  • Never pressure your healthcare provider for an antibiotic prescription.
  • Never save antibiotics for the next time you’re sick.
  • Remember that antibiotics won’t make you feel better if you have a virus.
  • Stay healthy and keep others healthy by cleaning hands, covering coughs, staying home when you are sick and getting recommended vaccines.

This is the week to be antibiotics aware for year-round smart use and best care. Visit to learn more about antibiotic prescribing and use.

Visit the Indiana Department of Health at or follow us on Twitter at @StateHealthIN and on Facebook at

Be the first to comment

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

warcinfo:
isPartOf: CC-MAIN-2021-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-99
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/


text:
Cloudbric Launches As An Independent Startup Following Immense Growth in 2017

Website security provider Cloudbric has announced its split from web and data security enterprise provider Penta Security Systems, thereby creating two independent companies with distinct business strategies beginning December 1, 2017. With over 20 years of IT expertise, Penta Security Systems first created Cloudbric as an in-house venture with the idea of bringing accessible security to all. The separation best positions Cloudbric and Penta Security Systems to capitalize on their respective expertise in the rapidly changing cybersecurity landscape.

The decision to separate has provided Cloudbric with the independence and flexibility it needs to grow its cloud-based web security services, as it strays away from traditional software and hardware appliances. Following this current trend in cloud computing has enabled Cloudbric to have a more competitive edge by allowing it to react to market and consumer demands more quickly. The split will advance Cloudbric’s growth trajectory and also allow both companies to develop their own vision and core values.

Cloudbric has already seen tremendous growth, acquiring 27 IDCs (Internet Data Centers), 50 partnerships, and 8,000 user sign-ups all within the span of the past fiscal year. Consisting of young and talented core members, developers, security analysts and researchers, Cloudbric was able to realize these accomplishments and more. With the Korean government pouring millions into funding startups and small businesses with grants and other tax incentives, Cloudbric, too, has successfully received its first round of investments from not only the Korean government but also secured investments from a local venture capital firm. Currently at a $10 million business valuation, Cloudbric expects to see even more venture capital funding in the near future.

“In order to reach a wider range of websites and establish a global presence, the Cloudbric team is constantly evaluating and exploring new opportunities to optimize our service and create value for investors. Because we now have the opportunity to fully realize our growth potential, our commitment to helping users become secure online is now greater than ever. Our goal is to generate long-term value for our customers,” says TJ Jung, newly named CEO of Cloudbric.

Cloudbric is looking to take on creative approaches to grow its service in the upcoming year through innovative projects that incorporate elements of deep learning and blockchain technologies. With a mission to help even the smallest organizations attain accessible security, Cloudbric is moving closer to achieving that goal with its projects and global partnerships. The company will continue to explore alternative business opportunities for its global expansion.

Have more questions? Submit a request


text:
Cliff Bleszinski

Clifford Bleszinski

Bleszinski presenting at the 2016 Game Developers Conference
Born Clifford Michael Bleszinski
(1975-02-12) February 12, 1975
North Andover, Massachusetts, U.S.
Residence Raleigh, North Carolina, U.S.
Other names CliffyB, Dude Huge[1]
Occupation Game designer
Spouse(s) Lauren Bleszinski

Clifford Michael Bleszinski (born February 12, 1975), popularly known as CliffyB, is an American video game designer, former design director for the game development company Epic Games, and the co-founder of Boss Key Productions. He is known for his role in the development of the Unreal franchise, especially 1999's Unreal Tournament, and the Gears of War franchise.[2]

Cliff Bleszinski made his first non-commercial game at the age of 11.[3] His first commercial game was made at age 17, an independently developed point-and-click adventure game called "The Palace of Deceit: Dragon's Plight".[4][5] Bleszinski created the game while he was a student at Bonita High School in La Verne, California, and released it in 1991 via his own company, Game Syndicate Productions. He sent a copy of the game to Tim Sweeney, the founder of Epic Games (then known as Epic MegaGames).[6] Sweeney was impressed with the game and hired Bleszinski to work at Epic.[7][8]

Epic Games

His next game was Dare to Dream, a point-and-click adventure, released in 1993. Bleszinski worked on one of Epic's first multi-person projects brought, 1994's Jazz Jackrabbit followed by 1998's Jazz Jackrabbit 2, and designed the first-person shooter game Unreal Tournament.[9]

In addition to his work on the Unreal series, Bleszinski served as lead designer on the Xbox 360 shooter Gears of War and its sequel, Gears of War 2. Gears evolved out of the development of what was going to be a game called Unreal Warfare.[10] As Bleszinski explained in a speech at GDC 2007 entitled "Designing Gears of War: Iteration Wins," the game started out as another first-person shooter in the Unreal universe.[11] Over time, however, influenced by the cover mechanic in Namco's 2003 game Kill Switch and the third-person Resident Evil 4,[12] Unreal Warfare became the game known as Gears of War. On April 12, 2010, he appeared on NBC's Late Night with Jimmy Fallon to promote Gears of War 3,[13][14] his last game for the company.[15][16]

Bleszinski at the Gears of War event at the Hollywood Forever Cemetery, 2006

Bleszinski is one of the creators of Epic Game's Infinity Blade, released in 2010. It is the first mobile game that he designed.[17]

Cliff announced his departure from Epic Games on October 3, 2012 after 20 years with the company, saying he had been making video games since he was a teen and wanted to take a break.[18][19]

Boss Key Productions

After a 2-year hiatus,[20][21] he announced a free-to-play, PC-focused arena shooter code-named BlueStreak created by Boss Key Productions, his new studio.[22][23][24]

On August 26, 2015, Cliff Bleszinksi revealed the first details about his upcoming free-to-play arena shooter, previously known as BlueStreak. The game, which is due out some time in 2016 and going to be published by Nexon, will be called LawBreakers.[25]

Cliff Bleszinski was offered an opportunity to work on the Silent Hill franchise by Hideo Kojima, vice president of Konami Digital Entertainment.[26][27] "I was flattered but declined," he wrote on Twitter.[27]

Bleszinski joined the board of advisers for Fig, a mixed crowd-funding/investment platform for video games, in May 2016.[28]

Personal life

Cliff is married to blogger Lauren Bleszinski (née Berggren).[29] One of his brothers is Tyler Bleszinski, a sports blogger who founded Athletics Nation and Vox Media. His father, whom Bleszinski describes as a "very stressed-out guy," was an engineer for Polaroid.[6] The nickname "CliffyB" was given to him derogatorily by "some jock kid" when he was a shy teenager; he then took it and developed a tougher persona around it.[6] In 2008, he expressed a desire to retire the CliffyB moniker, saying it's "time to grow up a bit".[30] Bleszinski is an atheist[31] (although he can sometimes be seen wearing a cross—see this pic [32]).

Bleszinski has opened two bars in Raleigh, North Carolina, one in 2014, called The Station,[33] and another one in 2015, The Raleigh Beer Garden.[34]

Bleszinski at PAX Prime 2012

Video games

  1. Ashcraft, Brian (April 8, 2010). "Why We Call Him Dude Huge". Kotaku. Retrieved October 3, 2012.
  2. Gaudiosi, John (July 21, 2014). "Interview: Legendary designer Cliff Bleszinski discusses the future of free-to-play shooters". PC World. International Data Group. Retrieved October 9, 2014.
  3. "Cliff Bleszinski (Person) - Giant Bomb". Retrieved 2016-03-14.
  4. Alexander, Leigh (February 18, 2014). "With new perspective on life and games, Cliff Bleszinski plots next move". Gamasutra. UBM plc. Retrieved October 9, 2014.
  5. Hsu, Dan (January 22, 2013). "Life after Epic: Getting to know Cliff Bleszinski (exclusive interview, part one: his past)". VentureBeat. Retrieved October 9, 2014.
  6. 1 2 3 Bissel, Tom (November 3, 2008). "The Grammar of Fun. CliffyB and the world of the video game". The New Yorker. Condé Nast. Retrieved December 24, 2014.
  7. Cobbett, Richard (12 July 2014). "Saturday Crapshoot: The Palace Of Deceit". PC Gamer. Retrieved 29 October 2016.
  8. K. Ohnesorge, Lauren (September 25, 2014). "Exclusive: Q&A with the boss behind Boss Key Productions: Cliff Bleszinski". Triangle Business Journal. American City Business Journals. Retrieved October 8, 2014.
  9. Reinhart, Brandon (June 9, 2000). "Postmortem: Epic Games' Unreal Tournament". Gamasutra. UBM plc. Retrieved October 11, 2016.
  10. Kuchera, Ben (May 7, 2012). "How Gears of War rose from the ashes of a scrapped Unreal title called "Warfare"". The Penny Arcade Report. Retrieved April 21, 2016.
  11. Dobson, Jason (March 12, 2007). "Post-GDC: Cliff Bleszinski Says Iteration Won Gears of War". Gamasutra. Retrieved April 21, 2016.
  12. Carlson, Alex (June 5, 2014). "How Gears of War Was the Xbox 360's Smartest Game". Hardcore Gamer. Retrieved April 21, 2016.
  13. Butts, Steve (April 12, 2010). "Gears Of War 3 On Jimmy Fallon". IGN. Retrieved October 9, 2014.
  14. Narcisse, Evan (April 13, 2010). "The Techland Interview: Cliff Bleszinski, Part 1". Techland Time. Retrieved October 9, 2014.
  15. Hoggings, Tom (September 19, 2011). "Gears of War 3 interview: Cliff Bleszinski". The Daily Telegraph. Telegraph Media Group. Retrieved October 9, 2014.
  16. Killingsworth, Jason (September 29, 2011). "Cliff Bleszinski interview". Edge. Future plc. Retrieved October 9, 2014.
  17. "GDC: Exclusive Interview-Epic Games CliffyB Cliff Bleszinski Talks Infinity Blade Dungeons & more by GamerLiveTV - 2016-03-15". Retrieved 2016-03-16.
  18. Epic Games (October 3, 2012). "Cliff Bleszinski Departs Epic". Epic Games Community. Epic Games. Archived from the original on October 4, 2012. Retrieved November 21, 2012.
  19. Makuch, Eddie (October 3, 2012). "Cliff Bleszinski out at Epic Games". GameSpot. Retrieved October 8, 2012.
  20. Makuch, Eddie (July 3, 2014). "Gears of War Veteran Developer Cliff Bleszinski "Coming Out Of Retirement"". GameSpot. CBS Interactive. Retrieved October 9, 2014.
  21. Hsu, Dan (July 21, 2014). "Cliff Bleszinski on his retirement, returning, what he's learned, and where he's going from here (interview)". VentureBeat. Retrieved October 9, 2014.
  22. 1 2 Campbell, Evan (July 8, 2014). "Gear of War Designer Cliff Bleszinski announces F2P shooter BlueStreak". IGN. Retrieved July 28, 2014.
  23. LeJacq, Yannick (July 8, 2014). "Cliff Bleszinski's Next Game Is A Free-To-Play Shooter". Kotaku. Retrieved September 27, 2014.
  24. Lahti, Evan (July 23, 2014). "Interview: Cliff Bleszinski on Project BlueStreak, PC gaming, FPS design, moddability". PC Gamer. Future plc. Retrieved October 9, 2014.
  25. Karmali, Luke (August 26, 2015). "Gears of War Creator Cliff Bleszinski Announces New Game LawBreakers". IGN. Retrieved August 26, 2015.
  26. "Cliff Bleszinski Turned Down A Chance to Work With Hideo Kojima on Silent Hills". Shacknews. Retrieved 2016-03-14.
  27. 1 2 Sirani, By Jordan. "Kojima Wanted to Make Silent Hills With Gears of War Creator Cliff Bleszinski". IGN. Retrieved 2016-03-14.
  28. Nutt, Christian (May 10, 2016). "Cliff Bleszinski invests in crowdfunding platform Fig". Gamasutra. Retrieved May 10, 2016.
  29. Kumpan, Sean (March 12, 2013). "EL337 Level: Interview with Lauren Bleszinski". PS Home Gazette. Archived from the original on 15 March 2013. Retrieved October 9, 2014.
  30. Blog post on MTV Multiplayer. (2008-05-21). Retrieved on 2012-11-21.
  31. "Twitter / therealcliffyb: And I'm not Jewish. I'm an Atheist". 2013-06-19. Retrieved 2014-02-11.
  32. Bleszinski at the Gears of War 2 launch event in Universal City Walk, LA in 2008. Retrieved 5 Oct 2016.
  33. Gaudiosi, John (July 22, 2014). "From Gears to Beers: A Video Game Mogul Opens a Restaurant". Men's Journal. Retrieved July 28, 2014.
  34. Weigl, Andrea (17 July 2015). "Raleigh Beer Garden to open Tuesday". The News & Observer. The McClatchy Company. Retrieved 20 July 2015.
  35. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 "Mobygames Developer BIO". Retrieved 2011-02-07.
  36. Brown, David (February 18, 2011). "Bulletstorm developer interview: Cliff Bleszinski". The Daily Telegraph. Telegraph Media Group. Retrieved October 9, 2014.
  37. Hall, Charlie (July 11, 2014). "Cliff Bleszinski's next game level is being made in Poland right now". Polygon. Vox Media. Retrieved July 15, 2014.
  38. jgaudiosi (September 26, 2006). ""Stay Alive" Hits DVD". videogames.typepad. Retrieved 2014-08-03.
  39. "WARREN SPECTOR TRIBUTE with Cliff Bleszinski". YouTube. Retrieved 2012-08-08.
  40. "SAKAGUCHI'S FINAL FANTASY". YouTube. Retrieved 2015-03-06.
  41. "Jake and Amir: The Hot Date presented by Gears of War 3". YouTube. Retrieved 2016-11-25.
  42. "Sonic For Hire – Gears of War". YouTube. Retrieved 2013-01-05.
  43. "Class in session! Video Game High School 2 Ep. 1 is live". Destructoid. 2013-07-26.
  44. Makedonski, Brett (2014-03-25). "Cliffy B chooses you to die in this Pokemon rap". Destructoid. Retrieved 2014-03-26.
  46. "The Golden Sins Of Horror Games (The Jimquisition)". YouTube. October 31, 2015. Retrieved November 25, 2016.
Wikimedia Commons has media related to Cliff Bleszinski.
This article is issued from Wikipedia - version of the 11/27/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.


WARC-Identified-Payload-Type: application/xhtml+xml

text:
CMF / CRF Details

CMF ID: 7750

Install shoulder rumble strips

Prior Condition: Roadways without should rumble strips

Category: Shoulder treatments

Study: Validation and Application of Highway Safety Manual (Part D) in Florida, Abdel-Aty et al., 2014

Star Quality Rating: 2 Stars   [View score details]
Rating Points Total: 70
Crash Modification Factor (CMF)
Value: 0.6
Adjusted Standard Error:
Unadjusted Standard Error: 0.09
Crash Reduction Factor (CRF)
Value: 40   (This value indicates a decrease in crashes)
Adjusted Standard Error:
Unadjusted Standard Error: 9
Crash Type: Run off road
Crash Severity: All
Roadway Types: Not specified
Number of Lanes: >2
Road Division Type: All
Speed Limit: 45-70
Area Type: Rural
Traffic Volume: Minimum of 2000 to Maximum of 50000 Annual Average Daily Traffic (AADT)
Average Traffic Volume:
Time of Day: All
If countermeasure is intersection-based
Intersection Type:
Intersection Geometry:
Traffic Control:
Major Road Traffic Volume:
Minor Road Traffic Volume:
Average Major Road Volume :
Average Minor Road Volume :
Development Details
Date Range of Data Used: 2005 to 2010
State: FL
Country: USA
Type of Methodology Used: 1
Sample Size (sites): 27 sites before, 27 sites after
Sample Size (site-years): 54 site-years before, 54 site-years after
Sample Size (miles): 38.684 miles before, 38.684 miles after
Sample Size (miles): 77.4 mile-years before, 77.4 mile-years after
Other Details
Included in Highway Safety Manual? No
Date Added to Clearinghouse: Mar-08-2016
Comments: CMFs of installing shoulder rumble strips on rural multi-lane highways apply to single-vehicle run-off-road crashes The number of crashes in the after period were not reported in this study, however, they have been recorded as 300 to give 10 points as a beneift of doubt for one or more of the following: (1) number of miles/sites in the reference/treatment group, (2) number of crashes in the references/treatment group, (3) reporting AADTs for the aggregate dataset but not for the disaggragate dataset used for CMF development.


text:
Writing Prompt

Snow White Stories

At first glance, Snow White is basically a variant of Cinderella. A young, pretty Protagonist is treated badly by her step-mother (although in older versions it's actually her biological mother) who is jealous of her. The [step-]mother tries to kill Cinder- sorry - Snow White instead of merely mistreating her. Aided by her Friends (for… Continue reading Snow White Stories


text:
Dzambala statue painted by Chia

2009年5月11日 星期一 上午2:17 评论关闭

This Dzambala statue face is painted by Chia, which include the eyebrows, eyes, hair and lip. Joy, James and Tamara helped Chia to do some correction to make the painting perfect. Beautiful traditional Tibetan deities statues brought to you by Kechara Saraswati Arts Department (


text:
What is Ayurveda based on?

What are the 5 principles of Ayurveda?

The five mahabhutas are Akasa,Vayu, Agni,Ap or jala and Prthivi . viz – Sound,Touch,Vision, Taste,and Smell are their properties respectively . According to Ayurveda everything in Universe is composed of the Pancamahabhutas – Akasa Space), Vayu (Air), Teja or Agni(Fire),Jala(Water)and Prithvi (Earth).

Is ayurvedic medicine scientifically proven?

There is no good evidence that Ayurveda is effective for treating any disease. Ayurvedic preparations have been found to contain lead, mercury, and arsenic, substances known to be harmful to humans.

What is Ayurveda and its practice?

Ayurveda, or ayurvedic medicine, is a healthy-lifestyle system that people in India have used for more than 5,000 years. Ayurveda emphasizes good health and prevention and treatment of illness through lifestyle practices (such as massage, meditation, yoga, and dietary changes) and the use of herbal remedies.

Is Ayurveda really effective?

Ayurvedic treatment is although highly effective; proper mode of action, pharmacology, pharmacokinetics, and pharmacovigilance of many important Ayurvedic drugs are still not fully explored.

Are Ayurvedic doctors real doctors?

AYUSH Minister Shripad Naik said that Ayurvedic doctors are educated at par with allopathic practitioners and they are even trained to perform surgeries. He further said “After completing their studies, the ayurvedic doctors undergo internship for one year. They are trained surgeons.”

IT IS INTERESTING:  Why is Sulphur used in homeopathy?

What is my Ayurvedic body type?

Ayurveda follows the concept of understanding the doshas in order to heal oneself. The three ayurvedic body types, or doshas, are Vata, Pitta and Kapha. Each type of dosha has a unique set of characteristics and the body type of a person depends on their physical and emotional attributes.

What is Ayurveda body type?

Ayurveda describes 7 basic body-types:

Vata/Pitta (pitta/vata) – bidoshic body-type. Pitta/Kapha (kapha/pitta) – bidoshic body type. Kapha/Vata (vata/kapha) – bidoshic body type. Vata/Pitta/Kapha – tridoshic body type which is rare.

What is Kapha body type?

Kapha individuals have a big body frame and stocky body. They have smooth, oily and lustrous skin. They sweat easily. Kapha people have thick, long, wavy, lustrous, brown hairs. Their eyes are brown, large and oval shape with clear white sclera.

Is Ayurvedic medicine have side effects?

Ayurvedic medicines may be beneficial to health, but are not devoid of adverse effects. Adverse events may be due to adulteration or some inherent constituents like alkaloids. Adverse effects and adverse events are not the same thing.

What are the disadvantages of Ayurvedic medicine?

Ayurvedic herbal medicines, like conventional medicines, may cause side effects, trigger allergic reactions, or interact with other medicines or herbs you are taking. Some ayurvedic medicines may contain high levels of heavy metals, which may be harmful to your body.


text:
About me quotes for dating profile

By Judith Silverstein, Michael Lasky. In addition to displaying a screen name, many online-dating sites allow you to display a phrase, called a tagline. Some sites, such as Match. That option can be a bit overwhelming, though, so go with a relatively short name and focus your creative juices on the tagline. If you try to be too creative with both, they tend to conflict and create a confused message. Do a search on your site to see which is more prominent — taglines or screen names. Focus on refining whichever one is more visible.

51 Best Dating Quotes

It is true. I, Michael Scott, am signing up with an online dating service. Thousands of people have done it, and I am going to do it. I need a username, and I have a great one.

Tough and Determined. Tough times never last, but tough people do. -.

Want something completely different. Our nation is fine, dating profile examples of dating headline. Things that, and will attract the headline of screen international, many different. Best reviews quotes on here are some great pof headlines. How insert funny dating headline. Share your dating quotes you in the best headlines quotes to display a damn good headlines that express you need them. Shop for dating headlines quotes for dating profile? Things that suits your dating profile quotes for best price dating headlines, but avoid writing prose which is fine, or blog post.

Happy birthday to come up with movie quotes and quote them in the best dating profile is similar to get a hot dude. The best dating sites allow you know what circles the document gives a good headlines are some of dating sites headlines. We have some perfect pof headlines to find the latest film news headlines and get a dating profile headlines quotes.

Funny Dating Quotes Worthy of a Chuckle

If you are looking for love online, a great profile is key. Of course you need compelling photos, but those who are looking for a real relationship will look beyond a pretty face to find out what you are about. It would be nice if everyone could give you the benefit of the doubt and magically see what a fascinating, unique, loving person you are, but that’s not how online dating works. A generic profile that doesn’t say much or says the wrong things will be overlooked by the very people you truly hope to connect with.

There are lots of quality singles online.

Funny online dating quotes. I thought modern day. Wsj online dating profile quotes selected by megan murray. Because women, funny dating has been slowly.

Catchy dating headlines. Creativity can be the difference between a Yes and a No. That above exchange is little more than asking for a phone number, sites the execution is novel. Not as clever for the ones before, but straightforward mixed with unexpected can have pretty good results. We know liners a lot of you who are reading this dating creative in your own ways.

Hit us with your best pick-up lines in the comments below. Whether clever, funny, or downright serious, give us your best shot and try to swoon us with one line. If none of these appeal to you, keep going headlines check out our collection of hilarious Tinder pick-up lines worth trying.

Picking a Tagline to Enhance Your Online Dating Profile

At Everyday Power, we have compiled these relatable dating quotes sharing experiences and lessons learned from people all around the globe. No matter what you are dealing with, it can be difficult to find a perspective that you can relate to. Today, we are diving into dating from a variety of perspectives including falling in love, online dating, and dealing with heartbreak.

If you show up in a masquerade outfit, neither is going to happen. Hunting for ways to be engaging.

60 quotes have been tagged as online-dating: Julie Spira: ‘Patience is a virtue and the best things in life are worth waiting for.’, Jayne Higgins: ‘Take.

Come up with a free russian online dating sites clever instagram bios with pinterest. No tinder bios: Stop saying ‘love is fast-paced, no one of great examples and ideas: One of romantic instagram bio is love’ and all? Find thousands of these sweet or hashtags and girls. Who has to write the official and connect with some great examples and then maybe.

Yea, absolutely not reveal your instagram bios on your bio quotes and twitter bios: Never stress about cute couple selfies, cute guys, on instagram bios on instagram has a boyfriend-filled boost, of women, and snarky. Link to help your instagram bio that school photos 75 at https: There was a man can see a date jisoo, of funny how to add to examples. Consider this, and photos 75 at times agonizing.

15 Funny Dating Profile Quotes to Get the Conversation Going

Flirty quotes are some of your online dating profile examples for man. See our tagline. Dating quotes on the subject of a clear frontrunner. Dowager countess may be?

Hopeful and Inspirational.

StricktlyDating is an Australian writer who creates pages of original funny quotes and status updates. If you’re struggling with what to write in your online dating profile, this is the place for you! In this article, you’ll find a huge collection of funny, sweet, and cheeky quotes and statements to enhance your profile. This includes some words to describe yourself, statements about what you’re looking for in your life and in a partner, and some simple hints for creating a successful dating profile.

Sign in or sign up and post using a HubPages Network account. Comments are not for promoting your articles or other sites. Great variety of quotes for online dating. I tried online dating in my twenties. I made sure to meet at safe places like coffee shops or restaurants. I had fun meeting a variety of guys but never met one that felt like ‘the one’.

Great hub. What you mention in this hub will hopefully be of great use. See if it increase my online presence for the ladies.. I am so glad I don’t have to do the online dating thing, but you give some excellent and entertaining lines for attracting interest.

Relationship Humor | ex quotes + relationship

Commentary: This week on Love Syncs, an official glossary of the phrases to avoid on dating apps. It took three swipes on Bumble to find a profile bio with the sentence, “I’m an open book, just ask. That might be the least surprising lede I’ve ever written for an article. If you’ve spent any time on The Apps, you’ve likely noticed there’s a sameness of language that pervades many bios. There are phrases that crop up over and over again: “Just say hi.

There’s a corner of my brain that keeps inconsequential conspiracy theories stored away like that one tin can of French-cut green beans you’re never in the mood for.

Online Dating Profile Headlines And Profile Examples. Online building a writing profile around an archtype, you give yourself the advantage profile working.

Hit enter to search or ESC to close. Get better captions are some new insta bios examples. Still need guidance? Fortunately, internet dating site addiction photos. Or follow him on instagram profile for instagram bios, including funny instagram bio quotes for instagram bios ideas about quotes cute girls! Getting the more relationships go on instagram photos.

Babe, including funny bone.

Dating Quote


text:
Code of the District of Columbia

§ 22–901. Definitions.

For the purposes of this chapter, the term:

(1) “Counterfeit mark” means:

(A) Any unauthorized reproduction or copy of intellectual property; or

(B) Intellectual property affixed to any item knowingly sold, offered for sale, manufactured, or distributed, or identifying services offered or rendered, without the authority of the owner of the intellectual property.

(2) “Intellectual property” means any trademark, service mark, trade name, label, term, picture, seal, word, or advertisement or any combination of these adopted or used by a person to identify such person’s goods or services and which is lawfully filed for record in the Office of the Secretary of State of any state or which the exclusive right to reproduce is guaranteed under the laws of the United States or the District of Columbia.

(3) “Retail value” means the counterfeiter’s regular selling price for the item or service bearing or identified by the counterfeit mark. In the case of items bearing a counterfeit mark which are components of a finished product, the retail value shall be the counterfeiter’s regular selling price of the finished product on or in which the component would be utilized.


text:
U+10A45 was added to Unicode in version 4.1 (2005). It belongs to the block Kharoshthi in the Supplementary Multilingual Plane.

This character is a Other Number and is mainly used in the Kharoshthi script. The codepoint has the Numeric value 20.

The glyph is not a composition. It has a Neutral East Asian Width. In bidirectional context it acts as Right To Left and is not mirrored. In text U+10A45 behaves as Alphabetic regarding line breaks. It has type Other for sentence and Other for word breaks. The Grapheme Cluster Break is Any.

The Wikipedia has the following information about this codepoint:

The Kharoṣṭhī script is an ancient script used by the ancient Gandhara culture of South Asia primarily in modern-day Afghanistan and Pakistan to write the Gāndhārī language (a prakrit) and the Sanskrit language. An alphasyllabary, it was in use from the middle of the 3rd century BCE until it died out in its homeland around the 3rd century CE. It was also in use in Bactria, Gandhara (particularly in the period of the Kushan Empire), Sogdiana and along the Silk Road, where there is some evidence it may have survived until the 7th century in the remote way stations of Khotan and Niya. Kharoṣṭhī is encoded in the Unicode range U+10A00–U+10A5F, from version 4.1.0.

System Representation
UTF-8 F0 90 A9 85
UTF-16 D8 02 DE 45
UTF-32 00 01 0A 45
URL-Quoted %F0%90%A9%85
HTML-Escape 𐩅
Wrong windows-1252 Mojibake ð©

Complete Record

Property Value
Age (age) 4.1
Unicode 1 Name (na1)
Block (blk) Kharoshthi
General Category (gc) Other Number
Script (sc) Kharoshthi
Bidirectional Category (bc) Right To Left
Combining Class (ccc) Not Reordered
Decomposition Type (dt) None
Decomposition Mapping (dm) 𐩅
Lowercase (Lower)
Simple Lowercase Mapping (slc) 𐩅
Lowercase Mapping (lc) 𐩅
Uppercase (Upper)
Simple Uppercase Mapping (suc) 𐩅
Uppercase Mapping (uc) 𐩅
Simple Titlecase Mapping (stc) 𐩅
Titlecase Mapping (tc) 𐩅
Case Folding (cf) 𐩅
ASCII Hex Digit (AHex)
Alphabetic (Alpha)
Bidi Control (Bidi_C)
Bidi Mirrored (Bidi_M)
Bidi Paired Bracket (bpb) 𐩅
Bidi Paired Bracket Type (bpt) None
Cased (Cased)
Composition Exclusion (CE)
Case Ignorable (CI)
Full Composition Exclusion (Comp_Ex)
Changes When Casefolded (CWCF)
Changes When Casemapped (CWCM)
Changes When NFKC Casefolded (CWKCF)
Changes When Lowercased (CWL)
Changes When Titlecased (CWT)
Changes When Uppercased (CWU)
Dash (Dash)
Deprecated (Dep)
Default Ignorable Code Point (DI)
Diacritic (Dia)
East Asian Width (ea) Neutral
Extender (Ext)
FC NFKC Closure (FC_NFKC) 𐩅
Grapheme Cluster Break (GCB) Any
Grapheme Base (Gr_Base)
Grapheme Extend (Gr_Ext)
Hex Digit (Hex)
Hangul Syllable Type (hst) Not Applicable
Hyphen (Hyphen)
ID Continue (IDC)
Ideographic (Ideo)
ID Start (IDS)
IDS Binary Operator (IDSB)
IDS Trinary Operator and (IDST)
Indic Positional Category (InPC) NA
Indic Syllabic Category (InSC) Number
ISO 10646 Comment (isc)
Joining Group (jg) No_Joining_Group
Join Control (Join_C)
Jamo Short Name (JSN)
Joining Type (jt) Non Joining
Line Break (lb) Alphabetic
Logical Order Exception (LOE)
Math (Math)
Noncharacter Code Point (NChar)
NFC Quick Check (NFC_QC) Yes
NFD Quick Check (NFD_QC) Yes
NFKC Casefold (NFKC_CF) 𐩅
NFKC Quick Check (NFKC_QC) Yes
NFKD Quick Check (NFKD_QC) Yes
Numeric Type (nt) Numeric
Numeric Value (nv) 20
Other Alphabetic (OAlpha)
Other Default Ignorable Code Point (ODI)
Other Grapheme Extend (OGr_Ext)
Other ID Continue (OIDC)
Other ID Start (OIDS)
Other Lowercase (OLower)
Other Math (OMath)
Other Uppercase (OUpper)
Pattern Syntax (Pat_Syn)
Pattern White Space (Pat_WS)
Quotation Mark (QMark)
Radical (Radical)
Sentence Break (SB) Other
Simple Case Folding (scf) 𐩅
Script Extension (scx) Kharoshthi
Soft Dotted (SD)
STerm (STerm)
Terminal Punctuation (Term)
Unified Ideograph (UIdeo)
Variation Selector (VS)
Word Break (WB) Other
White Space (WSpace)
XID Continue (XIDC)
XID Start (XIDS)
Expands On NFC (XO_NFC)
Expands On NFD (XO_NFD)
Expands On NFKC (XO_NFKC)
Expands On NFKD (XO_NFKD)


text:
Click here to Skip to main content
15,116,277 members
Articles / Artificial Intelligence
Posted 11 Sep 2008

141 bookmarked

Contract Model for Manageable Services

Rate me:
Please Sign up or sign in to vote.
4.98/5 (71 votes)
11 Sep 2008CPOL33 min read
This article describes the design and implementation of the Repository Tool to create and manage contracts for virtual (manageable) services.

  • Repository of the metadata for Contract Model
  • Contract Model of the endpoints, bindings, contracts, operations, messages, schemas, WSDL
  • Manually creating and editing metadata in the Repository
  • Importing contracts from endpoints (WSDL, Mex)
  • Importing contracts from assemblies
  • Drag & Drop metadata into Repository
  • Compounding metadata for operations, messages, etc. into the Virtual Contract
  • Creating Virtual Endpoints
  • Compiling schemas, messages, operations, and contracts
  • Exporting (generating) metadata for endpoints
  • Repository Service to discover metadata (WS-Transfer Get, etc.) hosting by Windows NT Service
  • Built-in client tester driven by the svcutil program
  • Export-Import loopback test
  • Built-in MMC Framework
  • SQL schema for storage
  • Implementation using LINQ-SQL, MMC 3.0, and .NetFX 3.5 technologies

Introduction and Concept

The latest Microsoft .NetFX 3.5 version released an integration model based on the Windows Communication Foundation (WCF) and the Windows Workflow foundation (WF) technologies. This model is called as WorkflowService, and its capability is based on projecting a service connectivity and business activity. In the present .NetFx 3.5, the WorkflowService projector is based on the WCF and WF metadata described by three different resources such as a config file (system.serviceModel section group), XOML, and rules files. In addition, this metadata can be extended with other resources such as XSLT, WSDL, etc. I do recommend reading my recent article VirtualService for ESB where more information about this topic (from the service-side point of view) is available.

From the architecture point of view, services driven by metadata enable mapping and managing a business logical model to the physical one. We can see this strategy at the Microsoft Road Map presented for the first time on PDC 2003 and the upcoming PDC 2008, where more details will be released about the OSLO project. You may also visit the following link, and What is Oslo? by Douglas Purdy, Product Unit Manager for Oslo.

This strategy encapsulates metadata from the implementation layer, and hosts AppDomains into one centralized place known as the Repository. This Knowledge Base can be created and modeled at design time, and then mapped into physical targets based on the deployment schema. In other words, present technologies such as .NetFX 3.5 have been integrated with WCF and the WF models at the runtime hosting layer. The upcoming version of the .NetFX is about the integration of metadata. Having a well structuralized and integrated metadata model represented by one resource (XAML) will simplify the design and implementation of the modeling tool and the runtime bootstrap. Based on the PDC 2008 sessions (OSLO/WCF/WF topics), we can see that the WorkflowService is going to play a key role for fully manageable services.

From the enterprise point of view, the Repository size can easily grow to a large Knowledge Base, and without the right tools, it will be very difficult to manage the business models of thousands of endpoints, bindings, services, workflows, XSLT, etc. resources. Manageable services driven by metadata is a big challenge for modeling, simulation, deployment, and runtime processes, and, of course, a quality different thinking (declaratively programming) for designers and developers. This article shows some portion of this challenge such as the Repository of the Contract Model for Manageable Services. Note, that we are limited to current technologies such as .NetFX 3.5.

What does Manageable Services and Contract Model mean?

Well, let's start by briefly describing about the "legacy" Web Services, and follow up to the VirtualService which represents a fully manageable service.

Basically, a service can be considered as fully manageable in the business model if its connectivity, behavior, business workflow, and deployment are described by metadata and located in the Enterprise Service Repository.

Unmanageable Service

The following picture shows a typical connectivity between a Web Service and its consumer client:

Image 1

The Web Service is implemented with a hardcoded model for a specific hosting, transport, binding, and message exchange pattern. Besides that, the business logic and activities are also hardcoded during design time. This model has very limited public metadata, which is mostly handled by a local repository such as a config file. Every change in the web service config metadata will force to recycle a hosting process. Using a SoapExtension in the message pipeline, we can customize the encoding, message contract, etc., and publish some metadata for managing conversation on the fly. Note, that extensions represent private local features for the specific web service.

The advantage of this model is its simplicity (just giving a URL address of the port) and interoperability between the different platforms based on the WSDL spec, which is a well known contract - MXL formatted document for consuming services. The Web Service has a built-in exporter of the metadata represented by the WSDL document resource. Based on this resource, the client can create a proxy during design time, or dynamically at runtime. This is a great feature of the loosely coupled connectivity in the logical connectivity model.

At the end of this, the Web Service is considered as an unmanageable business service. Therefore, we need another communication parading for mapping a logical connectivity to the physical connectivity in an easy and manageable way. This is accomplished very easily in WCF. The following picture shows a WCF Service instead of a Web Service.

Image 2

The WCF model is a quality change in the connectivity model, where each layer can be declaratively described and stored in the metadata resource (such as a config file). There is full encapsulation of the business logic, and activity from the hosting environment based on the ServiceContract model. Hosting a service is fully transparent to the AppDomain and transport channels. Of course, WCF also supports exporting the metadata, not just for HTTP/HTTPS transport.

It looks like the WCF model is a good candidate for a manageable service, isn't it? I can say almost, we are very close. The missing part is the orchestration of the service behind. In other words, the service is still hardcoded at design time, and its manageability is based on the private features. That's bad news; the good news is, that we have a recently released .NetFX version 3.5, where are integrated two models in one paradigm, called WorkflowService.

Manageable Service

The following picture shows a manageable service based on the WorkflowService model. The WCF features are extended by the Workflow model, and integrated into the common model driven by metadata located in the config, XOML and rules resources.

Image 3

Using WorkflowServices for mapping the business logical model into a physical one gives us the capability to mediate a connectivity and business activity orchestration. As you can see, all the resources are located in the service domain. The current version only supports reading resources from a file system such as a .config file and XOML/rules files. Therefore, any change in the config file will force a recycling host process. One of the solutions about hosting services in isolated business domains can be found in my recent article: VirtualService for ESB. We can centralize metadata into the Repository storage based on this solution.

The following picture shows the next step of our service modification side:

Image 4

As you can see in the above picture, the services metadata is stored in the database, with one common place for its modeling and managing. This feature looks very nice and doable in the above picture, but today, using the current technologies, we need to build on top of the .NetFX 3.5 version, another layer (infrastructure) for hosting services in the specific AppDomains, bootstrap for metadata, service for managing hosting services, repository model, tools, etc.

The WorkflowService can be connected to the Enterprise Service Bus in the position of the Connector withthe responsibility of contract mediation, service accessibility, etc.; in other words, for service integration; see the following picture:

Image 5

OK, let's continue, we have one more bullet in the manageable service description - Untyped Message.

Untyped Message

To enable virtualization of the service and, of course, increasing its manageability, the Service Contract should be virtualized. The virtual service can handle an incoming typed message by an untyped Operation Contract in a fully transparent manner like a typed contract. Also, on the opposite side, when the service is talking to another service, the virtual service can generate an outgoing untyped message to the endpoint driven by the typed operation contract. This is a great integration feature, when the virtual service can have full control of the message flow, exchange pattern, and message mediation.

That is true. The VirtualService (manageable WorkflowService) driven by metadata can project a Virtual Contract created during design time based on the existing and/or manually imported contracts, operations, messages, and data contract. The following picture shows this composition:

Image 6

In the above example, Contract A represents a Virtual Contract as a result of the composition process of Contracts 1 - N, where the specific operations have been imported and compounded into one new virtual contract. The composition process can mediate data contracts using the XSLT technology (that's an additional resource in the metadata).

The following picture shows an example of the VirtualService with the XOML composition process, where an untyped message is branched by an operation action into separate activities for message mediation. In this example, there are five branches in the service, the first three operations are for business activities, and the others are for internal features of the service such as error handling and publishing metadata. Note, these two branches should be included in any virtual service.

Image 7

Handling am unsupported operation in the virtual service is mostly done by throwing a specific exception with returning a Fault Message via am untyped contract. The other features such as publishing metadata (WSDL or Mex endpoint) are more challenging tasks for a virtual service. Note, there is a virtual (generic) contract in the service based on an untyped message contract. The following code snippet shows an example of the virtual contract:

[ServiceContract(Namespace = "urn:rkiss.esb/2008/08")]
public interface IGenericContract
     [OperationContract(Action = "*", ReplyAction = "*")]
     Message ProcessMessage(Message message);

A virtual contract like the above one does not produce a metadata for describing composited contract operations and/or data. One solution for this challenge is to create this metadata during design time (modeling) and export it to the virtual service, like another resource. In this case, the built-in service for metadata exchange is turned off (default configuration) and replaced by an operation branch (see the above picture) for its simulation using the WS-Transfer Get operation. This activity will simply return a WSDL resource back to the caller.

As you can see, in this concept, we push the challenge of the service virtualization to design time, and the bootstrap infrastructure doesn't care by who and how this resource has been generated and stored in the repository. We can use multiple tools (such as Altova, etc.) from the market to generate this metadata, and manually composite it by a Contract Model for runtime projecting. The other way is to create a lightweight tool hosted by MMC. I will describe this MMC Tool in more details later.

The following picture shows a concept of the manageable service driven by metadata:

Image 8

The Repository represents a central component of this concept, where the metadata for our model (communication, workflow, mediations, etc.) are stored. Basically, there are the following major activities:

  • Composition of the metadata by Tool, where Tool can import and create contracts, operations, schemas, bindings, WSDL, XSLT, endpoint, etc. Note, the contract can be imported from the existing endpoint or assembly.
  • Pull-up metadata by VirtualService (bootstraping).
  • Metadata exchange from the well-known endpoint based on the resource topic. For instance, calling this endpoint: net.pipe://localhost/repository/mex?order, we can get a metadata exchange resource for the topic order in a fully transparent manner like from other endpoints. Note that the Tool can also import its own metadata that was created by modeling.

How does this model work?

Well, I can explain it in the following basic scenario, where I assume that the Tool already created a metadata for the virtual service and we have an active service in the host environment. Let's say, some client wants to perform a business workflow for ordering a book. The client doesn't need to know about the connectivity for this business, he needs to know who knows it (like an artificial intelligence). Therefore, the client calls the well known endpoint of this Knowledge Base to get it (Discovery phase). Based on the imported metadata exchange resource, the client has enough information to create a proxy channel for the business endpoint. The proxy can be cached and recycled from the Knowledge Base (Repository) based on specific needs such as lifetime expired, error, etc.

The above described concept can be abstracted in the following picture:

Image 9

As you can see, there are two models, the first one is about the Contract which can be recognized by any component such as a service or a client. This is a logical connectivity model describing "who, how, and what" on the ESB. Note that this article is focusing on this model as a first part of the Tool.

The second model is an Application Model. This model describes the behavior of the service, business workflow, activities, hosting in the AppDomains, messages and service mediations, etc. That's another challenge of the service virtualization included in its business modeling.

The models are logically connected by the ServiceEndpoint metadata, which is a unique resource on the ESB. The ServiceEndpoint is exported by a Contract Model for a specific Address, Binding, and Contract (ABC). Assigning the ServiceEndpoint to the Application Model, we can get a common model of the VirtualService.

OK, finally, we have a picture of the ESB abstraction, where the Contract Models represent a Service Bus, logically centralized in the Repository, and physically decentralized bootstrapping metadata by the VirtualService Bootstrap located in the specific hosting machines:

Image 10

The Repository storage is plugged in to the ESB via a Connector Service, with a public endpoint to get the metadata resource based on the topic. This endpoint represents all virtual services managed by the Repository. The client should call this endpoint prior to the first business call for dynamically creating a proxy. Of course, the virtual service also supports the metadata exchange feature, but in this case, the client has full responsibility to manage this physical business endpoint (for example: rerouting, mediation, etc.) like another endpoint outside of the ESB.

As I mentioned early, the Repository Service represents an Enterprise endpoint for discovering metadata. The following picture shows this scenario:

Image 11

As you can see, the metadata service consumer can also be Visual Studio 2008, a console utility such as svcutil.exe, or any client. This is a great feature for centralizing manageable services, where contracts, operations, data, etc. can be unified and reused in the Contract Model. Another feature is the Model-First concept, where the Contract Model is created prior to the business process located behind the service. The VirtualService can help with the emulation of the business process in a transparent manner during the development cycle.

The following picture shows a strategy of the Repository in distributed systems. In the Repository is a business model logically centralized for modeling purposes, and physically decentralized for runtime processing. In other words, the modeling tools via the Repository (database) can declaratively write the service, its connectivity, message mediation, business processing, etc.

Image 12

OK, that's all for now, let's start digging in the design and implementation of the Contract Model and MMC Tool.

Design and Implementation

As I mentioned above, manageable services are driven by metadata (such as connectivity, business activity, etc.) centralized in the Repository. This logically centralized model must be ready for bootstrapping by business AppDomains and physically deployed on the Enterprise network. The challenge of this solution is creating the logical model including its modeling, simulation, and managing. This process takes a lot of stages from the development environment to the production one. The VirtualServices running on the virtual server enables the modeling process for business simulation and emulation for each stage of the developing cycle. At the bottom of this vertical model is the Contract Model for logically describing connectivity by an Endpoint resource.

The following picture shows an example of the Contract Model diagram, where the Endpoint object represents an abstraction of the service interoperability:

Image 13

The Contract Model is organized into the data hierarchy based on Schemas, Messages, Operations, Contracts, and Endpoints resources. The Endpoint declared by this model can be published by storing its XML formatted text in the WSDL resource for publishing later. This WSDL resource can be queried via the Repository service by name, with a sub-query for topic, version, and contract.

Creating the Contract Model schema in the repository storage and loading the standard bindings metadata supported by WorkflowServices, we are ready for mapping a logical connectivity to the physical one. The knowledge base of this repository can be learned by importing the metadata from the cloud network or manually by using the MMC Tool. The following picture shows this scenario:

Image 14

Based on the imported metadata such as schema, and/or contract, we can increase the knowledge of the connectivity model. Compounding operations, messages, etc., into the new contracts, we can virtualize our model connectivity. Besides that, we have a capability to manage metadata on the fly based on the application behavior. Note, this article implementation has some limitations (for instance, assigning only one contract to the endpoint) in the Contract Model and MMC Tool.

Image 15

The above picture shows a position of the virtual service managed by metadata models such as Application and Contract Models. On the top of this picture is shown a direct connectivity between the physical ends. Injecting a logical point between them, we can manage business contracts in a compound manner using different message exchange patterns (such as Request/Response, OneWay, etc.). This feature is enabled by using Untyped Contracts. Of course, there is no limitation for using the Typed Contract in the Virtual Service when it is suitable. For instance, REST/WS-Eventing connectivity to the Enterprise Storage.

To run the above scenario, the Repository must hold a knowledge base of the business workflow, contracts, and the hosting environment. All this information is stored as relational resources in the models. Note, the rational model of the Enterprise Businesses can be on the top of these models.

All resources in the Repository are represented by text and/or XML text formatted elements. There is no binary serialized CLR object in the model; therefore, we have to have enough information in our models (Knowledge Base) to provide runtime support for creating CLR types, instances, AppDomains, business activities, etc. This a big challenge for mapping the metadata to runtime CLR objects. Using "horse" classes such as WsdlExporter, WsdlImport, and XmlSchemaSet from the System.ServiceModel.Description and System.Xml.Schema namespaces and the LINQ technology will simplify the implementation of the Contract Model.

Publishing ServiceEndpoint

The following picture shows the basic process of publishing metadata:

Image 16

The design concept of exporting the metadata is to create a CLR instance of the System.ServiceModel.Description.ServiceEndpoint class from the metadata represented by textual resources. As the above picture shows, the ABC service endpoint needs an address, which is very easy to create using an EndpointAddress class by passing a Uri address. The challenge starts with a binding type, where an instance of the Binding class is generated based on the XML formatted resource.

The Contract Model has pre-loaded all the standard bindings supported by NetFX 3.5 in the Repository, and the user can add additional bindings by using the embedded XmlNotepad 2007 (as this time, I would like to say thanks for this great CodePlex project, for allowing me to embed its assembly into the MMC framework).

OK, back to the above picture, the Binding description.

The implementation of mapping a CLR object vs. data is encapsulated into two helper classes located in separate files. The following picture shows their class diagram:

Image 17

The first class, ConfigHelper has been implemented for deserializing an XML formatted resource into the configuration section, such as (in this case) the BindingsSection. This deserializing process gives us the BindingSection like it is done based on the config file.

The following code snippet shows a generic method for deserializing a config section from XML text:

public static T DeserializeSection<T>(string config) where T : class
  T cfgSection = Activator.CreateInstance<T>();
  byte[] buffer = new ASCIIEncoding().GetBytes(config);
  XmlReaderSettings xmlReaderSettings = new XmlReaderSettings();
  xmlReaderSettings.ConformanceLevel = ConformanceLevel.Fragment;

  using (MemoryStream ms = new MemoryStream(buffer))
    using (XmlReader reader = XmlReader.Create(ms, xmlReaderSettings))
            Type cfgType = typeof(ConfigurationSection);
            MethodInfo mi = cfgType.GetMethod("DeserializeSection",
                BindingFlags.Instance | BindingFlags.NonPublic);
            mi.Invoke(cfgSection, new object[] { reader });
        catch (Exception ex)
            throw new Exception( ...);
  return cfgSection;

Having the BindingsSection object created by metadata is a step to walk through the standard .NetFx 3.5 bindings or custom binding. At the end, we have an instance of the binding class for our ServiceEndpoint. The following picture shows a code snippet of the helper method:

public static Binding CreateBinding(
    string bindingName, string bindingNamespace, string xmlBinding)
  xmlBinding = string.Format("<bindings>{0}</bindings>", xmlBinding);
  BindingsSection bindingSection =
  Binding binding = CreateEndpointBinding(bindingName, bindingSection);

  if (!string.IsNullOrEmpty(bindingNamespace))
      binding.Namespace = bindingNamespace;
  return binding;

Next, the third requirement of the ServiceEndpoint is the Contract Description. This is a key of the implementation, where metadata such as contract, operations, messages, headers, data types, schemas, etc., described by relational data resources are mapped to the ContractDescription type.

The process of mapping metadata into the ContractDescription type begins from the definition of the DataContract types for the MessageDescription and MessageHeaderDescription objects. We need a schema in order to create the MessageBody or HeaderBody type. Therefore, the schemas are the bottlenecks of our Contract Model hierarchy. Schemas can be imported on-line, drag and dropped from third party tools, for instance Altova, or can be created interactively using the built-in XmlNotepad2007 user control. The schemas stored in the Repository and Notepad can be pre-compiled anytime by clicking on the MMC action item.

As I mentioned earlier, the Contract Model enables a composition of the imported contracts, share their schemas, messages, headers, and operations. The imported schemas must be properly collected by the XmlSchemaSet container to avoid their duplicity, etc. Each step of the contract composition can be pre-compiled before finishing in the Repository.

For this metadata mapping, the WsdlHelper static class has been created for simplified implementation - see the above class diagram.

There are many helpful methods for messaging the metadata and encapsulating this logic from the user interface. The following picture is a code snippet for exporting the service endpoint:

private void buttonExport_Click(object sender, EventArgs e)
  // ...
 StringBuilder sbLog = new StringBuilder();
 LocalRepositoryDataContext repository =
 #region PART 1: Generate ContractDescription (CLR Types)
 var contractTypes = WsdlHelper.GenerateContractDescriptions(
   repository, selectedEndpoint.contractId, selectedOperations, sbLog);
 ContractDescription contractDescription =
   contractTypes.FirstOrDefault(t => t.Name == selectedContract.Name);
 #region PART 2: Generate ServiceEndpoints
 Collection<ServiceEndpoint> endpoints = new Collection<ServiceEndpoint>()
   new ServiceEndpoint(contractDescription, binding, endpoint)
 #region PART 3: Generate wsdl
 MetadataSet metadataDocs =
   WsdlHelper.GenerateMetadata(endpoints, policyVersion);
 StringBuilder sb = new StringBuilder();
 // show result
 // ...

The above implementations looks very straightforward using the WsdlHelper class. As an example of this helper, the following is a code snippet for creating a set of schemas for an operation:

public static XmlSchemaSet CreateOperationXmlSchemaSet(
  LocalRepositoryDataContext repository,
  Guid? inputMessageId,
  Guid? outputMessageId,
  XmlSchemaSet set)
  if (set == null)
    set = new XmlSchemaSet();
    set.ValidationEventHandler += delegate(object sender, ValidationEventArgs args)
        throw args.Exception;

  var im = repository.Messages.FirstOrDefault(m => == inputMessageId);
  if (im != null)
    var om = repository.Messages.FirstOrDefault(m => == outputMessageId);
    if (im.schemaId == null || im.Schema.schema1 == null)
        throw new Exception("Missing schema for input message ...");

    // message schema
    if (set.Schemas().Count == 0 || set.Schemas().Cast<XmlSchema><xmlschema />().
        FirstOrDefault(s => s.TargetNamespace == im.Schema.@namespace &&
        s.SourceUri == im.Schema.sourceUrl) == null)
        set.Add(null, XmlReader.Create(
          new StringReader(im.Schema.schema1.ToString()))).SourceUri=

    if (im.headers != null)
        CreateXmlSchemaSetForHeaders(repository, im.headers.ToString(), set);

    if (om != null && om.schemaId != null)
      if (set.Schemas().Count == 0 || set.Schemas().Cast<XmlSchema><xmlschema />().
          FirstOrDefault(s => s.TargetNamespace == om.Schema.@namespace &&
          s.SourceUri == om.Schema.sourceUrl) == null)
          set.Add(null, XmlReader.Create(
            new StringReader(om.Schema.schema1.ToString()
        if (om.headers != null)
            CreateXmlSchemaSetForHeaders(repository, om.headers.ToString(), set);

  // imported schemas
  ImportSchemas(repository, set);

  return set;

During the processing of the above method, the XmlSchemaSet will accumulate all the contract's operation schemas from the repository (defined by the input/output message ID). The schema query is based on the TargetNamespace and SourceUrl in order to avoid a schema duplicity. Once we have a complete set of schemas on the contract(s) level, we can compile it. This is a step that can break our mapping process. When it happens, the error message will pop up with the error description. Note, the problem must be solved in order to continue to the next step. That's why we have an action (for each level of the metadata) to pre-compile metadata to eliminate the problem of storing bad metadata resources into the repository.

The other interesting feature of the WsdlExport class is creating a memory assembly of the types described by the schemas. Note, the assembly is loaded to the default AppDoman in this version of the article. It should be loaded in a separate AppDomain for its future unloading.

That's all for the description, let's continue with describing a tool which that allow us to create the metadata for service endpoints.

esbLocalRepository Tool

The esbLocalRepository is a lightweight tool for creating and managing metadata for the Contract Model. This tool is implemented in the MMC 3.0 framework, and it uses the LINQ-SQL technology for handling resources in the SQL database.

The UI layout design is based on three panels. The left one is dedicated for metadata type resources such as schemas, messages, operations, contracts, and endpoints/WSDL. The right panel is an Action panel for the selected resource. For instance, the operation resource will have the following actions: All Operations, Add New Operation, Compile Operation, Delete, Refresh. The central panel is for interactive work with the metadata resource. The relational resources are for reading purposes only. The user controls are DataGridView oriented, which allows us to page and filter specific resources from the repository.

The following picture is a screen snippet of the "Add New Operation" into the repository:

Image 18

The user control hierarchy grows vertically based on relational resources. For instance, the schema resource is on the bottom of this hierarchy, and the opposite endpoint resource is on the top. To show more a user friendly layout of this panel, double click on the row to minimize a client panel for three rows. In opposite, by clicking on the TabPage, the panel will be maximized to show more rows.

For XML formatted resources, the tool embedded the XmlNotepad 2007 assembly, which allows overriding its public XmlNotepad.FormMain class for our purposes. The following screen snippet shows a user control for Add Binding, where a customBinding can be dragged and dropped or interactively created:

Image 19

While talking about third party user controls that helped me to build this tool, there is one more control. It is the PopupControl. Thanks for this CodeProject assembly; I used this popup control on the combobox to select a specific resource (such as binding, schema, etc.) in a user friendly manner.

The Microsoft Management Console 3.0 (MMC 3.0) is a great managed framework for the Windows environment. Compared to version 2.0 - see my old article Remoting Managment Console written in 2003 for managing remoting objects and their hosting, version 3.0 makes quality changes for easy development and extensibility. Of course, there is a challenge for the next version, for example, having a Pub/Sub notification system with an event driven architecture including the broadcasting scenario. Anyway, thanks for this great MMC 3.0 boilerplate which increased my productivity.

OK, let's make a "Hello World" example to show the capabilities of the tool. This example shows creating a compound (virtual) contract based on the imported metadata from WS-Eventing and Amazon.

Import Contract from URL

Follow these steps:

  1. Select Contracts on the left panel.
  2. Select Import Contracts Action on the right panel.
  3. Insert URL for importing contract. For example:
  4. Click on the Get button. Note, that binding for this connectivity is standard, but it can be changed based on the binding selection (not supported in this version).

You should see contracts, operations. and messages/header in the central panel:

Image 20

  1. Select Contract for import to the Repository, for instance, SubscriptionManager.
  2. Select Operations for this selected Contract. Let's say, GetStatusOp.
  3. Click on the Import button to process the importing of schemas, messages/headers, operations for this selected contract.
  4. Click on the Cancel button to cleanup the user control.
  5. Type the new URL, for instance:
  6. Select a Contract (there is only one).
  7. Select Operations, for instance: CartAdd, CartClear, CartCreate, CartGet, and CartModify
  8. Click on the Import button. When the metadata is imported, Exist Column is marked.

Now, we should have two Contracts in the Repository. Each resource can be examined individually on their control. Be sure to Refresh the control after changes. The resource validation is done by Action Compile. Any errors will popup a modal dialog with error details.

Add New Contract (Compound)

The Compound (or Virtual) Contract is managed by a tool based on the metadata stored in the Repository. The process is very simple such as populating contract description properties and selecting operations. Following up on our above example, the following screen snippet should be displayed after clicking on the Compile button:

Image 21

If the metadata has been compiled, the button Finish will enabled; otherwise, we have to solve the problem described in the error popup dialog and repeat the compiling process.

OK, so far so good. We have our new contract named VirtualContract. This contract has been composited from two different external metadata (WS-Eventing and Amazon).

Now, we can assign this contract to the endpoint and export its metadata. The following steps show this scenario.

Export Endpoint

The Export Endpoint is a final resource for this tool. It will create and store metadata in the repository for future referencing and publishing. As I mentioned earlier, the generic contract (action="*") doesn't generate metadata at runtime. It will be hard to do it dynamically for any contract.

Back to our tool, selecting the control for New Endpoint and our evolution contract included in its operation, we can see the following screen:

Image 22

The Export and (of course) Save buttons are disabled. There are missing Address and Binding values. Let's type some unique endpoint address and then click on the combobox Binding. The popup control will show up all the binding registered in the Repository. The following screen snippet shows this action:

Image 23

After that, the Export button is enabled and ready to process exporting of this endpoint. When the compiler succeeds, the metadata is shown in the Metadata Preview tab and the button Save is enabled to store it in the repository.

The following portion of the screen snippet shows this scenario. You can see more tab pages in this control; for example, Generated Contract Types will show you the source code of all the types and service contract(s). Note, the Policy tab is not implemented in this article.

Image 24

Now, we can store the endpoint metadata into the repository under a unique key. The key is the Name and Topic properties. Clicking on the button Save, the WSDL resource will be stored in the repository and will get the following feedback screen on the Metadata Test tab page..

If we have installed and opened the Repository service (hosted in the Windows NT Service under the name LocalRepositoryService), we can run the svcutil.exe test by clicking on the button Run.

Image 25

Note that other optional command arguments can be added to svcutil.exe, or you can just type /? for more help.

One more thing about the serialization. The default serializer is used as DataContractSerializer. In same cases, we need to use the XmlSerializer, which is why we have a combobox selection. The compiling process will automatically select the best option by selecting the AutoSerializer option. In order for processing the XML on the contract operation(s), the checkbox XmlFormat can be checked.

The following code snippet shows the logic of selecting the type of the serialization. Note that the XmlSerializerImporter class is implemented in the solution:

XsdDataContractImporter importer = new XsdDataContractImporter()
    Options = new ImportOptions()
     { GenerateSerializable = true,
       EnableDataBinding = false,
       GenerateInternal = false,
       ImportXmlType = false

if (serializerOption != null &&
  serializerOption.Serializer == SerializerTypes.DataContractSerializer)
    // explicitly DataContractSerializer
    importer.Options.ImportXmlType = true;
    code = importer.CodeCompileUnit;
else if (serializerOption != null &&
  serializerOption.Serializer == SerializerTypes.XmlSerializer)
    // explicitly XmlSerializerImport
    XmlSerializerImport importer2 = new XmlSerializerImport();
    code = importer2.CodeCompileUnit;
else if (importer.CanImport(set))  // auto case
    // auto serializer, from DataContract to Xml
    code = importer.CodeCompileUnit;
    XmlSerializerImport importer2 = new XmlSerializerImport();
    code = importer2.CodeCompileUnit;

Modifying an Imported Contract

An imported contract can be modified by adding more operations or changing its properties. The following screen snippet shows the Modify Contract action, where the imported contract Test2 version is modified by adding one more CartAdd operations from another imported contract:

Image 26

Compiling this new version and clicking on the Finish button, the contract Test2 version will be stored in the repository. We can export the endpoint for this contract and store it for future discovery by the client or the Virtual Service (the bootstrapping process).

The Virtual Service driven by the metadata will project this Contract in the workflow service, like it is shown in the following picture:

Image 27

This is a simplified XOML virtual service in order to describe four operation branches. The first one is a branch for processing our additional operation CartAdd, which is not a part of the physical Test2 contract. The second branch is basically a router of the originator contract to the physical endpoint, the next branch is for publishing metadata via WS-Transfer, and the last one is for handling unsupported operations.

Basically, the above example showed a service mediation prior to the real physical endpoint. We extended a real unmanageable service for additional business in the virtual service based on the metadata. Note, the client didn't see this real endpoint, and actually the client doesn't care about its physical location and existence.

One more example to show is how to add a new message into the repository.

Add New Message

As you know, the imported contract will import schemas, messages, and operations. This is an implicit process of extracting all the resources from the imported metadata into the repository. This feature is recommended, that way we can import contracts from the assembly. The contracts can be created in Visual Studio in the contract assembly, and then imported into the repository.

However, the tool has the capability to create a new message (body and headers) explicitly via the Add New Message action. The following screen snippet shows this action:

Image 28

In order to create a new message, the schema and the specific type have to be selected (see the above picture for the message body and header). There is no way in this implementation to type the message body based on the parts. In all the cases, we need to have a message contract like a request/response. This element is selected by the schema type. In the case of the header, there is some flexibility to type the header manually except for importing from the schema. Once we are ready, the message can be compiled by clicking on the Finish button that will store the metadata in the repository for future composition.

The above sections described a few features of the esbLocalRepository. The tool gave you some overview of how to create a Virtual Contract. This contract is a result of composition resources such as operations, messages, schemas, types, etc. stored in the Repository. Therefore, the Repository can also be called a Knowledge Base of the Logical Connectivity and Business processing. The Repository must be educated implicitly from the existing contracts, or explicitly in a contract-first fashion.

The following picture shows the position of the Contract Model in the Manageable Service:

Image 29

As you can see, behind the Contract Model is an Application Model driven by XOML. This is the place where a virtual contract is projected based on the business model, including a service and message mediation such as changing a message exchange pattern, etc.

That's all for the description, and let's describe some usage of the metadata from the Repository.

The primary goal of the Contract Model is creating the metadata for the virtual service in a Model-First fashion. As I mentioned earlier, the service with a generic contract (Action="*") doesn't publish the metadata; therefore, we need to provide it to the service in advance. The best usage of the Contract Model is for a Virtual Service, together with an Application Model. Unfortunately, we don't have it in the scope of this article.

However, we can prove this concept in a small test using Visual Studio 2008 as a client and tiny self hosted generic services on the server side. The following code snippet shows its contract:

[ServiceContract(Namespace = "urn:rkiss.esb/2008/04")]
public interface IGenericContract
  [OperationContract(Action = "*", ReplyAction = "*")]
  Message ProcessMessage(Message message);

[ServiceContract(Namespace = "urn:rkiss.esb/2008/04")]
public interface IGenericOneWayContract
  [OperationContract(Action = "*",  IsOneWay=true)]
  void ProcessMessage(Message message);

The service has only one business logic: dump the full message on the console.

The Contract Model represented in the Repository can be consumed via a well known service endpoint. In this article, that point has been configured in the config file as net.pipe://localhost/repository/mex? with a simple query by the name of the metadata.

Let's create a Console Application client using WCF. This client needs to consume a service, therefore the proxy must be created. VS2008 has a built-in Add Service Reference feature for creating a proxy in a transparent manner.

The following screen snippet shows the utility dialog for importing metadata from the service endpoint:

Image 30

There is nothing special on the client side, the developer knows a service endpoint where he/she can obtain the metadata, and VS2008 will embed the source code and all the types into the project for consuming the service via a proxy. Note, the proxy has enough information for the message exchange pattern between the service and the client including the actual target endpoint address.

Once we have a proxy in the source code, the business layer can begin consuming the service via this proxy in a fully transparent manner like any other object located in the AppDomain.

That's all from the client side. In order to run our client, we need to launch our target service. In this example, we have an empty service to show a received SOAP message. Note, the service is very simple and works for one way operations only, there is no response message back to the caller.

The following screen snippet shows an example of the client calls for the RenewOp operation from WS-Eventing.

Image 31

The LocalRepositoryConsole solution has been built with the following five projects based on the three layers:

Image 32

The core of the solution is the LocalRepositoryConsole project where an implementation of the MMC tool for the Contract Model is located. The solution was developed with Visual Studio 2008/SP1 - target Framework 3.5/SP1 version, and the solution uses several technologies. There is a third party folder for holding a copy of the assemblies such as XmlNotepad 2007 and PopupControl. The solution (for test purposes) uses the MS svcutil.exe program from the standard installation path. Please modify the path to match your settings, if necessary.

Since the solution requires an installation process with SQL, MMC, etc., the following steps will help you deploy the solution on your box.

  1. Download and unzip the included source into your folder.
  2. Create a local database in SQLEXPRESS:
  3. connectionString = "Data Source=localhost\sqlexpress;
               Initial Catalog=LocalRepository;Integrated Security=True"
  4. Add the external tool InstallUtil.exe into your VS2008 for the install/uninstall assembly. Here are the command and arguments:
  5. C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe
  6. Open the solution by using VS2008.
  7. In the Server Explorer, add a database connection to the LocalRepository database.
  8. Compile the solution.
  9. In LocalRepositoryConsole, open the file CreateLocalRepository.sql and click on Execute SQL. This script will create all the tables and schemas for our repository.
  10. Open the file LoadingLocalRepository.sql and execute the script. This action will process and preload the metadata into the repository, for instance, standard bindings.
  11. Select LocalRepositoryWindowsService as the StartUp Project. Now, when you click on installutil (externaol), we can install this Windows NT service. Note, the service must be started manually, therefore open Computer Management Services and find the service with the name LocalRepositoryService and click on Start.
  12. Select LocalRepositoryConsole and setup for StartUp Project. Go to External Tools, and click on installutil.
  13. OK, now is the time for MMC. Go to Vista Start and type mmc. You should see an empty Console Root on MMC 3.0.
  14. Select File/Add or Remove Snap-ins.
  15. Add the esbLocalRepository snap-in.
  16. Now, the Contract Model tool is ready to be used. Be sure to save it before you close it.
  17. You can learn about your repository and work with the schemas, messages, etc. After this evaluation period, the repository can be purged with the script, ResetLocalRepository.

Note, as I mentioned earlier, this implementation is not a production version. It is an initial version for projecting the concept of the Contract Model for a Virtual Service. There are many missing features such as deleting constrained resources, improvement of merging schemas within the same service, comparing schemas, policy, compounding endpoints, etc.

The logical model connectivity is based on the Contract Model metadata which is a service endpoint description. From the modeling point of view, this model is logically centralized in the Repository and physically decentralized on the host processes. The current hardware technology enables us to deploy our application virtually on the quest machines of the physically hosted system. For instance, we can create clusters of virtual servers for front-end, middle-tier, and back-end databases. All these virtual servers can be hosted on one physical server with strong hardware resources. As you can see, the installation of these servers can be part of the modeling, too. The business processes are virtually decentralized and logically centralized using the Contract Model. This article described the Contract Model, which plays a very small part of the modeling challenge. The next challenge is creating an Application Model that describes the hosting of the VirtualService, activation, mediation, and the business processing (using a XAML activated WorkflowService).

We can hear more details about the modeling strategy at the Microsoft PDC 2008 conference, where the project Oslo and its technologies will be introduced. See you there.

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Roman Kiss
Software Developer (Senior)
United States United States
No Biography provided

Comments and Discussions

GeneralThree words to describe your article Pin
Grav-Vt22-Oct-08 3:25
MemberGrav-Vt22-Oct-08 3:25
GeneralMessage Closed Pin
6-May-20 4:21
MemberMember 148237186-May-20 4:21
GeneralHallo Roman, nice work Pin
Maros__21-Sep-08 23:20
MemberMaros__21-Sep-08 23:20
GeneralThis is going to take a bit more time Pin
WillemM21-Sep-08 3:47
MemberWillemM21-Sep-08 3:47
GeneralMarvelous Pin
rickgaribay.net17-Sep-08 19:01
Memberrickgaribay.net17-Sep-08 19:01
GeneralRe: Marvelous Pin
Roman Kiss18-Sep-08 9:16
MemberRoman Kiss18-Sep-08 9:16
QuestionIs this an article? Pin
António Barroso15-Sep-08 11:08
MemberAntónio Barroso15-Sep-08 11:08
AnswerRe: Is this an article? Pin
Roman Kiss15-Sep-08 12:13
MemberRoman Kiss15-Sep-08 12:13
QuestionSo does this help??? Pin
code-frog12-Sep-08 19:08
professionalcode-frog12-Sep-08 19:08
AnswerRe: So does this help??? [modified] Pin
Roman Kiss13-Sep-08 9:38
MemberRoman Kiss13-Sep-08 9:38
GeneralVote is self-explanatory Pin
Georgi Atanasov12-Sep-08 12:05
MemberGeorgi Atanasov12-Sep-08 12:05
GeneralRe: Vote is self-explanatory Pin
Roman Kiss13-Sep-08 8:48
MemberRoman Kiss13-Sep-08 8:48
Hi Georgi,

Thank you and I appreciate your comment.

Microsoft MVP - Connected System Developer

GeneralAs usual Roman - a gem Pin
Pete O'Hanlon12-Sep-08 0:45
mvePete O'Hanlon12-Sep-08 0:45
GeneralRe: As usual Roman - a gem Pin
Roman Kiss13-Sep-08 8:46
MemberRoman Kiss13-Sep-08 8:46
GeneralConfiguration - This project vs .NET StockTrader Configuration Service vs .NET 4.0 vs Oslo Repository [modified] Pin
J Healy11-Sep-08 23:35
MemberJ Healy11-Sep-08 23:35
GeneralRe: Configuration - This project vs .NET StockTrader Configuration Service vs .NET 4.0 vs Oslo Repository [modified] Pin
Roman Kiss13-Sep-08 8:44
MemberRoman Kiss13-Sep-08 8:44

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.


text:
Asked  7 Months ago    Answers:  5   Viewed   29 times

Is there a better way of getting this result? This function fails if num has more digits than digits, and I feel like it should be in the library somewhere (like Integer.toString(x,"%3d") or something)

static String intToString(int num, int digits) {
    StringBuffer s = new StringBuffer(digits);
    int zeroes = digits - (int) (Math.log(num) / Math.log(10)) - 1;
    for (int i = 0; i < zeroes; i++) {
    return s.append(num).toString();

String.format (

In your case it will be:

String formatted = String.format("%03d", num);
  • 0 - to pad with zeros
  • 3 - to set width to 3
Tuesday, June 1, 2021
answered 7 Months ago

Try this:

var MyDate = new Date();
var MyDateString;

MyDate.setDate(MyDate.getDate() + 20);

MyDateString = ('0' + MyDate.getDate()).slice(-2) + '/'
             + ('0' + (MyDate.getMonth()+1)).slice(-2) + '/'
             + MyDate.getFullYear();

To explain, .slice(-2) gives us the last two characters of the string.

So no matter what, we can add "0" to the day or month, and just ask for the last two since those are always the two we want.

So if the MyDate.getMonth() returns 9, it will be:

("0" + "9") // Giving us "09"

so adding .slice(-2) on that gives us the last two characters which is:

("0" + "9").slice(-2)

But if MyDate.getMonth() returns 10, it will be:

("0" + "10") // Giving us "010"

so adding .slice(-2) gives us the last two characters, or:

("0" + "10").slice(-2)
Tuesday, June 1, 2021
answered 7 Months ago

There is an issue already filed about this at the OpenJFX docs.

While it hasn't been resolved yet, there is a possible workaround, based on:

NetBeans only adds javadoc/source jars for a jar with the exact same name and -javadoc/-source suffix

So here are the steps to solve it:

  • Install NetBeans 10 and JDK 11.0.2.

  • Clone the HelloFX sample for NetBeans and Maven, from the OpenJFX samples.

  • Update the JavaFX dependencies to 11.0.2.

  • Run it:

    mvn clean compile exec:java
  • Check that the JavaFX dependencies have been downloaded to your local m2 repository. Under <user home>/.m2/repository/org/openjfx/javafx-base/11.0.2 for instance you will find javafx-base-11.0.2.jar and javafx-base-mac-11.0.2.jar (or win, or linux based on your platform).

  • Back on NetBeans, right click in the Dependencies folder and select Download Sources (see the task progress in the bottom right taskbar), and then Download Javadoc(see the task progress).

  • Go to your m2 repository and verify that there are now -source and -javadoc jar files.

However, this won't solve the issue yet, there is an extra step:

  • In your m2 repository, manually rename the -source and -javadoc jar files using your platform classifier, to -mac-source and -mac-javadoc (or win, or linux based on your platform). Do this for the different JavaFX modules:

Back to NetBeans, check that now you have JavaDoc, or if you press Ctrl/CMD+Click you can access the source.

Note that this fix has to be done only once, the rest of your Maven projects should pick JavaDoc and Sources.

Thursday, August 5, 2021
answered 4 Months ago

if you are going to step down, then change your project's source to 1.7 as well,

right click on your Project -> Properties -> Sources window

and set 1.7 here

note: however I would suggest you to figure out why it doesn't work on 1.8

Saturday, September 4, 2021
answered 3 Months ago

Timer is used to schedule tasks.. So where do you write those tasks?? Well you have to write those tasks in a TimerTask class...

Confused ? Let me break it down,

Timer timer = new Timer();

Now you have created a object of Timer class .. Now you have to do some task right? So to do that create an object of TimerTask.

TimerTask task = new TimerTask()
        public void run()
            //The task you want to do

Now you have created a task where you should be defining the tasks you want to do inside the run method..

Why have I written a TimerTask class itself?? Thats because TimerTask is a abstract class with three methods.. So you need to define whichever method you want to use..

Now scheduling the task

Note the 'l' after 5000. It is to denote long data type because the schedule method is defined as

void schedule(TimerTask task,long milliseconds)

For further reference

Saturday, October 2, 2021
answered 2 Months ago
Only authorized users can answer the question. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :


text:
What’s it Like Being on Medication for Anxiety?

Hello friends!

So you may have read my blog post a few months ago about my experience with counselling, and in it, I had promised to write a post about using medication to manage my anxiety. It’s been a long time coming, but I’ve finally sat down ready to write this.

Let’s start at the very beginning (it’s a very good place to starrrrrt!). My anxiety had gotten to a point where it was almost unbearable. I felt sick and panicky all the time, and it would take all my energy to walk into a room, or leave the house. I wasn’t sleeping well and I was generally just a bit of a mess.

I had been reluctant to try medication as I felt like it meant that I had failed, or that I would become a totally different person if I took it. However, by this stage, there wasn’t much of an option so Steven and I went to the doctors to have a talk.

My doctor was pretty nice and explained that she had suffered with anxiety and panic attacks in the past. She taught me some breathing techniques and we went on to discuss medication. She suggested Sertraline, (which in America is called Zoloft and it features in lots of films and things), which is used for anxiety, depression and OCD. We agreed I would start on 50mg and come back within a few weeks to reassess.

The first few days were the weirdest of my life. I felt spaced-out a lot, and would get dizzy even when sat down. My legs would twitch which was odd. I just generally felt weird. I read online that this was normal and that it would ease of, so I persevered.

After a week or so, I began to feel normal again. There were a few moments where I thought that I was only the verge of a panic attack and one didn’t seem to come which was a weird and slightly frustrating feeling. Thankfully that went away.

I also went a while without crying and I was worried that I had broken my emotions. Thankfully, I did eventually cry and since then I’ve been my usual (overly emotional) self.

When I went back to my doctor, we decided to increase the dose to 100mg, and a few months later, we increased to 150mg.

A few people around me knew that I had been put on these pills and in some cases it was a little awkward. I guess when no one sees the reality of what it can be like (and I am pretty great at hiding it from most people), suddenly being put on medication seems like a dramatic step.

That said, it really has made a difference and given me the opportunity to try and deal with other issues myself.

I recently decreased the dose back to 100mg and although I’m in no rush to come off them entirely, I’m happy with my progress.

One mistake I made a few weeks ago, was forgetting to put in my repeat prescription before a bank holiday, leaving me without any meds for almost a week. At first I thought it was a great opportunity to come off them, but there is a reason they suggest coming down in small doses. I was shaky, dizzy, verging on depressive and generally not in a great place. As soon as I got my prescription, the side effects went again and I felt much better.

I have noticed that alcohol affects me a lot more now, so I have to be careful on nights out. Other than that, it’s a pretty easy part of my life.

giphy (1)

giphy (1)

I take one pill every day, with my birth control one (no crazies, no babies), and although I am still very anxious, I feel much more in control than I did in the past.

Obviously, medication isn’t for everyone. Mental health is such a personal and individual thing that no one can tell you what is “right” for you. However, if you feel that medication could help you, but you feel like it’s the “easy” way out, please go and speak to your doctor. You will still feel like, and be, you. You’ll just be able to spend more time being yourself and less time having anxiety attacks. Asking for help isn’t failing, if anything it’s refusing to fail.

Leave a Comment


text:
The United States Securities and Exchange Commission, or SEC, has officially disapproved asset manager VanEck’s spot Bitcoin exchange-traded fund months after the firm submitted its application.

According to a Friday filing, the SEC rejected a proposed rule change from the Cboe BZX Exchange to list and trade shares of VanEck’s Bitcoin (BTC) Trust. Specifically, the SEC said any rule change in favor of approving the ETF would not be “‘designed to prevent fraudulent and manipulative acts and practices” nor “protect investors and the public interest.”

“The Commission concludes that BZX has not met its burden under the Exchange Act and the Commission’s Rules of Practice to demonstrate that its proposal is consistent with the requirements of Exchange Act Section,” said the SEC, adding:

“It is essential for an exchange listing a derivative securities product to enter into a surveillance-sharing agreement with markets trading the underlying assets for the listing exchange to have the ability to obtain information necessary to detect, investigate, and deter fraud and market manipulation, as well as violations of exchange rules and applicable federal securities laws and rules.”

The regulatory body had a maximum of 240 days to approve or deny the offering following its publication in the Federal Register on March 19, giving the SEC until Nov. 14 to make a decision after extensions on April 28 and Sept. 8. Industry expert Bloomberg senior ETF analyst Eric Balchunas said the SEC was highly unlikely to approve the VanEck fund given its track record of denying offerings from investment firms with exposure to crypto, a prediction which ultimately came to pass.

“[The SEC] address the inconsistency with not deeming CME a regulated mkt of sig size in spot denial but then approving futures ETFs,” said Balchunas. “It's such a good point, but SEC doesn't care. Not having it. Basically logic and reason are trumped by technical legality.”

Though the rejection may be a blow to many investors, the SEC has already approved ETFs linked to Bitcoin futures contracts. In October, shares of digital asset manager Valkyrie's and ProShares' BTC Strategy ETF launched on U.S. stock exchanges. ProShares' ETF has since risen to the top 2% of all ETFs in terms of total trading volume — roughly $400 million worth of shares traded on Nov. 10.

Related: Report suggests BlackRock has 'no current plans' to launch crypto ETF as deadline for VanEck's offering approaches

The impact on the price of Bitcoin saw the crypto asset briefly dip to $62,300 before returning to more than $63,000. The price marks a 9.7% fall since Bitcoin reached a new all-time high of $69,000 on Nov. 10.