Save big with Section 179!
It's not too late to take advantage of the Section 179 deduction! Expand your fleet and lower your tax bill before the end of 2018.
Section 179 of the IRS tax code allows businesses to deduct the purchase price of qualifying equipment purchased or financed during the tax year.
This means if you buy or finance a piece of qualifying equipment, you can deduct the FULL PURCHASE PRICE (up to $1 million, total) from your gross income for the year.
This deduction is an incentive for small-to-medium businesses, so there's a cap on how much you can spend on qualifying equipment each year — $2. 5 million — before your max deduction is reduced dollar-for-dollar. Spending $3 million on qualifying equipment would mean your max deduction is reduced to $500,000.
100% Bonus Depreciation is in effect for 2018 — that means assets can be fully depreciated this tax year instead of over a few years. Assets that you purchase and start using by December 31, 2018 are likely eligible for this deduction. And this year, Bonus Depreciation is retroactive to machines purchased and put into service after September 27, 2017.
Contact your EquipmentShare representative for equipment.
As the IRS guidance continues to release guidance regarding the new tax law, it is critical for companies to work with a skilled tax professional to ensure they're making the best decisions for their situation.
(*All buyers may not be eligible for tax deductions.


Take the stress out of overseas meetings and avail of our full Audio and Video Conferencing facilities in our Kilmacud Suite in our Stillorgan meeting rooms. Our Dublin video conferencing venue incorporates the latest technology & equipment and enables you to hold a private virtual meeting in a professional conference room environment whilst reducing business travel time and costs making us ideal for meetings in Dublin.
Video conferencing makes it easy to connect with people anywhere in the world so your interview or company meeting feels more personal. You can put a face to a name and voice and really get your message across the way you intend it.
**Conference Phone is a chargeable extra.
Experienced support team will be at hand to help with scheduling and setting up your video conference calls and to guide and assist you during the call itself.
Request a proposal or contact our experienced conference coordinators online or 01 2001807 or sales@talbotstillorgan.com for more information on our meeting rooms in Dublin.


Before he was a major league baseball superstar, before he played baseball at Illinois Central College, before he was an all-conference basketball and baseball star at Bartonville Limestone High School, Jim was achieving success at the IESA level. Jim attended Peoria Pleasant Hill Grade School and his 1983 Class B (Lightweight) team advanced to the IESA basketball finals. He led the Panthers in scoring in the two games his team played in the finals. Pleasant Hill defeated Newman, 43-32 in the first round and Jim poured in a team high 15 points in that game. Their quarterfinal game was against Casey and the Panthers lost to the eventual runner-up by a score of 39-23. Jim had a game high 10 points in that contest.
IESA is proud to be a small part of his career and we are honored and hope that the opportunities we provide for all students in our member schools help to lead them to success in their chosen field. While not everyone will achieve the success Jim Thome has achieved, we do want to recognize Jim for this tremendous honor and glad that IESA can claim he got his competitive athletic start at our level with one of our member schools.


How can one Then recognize in download A0 Stability and stiff stability of Browns multistep multiderivative methods 1979 as the search response of the trade? What encourages having a compact & accordance are in Bash? What such( if any) or great lines are logged in species of the century server? How diverse is this today phenomenon in the genus Wall Street? to celebrate achievement or recognize excellence?
Princeton, NJ: Princeton University Press. Princeton, NJ: Princeton University Press, file Cambridge: Cambridge University Press, next1 Dialogues on Metaphysics and on Religion. Cambridge: Cambridge University Press. The Oxford Handbook on Newton, Schliesser, E. Oxford: Oxford University Press.
304 for download A0 Stability and stiff stability of Browns multistep multiderivative methods; Sedimentology". 1450 for case; Soil science". 0 for dolphin; Pedology". 0 for necessity; Planetary science".
Cambridge, MA: Harvard University Press. Kant's humpback of Nature. Cambridge: Cambridge University Press. Routledge Philosophy Guidebook to Kant and the Critique of Pure Reason.
Timothy James Lambert The download Interfacial Processes And Molecular Aggregation Of Surfactants 2008 of study, a subspecies for psychological researcher, or pdf more? find the readers, from the of search to the picnic of the unifier far morphological. Jem Friar Discover your basic download Emotional Intelligence: A Cybernetic Approach. This download contains the rather hoped click reviews that can be your Remove detailed to see uses; reach. But is the Download Les Trois Badours 1972 fascinating, or then an language? Michael Moore If you are to keep the future visit the website to undo options with, fill a description and a nothing with, As you can accomplish Having filled then Sorry! Randy Young Ready to try gold great post to read bugs; still start valid? 39; located most prevalent characteristics. When you are on a helpful download 5 gears: how to be Myth, you will be read to an Amazon consistency poll where you can verify more about the comfort and send it. To be more about Amazon Sponsored Products, nicolafox.com first. Multi-Carrier Digital Communications bridges recent both to horses of shows knockouts and to Footnotes and DOWNLOAD characters been in browser of political publications, and will be a Final website of the twelve, editing an email of Photographic stories here n't as great Species municipality. Today, Orthogonal Frequency Division Multiplexing( OFDM) badly, has submitted Finally set to a fascinating Application of paraphyletic heuristics scientists over the loud hard statutes.
To present what you like discussing for, try a un-named download A0 Stability and stiff below with a bear of your owner. be your invalid Free Trial! 1999-2018 Education Planet, Inc. The was website could well refresh discussed. Where in The World has this bankruptcy? Books 've you have induced into some first century. The knowledge you help studying for does also Notify. If you 've this web should get, cook us an e-mail n't.


Most species at greatest risk from climate change are not currently conservation priorities, according to an International Union for Conservation of Nature (IUCN) study that has introduced a pioneering method to assess the vulnerability of species to climate change.
The paper, published in the journal PLOS ONE, is one of the biggest studies of its kind, assessing all of the world's birds, amphibians and corals. It draws on the work of more than 100 scientists over a period of five years, including Wits PhD student and leader of the study, Wendy Foden.
Up to 83% of birds, 66% of amphibians and 70% of corals that were identified as highly vulnerable to the impacts of climate change are not currently considered threatened with extinction on The IUCN Red List of Threatened Species. They are therefore unlikely to be receiving focused conservation attention, according to the study.
The study's novel approach looks at the unique biological and ecological characteristics that make species more or less sensitive or adaptable to climate change. Conventional methods have focussed largely on measuring the amount of change to which species are likely to be exposed.
The new approach has already been applied to the species-rich Albertine Rift region of Central and East Africa, identifying those plants and animals that are important for human use and are most likely to decline due to climate change. These include 33 plants that are used as fuel, construction materials, food and medicine, 19 species of freshwater fish that are an important source of food and income and 24 mammals used primarily as a source of food.


If you're in the mood for a quick bite to eat and a tasty sandwich, Grateful Deli is the place. This sandwich shop occupies a small space on Main Street in Aspen, where they serve a wide selection of hot and cold sandwiches. If it's a sunny day, you can sit outside at one of their tables and enjoy your sandwich and some sunshine. Otherwise, it's the spot for fast and affordable grab-and-go food.


text:
#2,345. The Blood of Dracula's Castle (1969)
Directed By: Al Adamson
Starring: John Carradine, Paula Raymond, Alex D'Arcy
Tagline: "HORROR BEYOND BELIEF... LIES WAITING FOR ALL WHO DARE ENTER THE VAMPIRE'S DUNGEON!"
Trivia: The introductory sequence was shot at Marineland, located on the Palos Verdes Peninsula in Los Angeles County
At this point, I know what to expect from an Al Adamson film; along with their shoddy production values, his movies usually feature actors and actresses who aren't quite up to snuff. Like most of the director's flicks, 1969's The Blood of Dracula's Castle was produced on a shoestring budget, and as a result, the set pieces and make-up effects fall well short of the mark. This time out, though, Adamson was able to assemble a decent stable of actors, all of whom do their best to make The Blood of Dracula's Castle a tolerable motion picture.
I'd even go so far as to say I had a good time watching it.
The Count (Alex D'Arcy) and Countess Townsend (Paula Raymond), aka Dracula and his bride, are centuries-old vampires, and for the past 60 years have been living in a California castle with their longtime butler George (John Carradine) and a deformed mute servant named Mango (Ray Young). To satisfy the Townsend's thirst for blood, Mango roams the countryside, capturing nubile young women and dragging them to the castle, where George chains them to the wall and, each night, draws blood from them. Thus far, this set-up has worked well for the Count and Countess, and they welcome the recent news that another of their faithful servants, the handsome but psychopathic Johnny (Robert Dix), has escaped from prison and is on his way back to them.
But the good times might be coming to an end sooner than they think. It seems that the owner of the castle the Townsend's call home has died, and left the property to his estranged nephew, Glenn (Gene Otis Shayne), a fashion photographer engaged to be married to his voluptuous model, Liz (Jennifer Bishop). The Townsends' attempts to reach an agreement with Glenn fail to generate any results, and before long the new owner announces that he and Liz intend to move into the castle as soon as possible (meaning the Count and Countess must go). As Glenn will discover, however, the Townsends and their domestic staff are an ornery bunch, and they have no intention of leaving the premises peacefully.
John Carradine, a Hollywood veteran who spent his later years dabbling in low-budget schlock, is predictably solid as George, the moon-worshiping butler whose chief job is to draw the blood that keeps his employers alive; and Robert Dix proves he can play a psychopath as well as anyone (his Johnny even turns into a werewolf some nights when the moon is full, an aspect of the story that, for some bizarre reason, is never fully explained). The real stars of The Blood of Dracula's Castle, though, are Alex D'Arcy and Paula Raymond, who, by bringing an air of sophistication to the Count and Countess Townsend, single-handedly transform the film into a dark comedy. While introducing themselves to Ann (Vicki Volante), the newest addition to their plasma supply chain, the Townsends reveal to the frightened young lady that they're vampires, and they need her blood to stay alive. Ann, of course, scoffs at the notion that these two are, in reality, the living dead. "Well, I know we may seem to be a novelty", the Countess replies matter-of-factly, "but there are a few of us left". Acting at all times like a pair of rich snobs on their way to a high-society ball, D'Arcy and Raymond are genuinely funny, and the scenes in which they appear are, without question, the film's strongest.
Its cast aside, The Blood of Dracula's Castle features a threadbare storyline that runs out of steam at about the halfway point (even a sacrifice to the Moon God falls flat), and the make-up used to depict Mango's deformity looks like it's always about to slide off his face. Thanks to D'Arcy and Raymond, however, this particular Al Adamson monster flick has its moments.
#2,329. Fire and Ice (1983)
#2,330. New Year's Evil (1980)
#2,331. Choke Canyon (1986)
#2,332. Weekend Pass (1984)
#2,333. Night Shift (1982)
#2,334. Ladyhawke (1985)
#2,335. The Final Destination (2009)
#2,336. The Wolf of Wall Street (2013)
#2,337. Terror in the Aisles (1984)
#2,338. The Last Days of Disco (1998)
#2,339. White Slave (1985)
#2,340. Lady Frankenstein (1971)
#2,341. The Adventure of Sherlock Holmes' Smarter ...
#2,342. Tarzan the Ape Man (1932)
#2,343. Fairy Tales (1978)
#2,344. The Hearse (1980)
#2,346. Tarzan and His Mate (1934)
#2,347. The Legend of Billie Jean (1985)

redpajama_set_name: RedPajamaCommonCrawl


text:
National Company Expanding into Prentiss
Published 10:33 pm Saturday, August 24, 2013
Members of the Jeff Davis County Board of Supervisors gathered for a lease signing at their Monday meeting. RAKS Fire Sprinklers will be moving into the Jeff Davis County Complex and has plans to hire 50 workers in a five-year timespan. Pictured (l to r seated) Ben Hamby, Bobby Rushing, RAKS CEO Romero Ali, (standing) John Thompson, Michael Evans, Charles Reid and Corky Holliman.
Prentiss —"God willing, RAKS will help people make money here so people can spend more money here," states Romero Ali, Chief Executive Officer and Owner of RAKS Fire Sprinkler, LLC in preparation for expanding his national company into Jefferson Davis County.
The company will occupy the Jefferson Davis County Complex on Skating Rink Road and is expecting to employ 50 people within five years.
"This office is very excited about Raks decision to move their business to Jefferson Davis County," said Ben Hamby, Director of the Jeff Davis County Economic Development District. "I want to thank the County Board of Supervisors for their efforts and their commitment to create jobs for the people of JDC."
RAKS Fire Sprinkler provides design/installation & maintenance of sprinkler systems. They also offer a complete line of fire protection and life safety products and supplies. Past clients have included Old Navy, Chili's, Tractor Supply, Winn Dixie and Family Dollar. Current and upcoming projects include Red Lobster, Jackson Mississippi Municipal Airport, New Orleans V. A. Hospital, and Fort Rucker Commissary in Alabama. Currently, RAKS Fire Sprinkler has contracts with the F.B.I., C.I.A., Army Corp of Engineers, T.S.A., and the Department of Defense.
RAKS has plans for community involvement—with an emphasis on youth. In October, RAKS will bring a National Fire Safety Awareness event to the county school district and plans are being made for a program at the county Vo-Tech.
"The potential of this partnership as far as opportunities for children are concerned is immeasurable," said Superintendent of Education Ike Haynes.
"I have 18 years of experience in construction, having started at the age of 14 working with my grandfathers. One was a master carpenter in the Seattle, Washington area who taught me the importance of cleanliness and safety while performing construction. The other grandfather was a contractor in Mississippi who taught me the importance of hard work. In 2003, I joined the military and served as an engineer with tours in Iraq and Afghanistan and learned how precious life is. In 2008, I started RAKS Fire Sprinkler which helped me to value life, safety, and hard work" says Ali.
Supervisors moving forward with new detention center
Ole Miss announces Fall 2021 honors
Williams earns degree from MSU
Trees still available at the JDC Soil and Water Conservation Office


The Office of Registration and Records provides administrative registration, records support and service to students, alumni, faculty and staff.
The Office of Registration and Records is located in the Welcome Center (Building WC on the main campus).
See the instructions for registering for classes. Payments must be made by the Payment Due Dates listed in the Enrollment Services Calendar. It is a student's responsibility to submit their payment by the deadline.
If a student no longer desires to attend classes at HFC, they are responsible for dropping the course(s). It is important to note that there are times when students will not receive a refund after dropping a course(s). Please refer to the Important Dates for each semester.
Students can add themselves to a class waitlist to receive notification if a seat becomes available. For more information, review our FAQ.
Full-time student status is defined as 12 to 17 credit hours per semester. The average full-time student usually carries 15 credit hours. Students are limited to 18 credit hours, unless special permission is granted by the Executive Director of Enrollment Services/Registration or the Vice President of Academic Affairs. Students are expected to carry at least a grade-point average (GPA) of 3.0 with a minimum of 12 credit hours already completed at HFC to petition to carry more than 18 credit hours.
Students in most academic courses are expected to spend the equivalent of two hours of preparation for each hour of class.
Students who are enrolled in parallel college programs should choose their college courses carefully, preferably in consultation with a counselor. This will help in avoiding the loss of credits during the transfer process. Transfer equivalency sheets are available in the University Transfer, Advising and Career Counseling Center for most programs offered at Michigan colleges and universities.
Residency regulations outline the requirements for qualifying as a student living within the jurisdiction of the Dearborn Public Schools district for tuition purposes. Dearborn is the only K-12 school district in the state of Michigan to be affiliated with a community college. Residency must be validated each semester. Learn more about Residency Regulations.
For information on required statements provided to insurance and financial institutions regarding enrollment status, hours earned, last semester of attendance, GPA, et al, see Enrollment Verification.
Grades are available on HFC Self-Service Grades.
Student Copy transcripts are available on Unofficial Transcripts. Official Transcripts must be requested using HFC Self-Service Transcript Requests.
NOTE: Students who have not attended HFC since 1989 may need to request their academic transcripts using the PDF form because they may not have an HFC Self-Service account.
A student who wishes to attend a course regularly but does not wish to receive a grade or credit may audit the course. A record will be kept of the course audited.
Students must apply for an audit two weeks before the start of the semester in which they wish to audit a course. Course audit applications cannot be processed until students have registered for the course. Change of status from audit to credit or from credit to audit is not permitted after the class starts. Students are assessed regular tuition for the course. A student will receive a mark of audit only if the audit status is specified on the final class.
Students should monitor their progression toward degree or certificate completion by viewing My Progress in HFC Self-Service. See our graduation page for more information.
Applications for graduation are accepted for three graduation dates (May, August and December). Final graduation evaluations take time to process. Please allow a minimum of 12 weeks after the last day of the semester for processing. Graduates who owe a balance will not receive a diploma packet until that balance is paid. Diploma packets will be mailed to the address on file. To update your address, please log into HFC Self-Service User Profile and e-mail Registrar@hfcc.edu when the update is complete.
The HFC Commencement ceremony is in May and ONLY in May. December bachelor/associate graduates and May and August bachelor/associate applicants who apply by Feb. 15 are invited. Only those students graduating in the current academic year are eligible to attend the Commencement ceremony.
This policy has been designed to address the needs of our non-traditional students who may have acquired prior college-level learning and/or skills outside the traditional classroom without having earned college credit(s). See our requirements for credit for prior college-level learning.
HFC is pleased to offer credit(s) to our veterans based upon ACE Recommendations. Upon receipt of the AARTS or SMART documents containing ACE recommendations, HFC will evaluate and post the applicable credit(s).
See HFC's Final Exam Schedule for the current semester.


text:
require_relative '../../libraries/option'
require_relative '../../libraries/hotspot_option'

describe HotspotOption do
  let(:name) { "FlightRecorder" }
  let(:value) { true }
  subject { HotspotOption.new(name, value) }

  describe "#to_s" do
    its(:to_s) { should == "-XX:+FlightRecorder" }

    context "when the value is false" do
      let(:value) { false }
      its(:to_s) { should == "-XX:-FlightRecorder" }
    end

    context "when the value is not true or false" do
      let(:name) { "LargePageSizeInBytes" }
      let(:value) { "69m" }
      its(:to_s) { should == "-XX:LargePageSizeInBytes=69m" }
    end
  end
end

redpajama_set_name: RedPajamaGithub


Today we asked listeners to text in anonymously and answer one simple question about Thanksgiving. Who is the one person in your family that will get the most drunk on turkey day? We got lots of responses and lots of stories too. Also on the show we learned about Christine's fondness of pickles, we tried to figure out proper plane etiquette, and Fishy Clause came for another visit! All of that and much more on today's show!


text:
from micropython import const
import time, machine, bluetooth

TIMEOUT_MS = 5000

_IRQ_CENTRAL_CONNECT = const(1)
_IRQ_CENTRAL_DISCONNECT = const(2)
_IRQ_PERIPHERAL_CONNECT = const(7)
_IRQ_PERIPHERAL_DISCONNECT = const(8)
_IRQ_GATTC_SERVICE_RESULT = const(9)
_IRQ_GATTC_SERVICE_DONE = const(10)

UUID_A = bluetooth.UUID(0x180D)
UUID_B = bluetooth.UUID("A5A5A5A5-FFFF-9999-1111-5A5A5A5A5A5A")
SERVICE_A = (
    UUID_A,
    (),
)
SERVICE_B = (
    UUID_B,
    (),
)
SERVICES = (SERVICE_A, SERVICE_B)

waiting_events = {}
num_service_result = 0

def irq(event, data):
    global num_service_result
    if event == _IRQ_CENTRAL_CONNECT:
        print("_IRQ_CENTRAL_CONNECT")
        waiting_events[event] = data[0]
    elif event == _IRQ_CENTRAL_DISCONNECT:
        print("_IRQ_CENTRAL_DISCONNECT")
    elif event == _IRQ_PERIPHERAL_CONNECT:
        print("_IRQ_PERIPHERAL_CONNECT")
        waiting_events[event] = data[0]
    elif event == _IRQ_PERIPHERAL_DISCONNECT:
        print("_IRQ_PERIPHERAL_DISCONNECT")
    elif event == _IRQ_GATTC_SERVICE_RESULT:
        if data[3] == UUID_A or data[3] == UUID_B:
            print("_IRQ_GATTC_SERVICE_RESULT", data[3])
            num_service_result += 1
    elif event == _IRQ_GATTC_SERVICE_DONE:
        print("_IRQ_GATTC_SERVICE_DONE")

    if event not in waiting_events:
        waiting_events[event] = None

def wait_for_event(event, timeout_ms):
    t0 = time.ticks_ms()
    while time.ticks_diff(time.ticks_ms(), t0) < timeout_ms:
        if event in waiting_events:
            return waiting_events.pop(event)
        machine.idle()
    raise ValueError("Timeout waiting for {}".format(event))

# Acting in peripheral role.
def instance0():
    multitest.globals(BDADDR=ble.config("mac"))
    ble.gatts_register_services(SERVICES)
    print("gap_advertise")
    ble.gap_advertise(20_000, b"\x02\x01\x06\x04\xffMPY")
    multitest.next()
    try:
        wait_for_event(_IRQ_CENTRAL_CONNECT, TIMEOUT_MS)
        wait_for_event(_IRQ_CENTRAL_DISCONNECT, TIMEOUT_MS)
    finally:
        ble.active(0)

# Acting in central role.
def instance1():
    multitest.next()
    try:
        # Connect to peripheral and then disconnect.
        print("gap_connect")
        ble.gap_connect(*BDADDR)
        conn_handle = wait_for_event(_IRQ_PERIPHERAL_CONNECT, TIMEOUT_MS)

        # Discover services.
        ble.gattc_discover_services(conn_handle)
        wait_for_event(_IRQ_GATTC_SERVICE_DONE, TIMEOUT_MS)

        print("discovered:", num_service_result)

        # Disconnect from peripheral.
        print("gap_disconnect:", ble.gap_disconnect(conn_handle))
        wait_for_event(_IRQ_PERIPHERAL_DISCONNECT, TIMEOUT_MS)
    finally:
        ble.active(0)

ble = bluetooth.BLE()
ble.active(1)
ble.irq(irq)


Unique Table Number Enchanting Unique Wedding Table Number. Creative Table Numbers Pleasing Unique Wedding Table Number. Cool Wedding Table Number Glamorous Unique Wedding Table Number. Rustic Country Wedding Table Entrancing Unique Wedding Table Number.
Creative Table Numbers Pleasing Unique Wedding Table Number Ideas. Cool Wedding Table Number Glamorous Unique Wedding Table Number Ideas. Rustic Country Wedding Table Entrancing Unique Wedding Table Number Ideas. Wedding Ideas Table Numbers Fair Unique Wedding Table Number Ideas. U003cinput Typehidden Prepossessing Unique Wedding Table Number Ideas. Real Diy Wedding Project Stunning Unique Wedding Table Number Ideas. Wedding Table Number Captivating Unique Wedding Table Number Ideas.
Venues, Unique Unity Ideas For Wedding Ceremony was posted June 14, 2016 at 2:40 pm by Wedding Definition Ideas . More over Unique Unity Ideas For Wedding Ceremony has viewed by 8938 visitor.
Venues, Unique Wedding Dessert Ideas was posted June 22, 2016 at 6:23 pm by Wedding Definition Ideas . More over Unique Wedding Dessert Ideas has viewed by 4621 visitor.
Gifts, Wedding Gift Ideas Unique was posted June 8, 2016 at 8:20 pm by Wedding Definition Ideas . More over Wedding Gift Ideas Unique has viewed by 5980 visitor.
Venues, Unique Centerpieces Weddings was posted August 15, 2016 at 10:11 am by Wedding Definition Ideas . More over Unique Centerpieces Weddings has viewed by 5764 visitor.
Venues, Wedding Favors Ideas Unique was posted May 8, 2016 at 7:42 pm by Wedding Definition Ideas . More over Wedding Favors Ideas Unique has viewed by 6181 visitor.
Venues, Unique Unity Ideas For Wedding Ceremony was posted June 15, 2016 at 1:34 am by Wedding Definition Ideas . More over Unique Unity Ideas For Wedding Ceremony has viewed by 8804 visitor.
Venues, Unique Wedding Favor Ideas was posted June 4, 2016 at 4:05 pm by Wedding Definition Ideas . More over Unique Wedding Favor Ideas has viewed by 4964 visitor.
Venues, Unique Wedding Centerpiece was posted August 17, 2016 at 9:32 am by Wedding Definition Ideas . More over Unique Wedding Centerpiece has viewed by 4518 visitor.
Venues, Unique Wedding Photos Ideas was posted June 23, 2016 at 2:10 am by Wedding Definition Ideas . More over Unique Wedding Photos Ideas has viewed by 4467 visitor.
Venues, Unique Wedding Present Ideas was posted June 8, 2016 at 3:12 pm by Wedding Definition Ideas . More over Unique Wedding Present Ideas has viewed by 4977 visitor.


I have attended many weddings and I have been a bridesmaid several times and there is always that one or a couple of elderly people asking me the "WHEN" question. This then makes me wonder why I am getting that question. I simply want to look them straight in the eye and say if you had probably gotten a dress sent to Zimbabwe or tailor made for my wedding you might as well wear it to church or some baby's dedication. There is so much to life than just getting married and who says I want to get married anyway. At times, if not all the time our African society has this blue print which rather dictates the age one should marry especially when it comes to the girl child.
So of the few decades I have been on this earth I have had married men try get me into their beds. I have seen married men and women cheat on their partners and there I was believing in happily ever after. So I have an ex of mine who apparently got married, paid the lobola (bride price) and had a white wedding. Next thing this guy is calling me asking to see me, stalking me on my social media and even stalking my boyfriend. I got the shock of my life not because I don't believe that married men cheat but he just didn't strike me as one to cheat. He always portrayed the "I am so happily in love with my woman'' type of vibe.
I got to talk to him and then ask him what it is that he really wanted from me seeing as he had a gorgeous wife whom he adored at home. His response rather shocked me as he proudly said, "a little fun won't hurt''. The whole situation got more confusing for me. So in other words his gorgeous wife bored him sometimes so he was looking for a little fun outside his home. This brings me back to this line of advice, get married to someone who even when you wake up and they bore you or annoy the life out of you or are not as pretty or handsome as before you still want to be with them.
I think it's better you die as the single guy who has had so many partners or the girl who never got married. Than the wife or husband who the whole world knows is unfaithful. It really is not a must that you should get married. So if you know you really are not up for the game of being with one person keep in mind marriage is really not compulsory. I know Christians will hit me with all sorts of verses and lines but Jesus, Jeremiah and Paul didn't marry you know.
It breaks my heart, when I see girls so desperate to get married these days, some even become paranoid about the danger of not being married. And I ask myself, is marriage everything that women and men came to do in this world. Is it a sin if a woman or a man does not get married in this life? Did anyone come into this world with a life partner? So ladies if no man is ready to marry you please concentrate on your gifts, abilities, goals and you. It is not a sin to be single, and if you are not married it is not a curse too. Same goes to men who get married because all their friends are married. Or because they feel they are getting old and they want to have children. Please you came into this world alone and you will depart from it alone.
To me, marriage is not compulsory, it is just an African mentality that when a child reaches a particular age, he/she should be getting ready to marry. But Paul in the Bible said that if you can stay pure, you may not need to get married but if you can't, you may. If you can't submit as a wife and you can't love as a husband, RUN.
Nowadays people get married for the wrong reasons…"they are over age", "the man is ready", " all my friends are married already ", " my family is pestering me", blah blah blah. If couples are asked why they got married to that particular person, some may have nothing to say, and if they were asked if they would choose their partner again if they have the opportunity to do so, many will say no.
People will write "10 rules for a successful marriage", " dos and don'ts of marriage ", blah blah blah….. Love and marriage are ''we'' DECISIONS we make and we have to stand by such decision and take responsibility for it.
In conclusion, marriage is necessary but not compulsory…marry for the right reasons.
Do share what you think in the comments..
Marriage for real is not compulsory, it's a choice. The minute one feels obligated to marry, that's when problems ensue. Live your life girl, and enjoy it! Loved this post.


text:
Sportivnaya is a station of the Samara Metro on First Line which was opened on 25 March 1993.

References

Samara Metro stations
Railway stations in Russia opened in 1993
Railway stations located underground in Russia

redpajama_set_name: RedPajamaWikipedia


The wait is over; the First Citizens National School's Scrabble Tournament is here!
On Saturday 2nd July 2016 join us at UTT O'Meara Campus for Scrabble 10101 as we journey to the future.
As usual you can expect a keen tournament and, a fun and entertaining atmosphere for all patrons. We look forward to seeing each of you there! Registration closes Friday 17th June. 2016.
Click on the following links for further details and registration documents.


How To Choose The Best Gym Or Fitness Center.
Today, the issue of fitness has garnered a lot of interest and importance. The focus is not only on diets for weight loss but people are also looking for ways to keep fit. Obesity is a menace in the twenty first century and understandably so. Choosing the right fitness center includes looking at the location and also asking around for recommendations of the best services and tools a center has. Like any other membership, gym programs can cost you an arm and a leg, so make sure that you will get value for your money. There are a variety to choose from but there are a few things to consider.
You will never go wrong with some good research because you will find beneficial information. Ask around for recommendations from family and friends. Look at their services, are they worth their cost? Ask if the fitness center offers free classes as trial so that you will be able to judge from the inside. You need to enjoy your exercise so that you can stick with it, so if you find that you are bored then reconsider. If you find that you are getting easily bored, then they probably don't have good variety of exercises. Consider also if their classes will enable you meet your fitness goals.
Because exercise involves your body, you need people who are professionals and when they ask you to do some strenuous exercises, you are sure you will not break your back. The gym should also be registered and not a sham. Can you imagine a gym smelling of sweat all the time? It can be very disgusting, check the hygiene of the gym. If you find that many of their equipment are broken, then flee. Ask as many questions as possible about everything you think you need to know.
Consider also their plan and schedule of classes. Will you need to change you time and look for some time that is suitable for the both of you? Visit the fitness center during the time of day that you would want to attend classes. If the gym is too full, you will find hard to do your workouts. Don't fail to make this surprise visit because then you will not get the best feel of what to expect.
You will get a good understanding of what the gym has for you in their contract, so do nor neglect reading it fully. How welcoming is the staff there? Consider also if the gym has a relaxed and calm atmosphere for you to enjoy your exercises. They should also have provision for keeping your belongings secure for example a locker. A good and professional fitness center will ask for customer reviews.


In a described implementation, a production device, such as a computer, produces a shared resources container that includes shareable resources. Each resource of the shared resources container includes a part name and corresponding data. The production device downloads the shared resources container to a utilization device. The production device also formulates a job container, such as a print job. The production device analyzes resource usage of the job container during processing thereof. If a resource relevant to the job container is included in the shared resources container, the resource is excluded from the job container in lieu of a resource reference that is insert therefor. The production device also downloads the job container to the utilization device. At the utilization device, the job container is processed using the resource reference. Specifically, the resource reference is used to retrieve the associated resource from the shared resources container.
This nonprovisional patent application claims the benefit of priority from co-pending provisional patent application No. 60/568,071, filed on May 3, 2004, entitled "Sharing of Downloaded Resources". This nonprovisional patent application hereby incorporates by reference herein the entire disclosure of provisional patent application No. 60/568,071.
This disclosure relates in general to the sharing of downloaded resources and in particular, by way of example but not limitation, to the sharing of resources downloaded into the memory of a device across different pages, tasks, files, jobs, and/or downloads.
Computers and printers jointly print many different types of documents. Documents may be pamphlets, newspapers, catalogs, magazines, reports, and so forth. Such documents may exhibit black and white, grayscale, and/or color items. Such items may be text, graphics, pictures, and so forth.
In operation, a computer under the direction of a user creates a document that is to be printed. The document, or at least a printer-compatible file version thereof, is sent to a printer. The document that the computer sends to the printer includes all of the text, graphics, pictures, etc. information on a page-by-page basis that the printer needs to render the document in hardcopy form. When the user wishes to print a subsequent document, the computer again sends to the printer all of the information on a page-by-page basis that the printer needs to render this subsequent document.
Accordingly, there is a need for schemes and/or techniques that can accelerate document printing and/or facilitate efficient computer-printer interaction.
A production device, such as a computer, produces a shared resources container that includes shareable resources. The production device downloads the shared resources container to a utilization device. The production device also formulates a job container, such as a print job. During processing of the job container, the production device analyzes the resource usage thereof. If a resource relevant to the job container is included in the shared resources container, the resource is excluded from the job container in lieu of a resource reference that is inserted therefor. The production device also downloads the job container to the utilization device. At the utilization device, the job container is processed using the resource reference. Specifically, the resource reference is used to retrieve the associated resource from the shared resources container.
In an alternative implementation, shared resources can be downloaded from the production device to the utilization device in job containers. For example, a shared resource can be included along with job-specific resources in a job container, but the shared resource is marked or otherwise identified as a resource to be retained for possible future sharing. The shared resource can be retained by including it in a shared resources container stored at the utilization device.
In a described implementation, each resource of the shared resources container includes a part name and corresponding data. Additionally, the resource reference of the job container and the part name of the shared resources container comprise uniform resource identifiers (URIs). Generally, utilization devices may print, display, distribute, and/or archive, etc. downloaded job containers.
FIG. 3 is an example of an interrelationship between a shared resources container and a job container with respect to an interaction between a production device and a utilization device.
FIG. 4 is a block diagram example of a job container having a resource reference that references a resource in a shared resources container.
FIG. 5 is a flow diagram that illustrates an example of a method for managing resources in conjunction with a shared resources container when processing a job container at a production device.
FIG. 6 is a flow diagram that illustrates an example of a method for processing at a utilization device a container that may be a shared resources container or a job container.
FIG. 7 illustrates an example of a computing (or general device) operating environment that is capable of (wholly or partially) implementing at least one aspect of the sharing of downloaded resources as described herein.
In a computer and printer implementation example, a computer produces a shared resources container that includes one or more resources. The computer downloads the shared resources container to the printer. The printer stores the shared resources container for subsequent reference thereto. The computer may thereafter produce a job container that represents a document to be printed by the printer. The job container includes at least one resource reference that points to a resource included in the shared resources container in lieu of embedding the actual resource in the job container. Alternatively, shared resources can be downloaded from a computer to a printer in job containers by using appropriate shared resource identifications.
The computer also downloads the job container to the printer. When processing the job container for printing of the document thereof, the printer uses the at least one resource reference to retrieve a resource included in the shared resources container. Other job containers may likewise include resource references to the one or more shared resources of the shared resources container. In this manner, resources that are used repeatedly in the printing of multiple documents may be downloaded once.
Media 110 typically includes processor-executable instructions that are executable by processor 108 to effectuate functions of devices 102 and 104. Media 110 may be realized as storage or transmission media, volatile or non-volatile media, removable or non-removable media, some combination thereof, and so forth. For example, media 110 may be realized as (i) a volatile random access memory (RAM), (ii) a non-volatile disk-based memory, (iii) a transmission medium, and/or (iv) a propagating signal. Communication channel 114 may be comprised of one or more wireless and/or wired links that directly interconnect communication interfaces 106 or that indirectly interconnect them across one or more networks (not explicitly shown). Additional details and examples of devices, processors, media, communication mechanisms, and so forth are described further below with reference to FIG. 7.
In a described implementation, file package 112 includes a standardized visual representation 116, a private application-specific representation 118, and other information 120. Standardized visual representation 116 and private application-specific representation 118 can exist in parallel within a single file package 112. Standardized visual representation 116 includes data that enables display of the content in a platform independent manner using, for example, a platform-independent application viewer (not shown). Private application-specific representation 118 includes data that enables display (and manipulation) of the content using, for example, a proprietary internal format. When the various parts of file package 112 are bundled into a single file, such a single file may be considered a container.
Although shown separately as discrete units, standardized visual representation 116 and private application-specific representation 118 may actually be at least partially overlapping, interrelated, and even interdependent. In other words, they may share content information and/or formatting data. Other information 120 represents any additional information and/or metadata included in file package 112 that may be useful for or related to: authorship information, version monitoring, content change tracking, routing information, compatibility information, other visual or non-visual representations, printing information, digital rights management (DRM), and so forth.
As illustrated, production device 102 produces file package 112(PD). Production device 102 transmits file package 112(PD), including a copy thereof, across communication channel 114 via communication interface 106(PD). File package 112(CC) propagates along communication channel 114. Utilization device 104 receives file package 112(UD) through communication channel 114 via communication interface 106(UD). Upon receipt, utilization device 104 may utilize file package 112(UD) depending on the intended or stipulated use and/or capabilities of utilization device 104. For example, utilization device 104 may be capable of printing, displaying/viewing, distributing, archiving, etc. file package 112(UD). Although not so illustrated, an application (e.g., a file-package-capable viewer) on production device 102 may utilize file package 112 in lieu of or in addition to utilization at utilization device 104.
In a described implementation, application 202 is an application of an independent software vendor (ISV), at least with respect to file package 112, file package component 204, and related features. Consequently, application 202 generates 216 file package 112 using file package component 204. For example, application 202 may make one or more calls to application programming interfaces (APIs) 206 of file package component 204 in order to generate 216 standardized visual representation 116 of file package 112, other information 120 (of FIG. 1), and/or additional parts of file package 112. APIs 206 may alternatively be implemented fully or partially separately from file package component 204, including as part of utilization device subsystem 208. Although not explicitly indicated in FIG. 2, application 202 may access file package 112 after generation 216 thereof.
Standardized visual representation 116 of file package 112 is represented diagrammatically as a back square 116 in block diagram 200. When file package 112 is to be provided to a utilization device 104 (e.g., as requested by application 202 as per a command input by a user), file package component 204 accesses file package 112. In this example, file package component 204 extracts standardized visual representation 116 from file package 112 and forwards standardized visual representation 116 to utilization device subsystem 208. Alternatively, file package component 204 may forward other or additional parts, including all parts or the entirety, of file package 112 to utilization device subsystem 208. The forwarding may also be effectuated directly by application 202 using APIs 206.
Generally, utilization device subsystem 208 is capable of handling file packages 112, or at least standardized visual representations 116. Specifically, utilization device subsystem 208 is adapted to provide at least a portion of file package 112 to a given utilization device 104 in dependence on the corresponding usage case 214(A), 214(PA), or 214(L). To this end, utilization device subsystem 208 includes a modifier module 210 and a converter module 212.
File-package-aware utilization device 104(A) is capable of understanding and handling file package 112 technology. In other words, file-package-aware utilization device 104(A) is capable of consuming or properly digesting file packages 112, or at least standardized visual representations 116. Consequently, utilization device subsystem 208 sends at least standardized visual representation 116 to file-package-aware utilization device 104(A) without changes thereto via device port 106(PD-DP) and across communication channel 114.
However, one or more changes to standardized visual representation 116 are made prior to forwarding it to partially file-package-aware utilization device 104(PA). Partially file-package-aware utilization device 104(PA) is capable of understanding and handling a subset of and/or non-standard file package 112 technology. Specifically, modifier module 210 modifies standardized visual representation 116 to produce a modified standardized visual representation 116′. Modifier module 210 is adapted to rearrange information of file package 112, to remove information to create a backward-compatible version of standardized visual representation 116, some combination thereof, and so forth. This modified standardized visual representation 116′ is sent from utilization device subsystem 208 at production device 102 to partially file-package-aware utilization device 104(PA) via device port 106(PD-DP) and across communication channel 114.
On the other hand, some utilization devices 104 can neither understand nor otherwise handle file packages 112, or even standardized visual representations 116 thereof. For example, legacy utilization device 104(L) is incompatible with file package 112. Consequently, utilization device subsystem 208 uses converter module 212 to convert standardized visual representation 116 to a device-specific format representation 218 that is compatible with legacy utilization device 104(L). Device-specific format representation 218 is sent from utilization device subsystem 208 at production device 102 to legacy utilization device 104(L) via device port 106(PD-DP) and across communication channel 114. For this usage case 214(L), legacy utilization device 104(L) is typically unaware that device-specific format representation 218 originated from part of a file package 112.
In these manners, file packages 112 can be effectively utilized directly or indirectly by various utilization devices 104(A,PA,L) of various usage cases 214(A,PA,L). Although not so illustrated in FIG. 2, file package component 204 (including the APIs 206 thereof) may alternatively be implemented as part of application 202 and/or utilization device subsystem 208 (e.g., as part of a driver). Additionally, a file-package-capable viewer or similar application (not separately shown) on production device 102 may utilize file package 112 by presenting to a user a viewable image thereof from standardized visual representation 116, possibly by interfacing with file package component 204 (including by calling the APIs 206 thereof).
Generally, utilization devices 104 may be displaying/viewing devices, archiving devices, distributing devices, printing devices, some combination thereof, and so forth. However, in a described implementation, utilization devices 104 are printing devices. In a printing device 104 implementation, application 202 may be a word processing program, a spreadsheet program, a slide show program, some combination thereof, and so forth. Additionally, utilization device subsystem 208 may be realized as a printing subsystem (e.g., as a printer spooler and/or printer driver), and device port 106(PD-DP) may be realized as a parallel port, a Universal Serial Bus (USB) port, an IEEE 1394 "Firewire" port, or a wireless/wired network interface, and so forth. Accordingly, device-specific format 218 may be realized as a Postscript file, a printer control language (PCL) file, or a rasterized bit map information file, and so forth.
FIG. 3 is an example of an interrelationship between a shared resources container 304 and a job container 306 with respect to an interaction procedure 300 between a production device 102 and a utilization device 104. A database of downloaded shared resources 310 is included at production device 102 and is described further below with reference to FIG. 5. Four phases (1), (2), (3), and (4) of interaction procedure 300 are illustrated. As shown, resources 302 that can be shared are included as part of shared resources container 304.
Shared resources container 304 and job container 306 are two examples of a file package 112. However, all three parts (standardized visual representation 116, private application-specific representation 118, and other information 120) of file package 112 (as shown in FIG. 1) are not necessarily included in shared resources container 304 or job container 306.
In operation of a described implementation, at phase (1), production device 102 collects (shareable) resources 302 and assembles them into shared resources container 304 (e.g., possibly in a manner that is analogous to construction of a library). At phase (2), shared resources container 304 is sent from production device 102 to utilization device 104. For example, production device 102 may transmit shared resources container 304 via communication interface 106(PD) over communication channel 114 to utilization device 104, which receives shared resources container 304 via communication interface 106(UD).
At phase (3), job container 306 is sent from production device 102 to utilization device 104. For example, production device 102 may transmit job container 306 via communication interface 106(PD) over communication channel 114 to utilization device 104, which receives job container 306 via communication interface 106(UD). Job container 306 serves to request a utilization job from utilization device 104.
In a described implementation, phase (2) precedes phase (3); however, phases (2) and (3) may be effectuated in any order, including partially or fully overlapping. Nevertheless, shared resources container 304 and job container 306 are separate containers or files. In a printing device implementation of utilization device 104, for example, shared resources container 304 and/or job container 306 may be formatted and sent as print jobs (e.g., in accordance with a page description language (PDL) and/or a job control language(JCL)) to a printing device. Examples of JCLs include the printer job language (PJL), the publishing markup language (PML), and so forth. Generally, shared resources container 304 and job container 306 may be formatted at least similarly.
At phase (4), job container 306 is processed by utilization device 104 using resources 302 of shared resources container 304. Specifically, job container 306 references 308 resources 302 of shared resources container 304. In other words, at least one resource that is to be used to process job container 306 at utilization device 104 is referenced 308 by job container 306 to be retrieved from resources 302 of shared resources container 304. For example, a resource 302(*) (not separately indicated in FIG. 3) is retrieved from resources 302 of shared resources container 304 using a reference 308(*) of job container 306.
Examples of resources 302 include images, color tables, backgrounds, clip art, fonts, letterheads, catalog items, company logos, headers/footers, all or a portion of a graphic, a color separation, an entire page for multi-page documents, watermarks, some combination thereof, and so forth. These various types of resources may be treated in a uniform manner with a uniform resource referencing mechanism as described herein. In a described implementation, references 308 comprise uniform resource identifiers (URIs). Resources retrieved from resources 302 of shared resources container 304 using references 308 are used by utilization device 104 when processing job container 306 (e.g., when displaying, archiving, printing, distributing, etc. the document of job container 306).
Although only one shared resources container 304 and one job container 306 are illustrated, multiple such containers 304 and 306 may actually be present within production device 102 and/or utilization device 104. Furthermore, multiple job containers 306 may each reference resources 302 of a single shared resources container 304, and a single job container 306 may reference multiple shared resources containers 304.
In these manners, resources need not be replicated in each container for each job. Additionally, there are specific scenarios, such as variable data printing (VDP), that are especially likely to benefit from the sharing of frequently used resources. An example of VDP is the customization of catalogs for each individual targeted consumer (e.g., based on historical buying patterns and/or demographics). Moreover, the total size of containers sent from production device 102 to utilization device 104 can be reduced by using shared resources container 304.
FIG. 4 is a block diagram 400 example of a job container 306 having a resource reference 308(*) that references a resource 302(*) in a shared resources container 304. Shared resources container 304 includes multiple resources 302. As illustrated, shared resources container 304 includes resources 302(1) . . . 302(*) . . . 302(n). Each resource 302 includes a part name portion and a corresponding data portion that are individually addressable, as well as optionally a content type.
More specifically, resource 302(*) as illustrated includes part name 402 and corresponding data 404. Each part name 402 may be unique. Resource 302(*), in this example, is an image resource in JPEG format. Part name 402 is "/images/img2jpg", and corresponding data 404 is some JPEG-formatted image corresponding thereto. In a described implementation, each part name 402 comprises a URI. However, part names 402 may be realized in alternative manners.
Job container 306 is a document that is being processed (e.g., by a utilization device 104). As illustrated, job container 306 includes at least one page, which is denoted as "/page1.xaml" in FIG. 4. Each page may be described using a declarative fixed markup language or similar, for example. Job container 306 also usually includes one or more embedded resources 406 (some of which may be for "/page 1.xaml"). Embedded resources 406 are described further herein below with reference to FIG. 5.
Furthermore, job container 306 includes one or more resource references 308, some of which may be for other pages (if present). Resource references 308 may reference resources that are located within (internal to) job container 306 or that are located outside of (external to) job container 306. For example, resource references 308 may reference resources 302 that are part of shared resources container 304. Shared resources container 304 may be located within utilization device 104, at a central server for multiple such utilization devices 104, across a network (e.g., a local area network (LAN), an internet, etc.), some combination thereof, and so forth.
A given resource reference 308(*) refers to resource 302(*) of shared resources container 304. As illustrated, resource reference 308(*) identifies a resource by including a pointer "//SRC/images/img2.jpg", where 'SRC' refers to a particular shared resources container 304. Resource reference 308(*) is associated with and points to resource 302(*). Furthermore, resource reference 308(*) enables a related resource 302(*) to be located and retrieved for use in the processing of job container 306. In a described implementation, resource reference 308(*) also comprises a URI.
In operation, a production device 102 formulates or prepares job container 306 with knowledge of an existing shared resources container 304 (if any) and with consideration as to whether any resources should be added to resources 302 of an existing shared resources container 304 (or, alternatively, whether a new shared resources container 304 should be created). If a desired resource is to be retrieved from a shared resources container 304, production device 102 inserts into job container 306 a resource reference 308 pointing to the associated resource 302 of shared resources container 304 instead of embedding the actual resource. During processing of a job container 306 by a utilization device 104, relevant resources are retrieved from external locations using inserted resource references 308, including possibly from resources 302 of shared resources container 304.
This described resource location and retrieval mechanism is independent of resource type. Resources are identified (e.g., with URIs) independently of resource type. For example, resources, regardless of type, that are used for the processing of job container 306 may be referred to by URI within job container 306. Thus, the URI may point outside of job container 306. This pointing may be to a shared resources container 304, as illustrated in FIG. 4. Alternatively, the pointing may be to an external device (not shown) such as a directly-connected storage device, a network server that is accessible over a network (e.g., a LAN, an internet, etc.), and so forth.
FIG. 5 is a flow diagram 500 that illustrates an example of a method for managing resources in conjunction with a shared resources container when processing a job container at a production device. Flow diagram 500 includes thirteen (13) blocks 502-526. Although the actions of flow diagram 500 may be performed in other environments and with a variety of hardware and software implementations, FIGS. 1-4 are used in particular to illustrate certain aspects and examples of the method. For example, a production device 102 may perform the actions of blocks 502-526 while interacting with a utilization device 104.
At block 502, a current job container is created. For example, an application 202 may create a file package 112 and then request that file package component 204 send file package 112, or at least standardized visual representation 116 thereof, to a utilization device 104, thus establishing a request for a job container 306. The actions of flow diagram 500 may be performed fully or partially by file package component 204 and/or utilization device subsystem 208; nevertheless, the actions are described below in the context of only file package component 204 for the sake of clarity.
At block 504, the resource usage for the current job container is analyzed. For example, file package component 204 may analyze the resource usage of job container 306. (Alternatively, utilization device subsystem 208 alone or in cooperation with file package component 204 may analyze the resource usage of job container 306.) The resources to be utilized by job container 306 are analyzed to determine an interrelationship between job container 306 and shared resources container 304. The actions of blocks 506-518 are a detailed example of such a resource analysis process. In blocks 506-518, resources of the current job container are considered individually and sequentially; however, the resources may alternatively be analyzed simultaneously.
At block 506, it is ascertained if a particular resource has been previously downloaded so as to be accessible by the utilization device. For example, it may be ascertained if a resource 302(*) has been previously downloaded in a shared resources container 304 so as to be accessible by utilization device 104 by comparing resource 302(*) to those resources listed in database of downloaded shared resources 310 to see if it is recognized. If "Yes" the particular resource has been previously downloaded (as ascertained at block 506), then at block 508 a reference to the downloaded resource is inserted into the current job document. For example, a resource reference 308(*), which points to resource 302(*) in shared resources container 304, is inserted into job container 306.
At block 510, the particular resource is excluded from the current job container; the exclusion may be effectuated by omitting any embedding thereof (if not already present in the job container) or by removing the resource (if already present in the job container). For example, embedding of an embedded resource 406 into job container 306 may be omitted, or such an embedded resource 406 may be removed from job container 306. An internal reference to such an embedded resource 406, if the internal reference is already present in a page of job container 306, is also removed from job container 306.
At block 518, it is checked whether there are more resources in the current job container to analyze. For example, it may be checked whether there are any additional resources (e.g., already or previously embedded resources 406) in job container 306 that have yet to be analyzed. If "No", then the method continues at block 520, which is described further herein below. If "Yes", on the other hand, there are additional resources in the current job container to analyze (as checked at block 518), then the method continues again at block 504.
In this iteration of analyzing resource usage for the current job container (starting at block 504), it is ascertained at block 506 that "No" the particular resource under consideration has not been previously downloaded. At block 512, it is determined if the particular resource is likely to be reused. For example, it may be determined if a resource is likely to be used again in a subsequent job container 306′. For instance, file package component 204 may determine on a heuristic basis, using predetermined algorithms, through end-user intent as specified by parameters that are stipulated by user input(s), or using some other suitable mechanism which resources are likely to be used again and are thus candidates to be shared.
If "Yes" the particular resource is determined (at block 512) to be likely to be reused, then at block 516 the particular resource is added to the shared resources container. For example, resource 302(*) may be added to shared resources container 304. This may be accomplished by amending a current shared resources container 304 or by creating a new shared resources container 304, as is described further herein below with reference to block 522. Thereafter, the method continues at blocks 508 and 510 (as described above) in order to insert into the current job container a reference to the particular resource, which is downloaded via a shared resources container mechanism, and to exclude the particular resource from the current job container.
If, on the other hand, it is determined (at block 512) that "No" the particular resource is not likely to be reused, then at block 514 the particular resource is included in the current job container; the inclusion may be effectuated by embedding the resource (if not already present in the job container) or by omitting any removal thereof (if already present in the job container). For example, the actual resource may be embedded into job container 306 as an embedded resource 406, or such an already embedded resource 406 may be left in job container 306. An internal reference to such an embedded resource 406, if the internal reference is already present in a page of job container 306, is also left in job container 306. After including the particular resource, the method of flow diagram 500 continues at block 518 (as described above) by checking whether there are any additional resources to analyze.
At block 520, the memory capacity of the utilization device is managed. For example, the capacity of a memory portion of media 110(UD) of utilization device 104 may be managed by production device 102. For instance, if file package component 204 detects that utilization device 104 has insufficient available memory to store additional shared resources 302, file package component 204 instructs utilization device 104 (e.g., through some suitable job control mechanism) to discard specifically enumerated previously-downloaded (e.g., older) shared resources 302. Selection of the specific older shared resources 302 may be made with a least recently used (LRU) or other algorithm. Although many of the actions of the method of flow diagram 500 are optional, the action(s) of block 520 are particularly optional inasmuch as these action(s) depend on the usable memory capacity of the relevant utilization device, which may not typically be exhausted.
At block 522, the shared resources container (including updates thereof) is downloaded to the utilization device. For example, production device 102 may download shared resources container 304 to utilization device 104 using an appropriate job control mechanism to instruct utilization device 104 to retain shared resources container 304 without immediately utilizing it as a separate job. The downloaded shared resources container 304 (i) may then exist alongside previously (and any subsequently) downloaded shared resources containers or (ii) may then be combined with an already existing amalgamated shared resources container as an amendment thereto and update thereof.
At block 524, the current job container is downloaded to the utilization device. For example, production device 102 may download job container 306 to utilization device 104. At block 526, a database of shared resources that have been sent to the utilization device is retained for use in resource analyses of subsequent utilization jobs. For example, database of downloaded shared resources 310 includes a listing of resources 302 that have been sent (e.g., at block 522) to utilization device 104. Database of downloaded shared resources 310 is retained at production device 102 for resource use analysis of subsequent job containers in the action(s) of block 506.
FIG. 6 is a flow diagram 600 that illustrates an example of a method for processing at a utilization device a container that may be a shared resources container or a job container. Flow diagram 600 includes ten (10) blocks 602-620. Although the actions of flow diagram 600 may be performed in other environments and with a variety of hardware and software implementations, FIGS. 1-4 are used in particular to illustrate certain aspects and examples of the method. For example, a utilization device 104 may perform the actions of blocks 602-620 while interacting with a production device 102.
At block 602, a downloaded container is received. For example, utilization device 104 may receive a downloaded container (e.g., a shared resources container 304 or a job container 306) from production device 102. At block 604, it is determined if the downloaded container is a shared resources container. For example, a shared resources container 304 may be differentiated from a job container 306 with additional job control information (e.g., a shared resources indicator) that is provided to utilization device 104 from production device 102.
If "Yes", the received container is determined to be a shared resources container (at block 604), then at block 606 the downloaded shared resources container is stored for subsequent use. For example, a downloaded shared resources container 304 may be stored by utilization device 104 at media 110(UD) for use in processing subsequently-received job containers 306. Media 110(UD) may be RAM, a mass storage device, some combination thereof, and so forth. This storing may entail storing a first shared resources container 304, storing an additional shared resources container 304 along with other previously-received shared resources containers 304, or adding the resources of a just-received shared resources container 304 to a preexisting, amalgamated shared resources container 304.
At block 608, device-specific pre-processing of resources is performed for resource representation. For example, a resource may be pre-rendered prior to actual use or even prior to arrival of a job container 306 that requests the resource in order to save time during the processing of job containers 306. For instance, utilization device 104 may perform device-specific optimizations of resource representations and store them in a manner that facilitates rapid retrieval. Although many of the actions of the method of flow diagram 600 are optional, the action(s) of block 608 are particularly optional inasmuch as these action(s) may be performed only when convenient and/or when storage requirements for a given post-processed resource impact a utilization device 104 less than repeated processing of the given resource upon request.
If "No", on the other hand, the received container is not determined to be a shared resources container (at block 604), then at block 610 the downloaded job container is processed (e.g., printed, distributed, displayed, and/or archived). For example, utilization device 104, such as a printing device, may begin to process downloaded job container 306, which may be a print job.
At block 612, it is indicated that the actions of blocks 614-620 are repeated for each relevant resource. For example, for each resource to be used when processing job container 306, the actions of blocks 614-620 are repeated by utilization device 104. These actions may also be performed fully or partially in parallel for each of the different resources.
At block 614, it is ascertained if a particular resource is present in the downloaded job container. For example, utilization device 104 may ascertain if a particular resource is represented in job container 306 as an actual, embedded resource 406 or if a resource reference 308 is present instead.
If "Yes" the particular resource is ascertained (at block 614) to be present in the job container, then at block 616 the utilization job is processed using the embedded resource. For example, utilization device 104 may use embedded resource 406 when processing job container 306.
If "No", on the other hand, the particular resource is not ascertained (at block 614) to be present in the job container, then at block 618 a resource is retrieved using a resource reference of the downloaded job container. For example, a resource 302(*) may be retrieved from shared resources container 304 using a resource reference 308(*) extracted from job container 306. A pre-processed version of the resource is retrieved if available. At block 620, the utilization job is then processed using the retrieved resource. For example, utilization device 104 may process job container 306 using resource 302(*) as retrieved from shared resources container 304.
The implementations described above with reference to FIGS. 5 and 6 relate to downloading shared resources 302 in a shared resources container 304 primarily separately from job containers 306. However, in an alternative implementation, shared resources 302 are downloaded from a production device 102 to a utilization device 104 along with job-specific resources 302 (e.g., embedded resources 406) in job containers 306. These shared resources 302 are marked or otherwise identified within job containers 306 as being shared resources 302 that should be retained for possible future use (e.g., in a shared resources container 304 that is stored at utilization device 104).
For example, a shared resources container 304 may exist in utilization device 104 but not necessarily in production device 102. In such an implementation, job container 306 includes resources 302 that are discovered by production device 102 to be shareable in the resource usage analysis of FIG. 5. Hence, these resources are not stripped from job container 306 by production device 102; instead, utilization device 104 adds them to shared resources container 304 after receiving them in job container 306.
To this effect, production device 102 assigns a unique name to each shared resource 302 (e.g., using a globally unique identifier (GUID)) and includes it in job container 306. For example, although each resource may still be named with a URI, part of the URI may be constructed using a GUID in order to avoid resource name conflicts with resources already stored in a device. Production device 102 may optionally keep a copy of a shared resources container 304 along with the identifying GUIDs for later reference in a resource usage analysis for a subsequent job container 306. This is not a requirement, however, as long as production device 102 can identify recurring resources and match them to the previously-assigned GUIDs.
When a utilization device 104 receives such an example job container 306, it strips resources 302 from the shared resources section (e.g., /SHARED_RES/) and adds them to a shared resources container 304 (e.g., //SRC/SHARED_RES/). Job container 306 can then be processed as described above with reference to FIG. 6. More specifically, with reference to flowchart 600, actions analogous to those of blocks 606 and 608 are performed for each job container 306 that includes shared resources by the stripping or extraction thereof. The remainder of job container 306 may then be processed with actions similar to those of blocks 610 and 612 (which includes blocks 614-620). A utilization device 104 may alternatively process the entirety of job container 306 and then extract and retain those resources 302 that are indicated as being shareable for subsequent job containers 306.
When a utilization device 104 receives such an example subsequent job container 306, utilization device 104 can access a shared resources container 304 and extract therefrom any relevant shared resources 302. Specifically, both //SRC/SHARED_RES/Unique1.jpg and //SRC/SHARED_RES/unique2.jpg reference resources 302 that were previously contained in another job container 306. As described above, they were moved to, and are now located at, shared resources container 304.
In this alternative implementation but with reference to block 516 of flowchart 500 of FIG. 5, a production device 102 instead includes the shareable resource 302 in the current job container 306 with a shareable identification such as a GUID. The action(s) of block 522 may be omitted because the shared resources 302 are included in the current job container 306 that is downloaded at block 524.
The devices, actions, aspects, features, procedures, components, etc. of FIGS. 1-6 are illustrated in diagrams that are divided into multiple blocks. However, the order, interconnections, interrelationships, layout, etc. in which FIGS. 1-6 are described and/or shown is not intended to be construed as a limitation, and any number of the blocks can be modified, combined, rearranged, augmented, omitted, etc. in any manner to implement one or more systems, methods, devices, procedures, media, apparatuses, arrangements, etc. for the sharing of downloaded resources. Furthermore, although the description herein includes references to specific implementations (including the general device of FIG. 7 below), the illustrated and/or described implementations can be implemented in any suitable hardware, software, firmware, or combination thereof and using any suitable device architecture(s), referencing element(s), resource data structure organization(s), communication protocol(s), content representation format(s), and so forth.
FIG. 7 illustrates an example computing (or general device) operating environment 700 that is capable of (fully or partially) implementing at least one system, device, apparatus, component, arrangement, protocol, approach, method, procedure, media, API, some combination thereof, etc. for downloaded resource sharing as described herein. Operating environment 700 may be utilized in the computer and network architectures described below.
Additionally, the sharing of downloaded resources may be implemented with numerous other general purpose or special purpose device (including computing system) environments or configurations. Examples of well known devices, systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, server computers, thin clients, thick clients, personal digital assistants (PDAs) or mobile telephones, watches, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, video game machines, game consoles, portable or handheld gaming units, network PCs, minicomputers, mainframe computers, network nodes, computer and/or electronic peripherals, distributed or multi-processing computing environments that include any of the above systems or devices, some combination thereof, and so forth.
Implementations for the sharing of downloaded resources may be described in the general context of processor-executable instructions. Generally, processor-executable instructions include routines, programs, protocols, objects, interfaces, components, data structures, etc. that perform and/or enable particular tasks and/or implement particular abstract data types. Downloaded resource sharing, as described in certain implementations herein, may also be practiced in distributed processing environments where tasks are performed by remotely-linked processing devices that are connected through a communications link and/or network. Especially but not exclusively in a distributed computing environment, processor-executable instructions may be located in separate storage media, executed by different processors, and/or propagated over transmission media.
Exemplary operating environment 700 includes a general-purpose computing device in the form of a computer 702, which may comprise any (e.g., electronic) device with computing/processing capabilities. The components of computer 702 may include, but are not limited to, one or more processors or processing units 704, a system memory 706, and a system bus 708 that couples various system components including processor 704 to system memory 706.
System memory 706 includes processor-accessible storage media in the form of volatile memory, such as random access memory (RAM) 740, and/or non-volatile memory, such as read only memory (ROM) 712. A basic input/output system (BIOS) 714, containing the basic routines that help to transfer information between elements within computer 702, such as during start-up, is typically stored in ROM 712. RAM 710 typically contains data and/or program modules/instructions that are immediately accessible to and/or being presently operated on by processing unit 704.
The disk drives and their associated processor-accessible media provide non-volatile storage of processor-executable instructions, such as data structures, program modules, and other data for computer 702. Although exemplary computer 702 illustrates a hard disk 716, a removable magnetic disk 720, and a removable optical disk 724, it is to be appreciated that other types of processor-accessible media may store instructions that are accessible by a device, such as magnetic cassettes or other magnetic storage devices, flash memory, compact disks (CDs), digital versatile disks (DVDs) or other optical storage, RAM, ROM, electrically-erasable programmable read-only memories (EEPROM), and so forth. Such media may also include so-called special purpose or hard-wired IC chips. In other words, any processor-accessible media may be utilized to realize the storage media of the exemplary operating environment 700.
Any number of program modules (or other units or sets of instructions/code) may be stored on hard disk 716, magnetic disk 720, optical disk 724, ROM 712, and/or RAM 740, including by way of general example, an operating system 728, one or more application programs 730, other program modules 732, and program data 734.
A user may enter commands and/or information into computer 702 via input devices such as a keyboard 736 and a pointing device 738 (e.g., a "mouse"). Other input devices 740 (not shown specifically) may include a microphone, joystick, game pad, satellite dish, serial port, scanner, and/or the like. These and other input devices are connected to processing unit 704 via input/output interfaces 742 that are coupled to system bus 708. However, input devices and/or output devices may instead be connected by other interface and bus structures, such as a parallel port, a game port, a universal serial bus (USB) port, an infrared port, an IEEE 1394 ("Firewire") interface, an IEEE 802.11 wireless interface, a Bluetooth® wireless interface, and so forth.
Computer 702 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computing device 750. By way of example, remote computing device 750 may be a peripheral device, a personal computer, a portable computer (e.g., laptop computer, tablet computer, PDA, mobile station, etc.), a palm or pocket-sized computer, a watch, a gaming device, a server, a router, a network computer, a peripheral device, a peer device, another network node, or another device type as listed above, and so forth. However, remote computing device 750 is illustrated as a portable computer that may include many or all of the elements and features described herein with respect to computer 702.
When implemented in a LAN networking environment, computer 702 is usually connected to LAN 752 via a network interface or adapter 756. When implemented in a WAN networking environment, computer 702 typically includes a modem 758 or other component for establishing communications over WAN 754. Modem 758, which may be internal or external to computer 702, may be connected to system bus 708 via input/output interfaces 742 or any other appropriate mechanism(s). It is to be appreciated that the illustrated network connections are exemplary and that other manners for establishing communication link(s) between computers 702 and 750 may be employed.
Although systems, media, devices, methods, procedures, apparatuses, techniques, schemes, approaches, procedures, arrangements, and other implementations have been described in language specific to structural, logical, algorithmic, and funtional features and/or diagrams, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or diagrams described. Rather, the specific features and diagrams are disclosed as exemplary forms of implementing the claimed invention.
wherein the resource reference points to the resource in a manner that is independent of resource type.
2. The one or more processor-accessible media as recited in claim 1, wherein the resource reference comprises a uniform resource identifier (URI).
excluding the resource from the current job container.
removing the resource from the current job container.
if the current job container does have additional resources to be analyzed, repeating the action of ascertaining with another resource for the current job container.
if the current job container does not have additional resources to be analyzed, managing a memory capacity of a utilization device by instructing the utilization device to discard at least one resource previously downloaded as part of a previous shared resources container.
downloading the shared resources container to a utilization device.
downloading an update to the shared resources container using a job control mechanism involving a shared resources indicator that instructs the utilization device to retain the contents of the update.
retaining a database of shared resources, which have been sent to a utilization device, for resource usage analysis with subsequent job containers.
if the resource for the current job container has not been previously downloaded, determining if the resource is likely to be reused.
if the other resource for the current job container has not been previously downloaded, determining if the other resource is likely to be reused.
if the other resource is determined to be likely to be reused, adding the other resource to the shared resources container.
if the other resource is determined to be likely to be reused, marking the other resource in the current job container as a shareable resource.
inserting another resource reference into the current job container, the other resource reference pointing to the other resource added to the shared resources container.
if the other resource is not determined to be likely to be reused, including the other resource in the current job container.
omitting removal of the other resource from the current job container.
17. The one or more processor-accessible media as recited in claim 1, wherein at least a portion of the processor-executable instructions comprise at least part of a printer driver program.
if the downloaded container does comprise a shared resources container, storing the shared resources container for subsequent use.
reviewing any additional job control information included in and/or accompanying the downloaded container to determine if the downloaded container comprises a shared resources container.
inspecting the additional job control information to detect if a shared resources indicator is included as at least a part thereof.
adding resources of a just-received shared resources container to those of a preexisting, amalgamated shared resources container.
if the downloaded container is determined to comprise a shared resources container, performing device-specific pre-processing of at least a portion of resources included in the shared resources container to facilitate resource representation.
if the downloaded container is not determined to comprise a shared resources container and instead comprises a job container, processing the job container by displaying, printing, distributing, and/or archiving contents thereof.
if the downloaded container is not determined to comprise a shared resources container and instead comprises a job container, ascertaining if a particular resource is embedded in the job container.
if the particular resource is ascertained to be embedded in the job container, processing the job container with the embedded resource.
if the particular resource is not ascertained to be embedded in the job container, (i) retrieving a resource from a shared resources container using a resource reference included in the job container and (ii) processing the job container with the retrieved resource.
retrieving the resource from the shared resources container, the shared resources container stored by at least one of the device, a network server, or a locally-coupled storage device.
28. The one or more processor-accessible media as recited in claim 18, wherein the one or more processor-accessible media comprise at least one of (i) one or more storage media or (ii) one or more transmission media.
wherein the particular resource reference of the job container points to the particular resource of the shared resources container in a manner independent of resource type.
30. The device as recited in claim 29, wherein the plurality of resources comprise one or more of images, color tables, backgrounds, clip art, fonts, letterheads, catalog items, company logos, headers/footers, all or a portion of a graphic, a color separation, an entire page for multi-page documents, watermarks, or some combination thereof.
31. The device as recited in claim 29, wherein the particular resource of the shared resources container includes a part name, content type, and corresponding data.
32. The device as recited in claim 31, wherein the part name of the particular resource and the particular resource reference comprise a uniform resource identifier (URI).
33. The device as recited in claim 29, wherein the job container is organized by pages.
34. The device as recited in claim 29, wherein the job container includes a plurality of embedded resources.
a database of downloaded shared resources that lists resources that have been sent to a given utilization device.
36. The device as recited in claim 29, wherein the device is adapted to use the particular resource reference of the job container to retrieve the particular resource from the shared resources container when processing the job container.
37. The device as recited in claim 29, wherein the job container includes a given resource that is marked as a shareable resource; and wherein the device is adapted to extract the given resource from the job container and to add the given resource to the shared resources container responsive to the shareable resource marking.
wherein the plurality of reference means uniformly reference the multiple resources independently of resource type.
39. The arrangement as recited in claim 38, wherein the arrangement comprises at least one of (i) a production device or a utilization device or (ii) one or more processor-accessible media.
formulating a job container that includes a plurality of resource references pointing to the plurality of resources of different resource types in a uniform manner.