<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title> &#187; News and Events</title>
	<atom:link href="https://www.ical.com/blog/?cat=14&#038;feed=rss2" rel="self" type="application/rss+xml" />
	<link>https://www.ical.com/blog</link>
	<description></description>
	<lastBuildDate>Fri, 12 Feb 2016 00:33:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.2.38</generator>
	<item>
		<title>ICAL Talks Shop on XojoTalk</title>
		<link>https://www.ical.com/blog/?p=302</link>
		<comments>https://www.ical.com/blog/?p=302#comments</comments>
		<pubDate>Wed, 03 Feb 2016 22:23:03 +0000</pubDate>
		<dc:creator><![CDATA[ical]]></dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[News and Events]]></category>

		<guid isPermaLink="false">http://www.ical.com/blog/?p=302</guid>
		<description><![CDATA[As system developers, we always love talking shop. In the technology industry there are seemingly endless ways to get things done. Since we work in a general IT shop, we work on many platforms including Windows, OS X, portables, Linux and embedded systems. The constant challenge is to learn (and remember) all the individual tools <a href='https://www.ical.com/blog/?p=302' class='excerpt-more'>[...]</a>]]></description>
				<content:encoded><![CDATA[<p>As system developers, we always love talking shop. In the technology industry there are seemingly endless ways to get things done. Since we work in a general IT shop, we work on many platforms including Windows, OS X, portables, Linux and embedded systems.</p>
<p>The constant challenge is to learn (and remember) all the individual tools you need to develop solutions for each platform. At ICAL we use a product called XOJO to do a lot of our cross platform development. It is one of the few truly cross-platform tool sets.<span id="more-302"></span></p>
<p>Toward the end of January we were invited to discuss XOJO with the people who produce it. ICAL, Tom and Arthur (not to be confused with Tom and Ray) spoke with XOJO Inc&#8217;s Paul Lefebvre about enterprise solutions using XOJO.</p>
<p>We&#8217;re not radio jocks, but it is an interesting topic for technology consumers/developers. The rest of you non-techies with sleep disorders may also find it helpful.</p>
<p>Check it out: <a href="http://blog.xojo.com/xojotalk-021-enterprise-consulting">XojoTalk 21 (Enterprise Consulting)</a></p>
]]></content:encoded>
			<wfw:commentRss>https://www.ical.com/blog/?feed=rss2&#038;p=302</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ICAL celebrates 15yrs in the cloud!</title>
		<link>https://www.ical.com/blog/?p=214</link>
		<comments>https://www.ical.com/blog/?p=214#comments</comments>
		<pubDate>Mon, 04 Jan 2016 17:57:31 +0000</pubDate>
		<dc:creator><![CDATA[Arthur Couture]]></dc:creator>
				<category><![CDATA[News and Events]]></category>

		<guid isPermaLink="false">http://www.ical.com/blog/?p=214</guid>
		<description><![CDATA[ICAL has spent 15 years in the cloud. Yes, we know, we don&#8217;t need to state the obvious, but seriously, we have been developing and later hosting remote applications for 15 years. When we started building remote applications, they weren&#8217;t even called cloud services. We just thought of them as remote programs, just like the <a href='https://www.ical.com/blog/?p=214' class='excerpt-more'>[...]</a>]]></description>
				<content:encoded><![CDATA[<p>ICAL has spent 15 years in the cloud. Yes, we know, we don&#8217;t need to state the obvious, but seriously, we have been developing and later hosting remote applications for 15 years. When we started building remote applications, they weren&#8217;t even called cloud services. We just thought of them as remote programs, just like the network applications we had been building for years.  <span id="more-214"></span></p>
<p>With the Dot Com bubble burst in 2000, we started approaching brick and mortar companies that could use web technology to enhance their business.</p>
<p>ICAL developed its first customer web application in 2001. That year we developed a document image retrieval system for First American Title Insurance. This system began a series of projects that let agents get their own information and order policies directly, online. Previously, company staff had to send document copies via courier or fax to their attorney agents. </p>
<p>This led to 12 years of service and improvements to the company&#8217;s agency business systems. It was transferred to another portion of the company in 2012 and re-written, but the basic system design and functionality continues to this day.</p>
<p>2004 marked the first time that ICAL hosted applications for customers in our data center. We began hosting an accounting solution for a Central American customer. We built a series of servers in our data center to host a Platinum Accounting system for renewable energy developers operating in Guatemala and Costa Rica. </p>
<p>That same year, we developed a web application for CHI Energy, another energy client. This was a web based production reporting system. It tracked energy production and outages for renewable plants in the United States and Canada. </p>
<p>CHI Energy was later purchased by Enel Energy. We continued to support and maintain this application for the next 11 years until it was retired in 2015.</p>
<p>ICAL has gone on to develop and host many &#8216;cloudy web applications&#8217; since then. Today, we regularly develop web applications and hybrid desktop programs that rely on web services both in our data center and elsewhere.</p>
<p>If you have a need for a distributed, web, desktop or hybrid application <a href="../contactjs.html">contact us</a> today.</p>
<p>Happy Computing! </p>
]]></content:encoded>
			<wfw:commentRss>https://www.ical.com/blog/?feed=rss2&#038;p=214</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Internet Explorer support ends &#8211; January 2016!</title>
		<link>https://www.ical.com/blog/?p=218</link>
		<comments>https://www.ical.com/blog/?p=218#comments</comments>
		<pubDate>Mon, 28 Dec 2015 15:56:51 +0000</pubDate>
		<dc:creator><![CDATA[Arthur Couture]]></dc:creator>
				<category><![CDATA[News and Events]]></category>

		<guid isPermaLink="false">http://www.ical.com/blog/?p=218</guid>
		<description><![CDATA[As of January 12, 2016, Microsoft will no longer support bug fixes for Internet Explorer versions older than Version 11. This means that any computer going out on the web with an older browser version is vulnerable to hacking exploits identified after that date. The fix for most of us is to simply upgrade or <a href='https://www.ical.com/blog/?p=218' class='excerpt-more'>[...]</a>]]></description>
				<content:encoded><![CDATA[<p>As of <a href="https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support">January 12, 2016</a>, Microsoft will no longer support bug fixes for Internet Explorer versions older than Version 11. This means that any computer going out on the web with an older browser version is vulnerable to hacking exploits identified after that date. <span id="more-218"></span></p>
<p>The fix for most of us is to simply upgrade or change browsers. Many people or organizations that operate Microsoft Windows based computers have them configured to automatically update. For them this won&#8217;t be a problem. These computers are likely already updated to a later browser version.</p>
<p>Unfortunately, many companies maintain older web applications that only work correctly on older versions of Internet Explorer. If you find yourself or your company in this situation, you need to be aware.</p>
<p>In order to protect the integrity of your company&#8217;s network you need to consider doing one of the following:</p>
<ul>
<li>Limit Workstation Access to other areas on the web</li>
<li>Re-configure your workstations to sandbox the browser</li>
<li>Update your application to use a later browser version</li>
<li>Enforce a policy of only using the outdated browser for your dependent application</li>
</ul>
<p>Ultimately, only updating or re-writing your application will fix the problem. The other solutions will extend the usability of your current solution, but as you purchase new equipment it won&#8217;t have access to the older browser versions.</p>
<p>Check <a href="https://support.microsoft.com/en-us/lifecycle#gp/Microsoft-Internet-Explorer">here</a> for a list of Microsoft Internet Explorer life cycles on distinct operating platforms.</p>
<p>This can be very disruptive to business, but it can be managed so that the impact is minimized. </p>
<p>If you need help that is what ICAL does. We can help. <a href="../contactjs.html">Contact Us</a></p>
<p>As always, Happy Computing!</p>
]]></content:encoded>
			<wfw:commentRss>https://www.ical.com/blog/?feed=rss2&#038;p=218</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Our hosted apps now have a heartbeat</title>
		<link>https://www.ical.com/blog/?p=233</link>
		<comments>https://www.ical.com/blog/?p=233#comments</comments>
		<pubDate>Thu, 17 Dec 2015 22:38:49 +0000</pubDate>
		<dc:creator><![CDATA[Arthur Couture]]></dc:creator>
				<category><![CDATA[News and Events]]></category>
		<category><![CDATA[Tech Insight]]></category>

		<guid isPermaLink="false">http://www.ical.com/blog/?p=233</guid>
		<description><![CDATA[No, we are not kidding. The applications we develop can now optionally have a heartbeat. This isn&#8217;t some new age hippie zen thing to get in touch with your program. Our programs don&#8217;t really have a heart. &#8216;Heartbeat,&#8217; in this case, means programs that we write can now be setup to regularly send out a <a href='https://www.ical.com/blog/?p=233' class='excerpt-more'>[...]</a>]]></description>
				<content:encoded><![CDATA[<p>No, we are not kidding. The applications we develop can now optionally have a heartbeat. This isn&#8217;t some new age hippie zen thing to get in touch with your program. Our programs don&#8217;t really have a heart. &#8216;Heartbeat,&#8217; in this case, means programs that we write can now be setup to regularly send out a signal to show that they are still running properly. <span id="more-233"></span></p>
<p>We developed a set of tools that listen for those signals just like a doctor might listen to your heart. </p>
<p>The &#8216;Heartbeat Monitor&#8217; can be configured to take several different actions when a monitored program fails to signal or signal correctly. Specifically, the monitor can:</p>
<ul>
<li>log an event</li>
<li>allow several failures before acting</li>
<li>notify ICAL staff by text or email</li>
<li>restart a program that has failed</li>
<li>do nothing</li>
</ul>
<p>There are both commercial and open source tools that do similar things, but they are more focused on data center management, not application monitoring. Most provide a lot of abilities we don&#8217;t need, and each lacked a few features that make it easier to watch our monitored applications. </p>
<p>The monitor program and the tools that were needed for each program to talk to it were developed over a year. We began of defining a simple protocol in 2014. In June of 2015, we started testing the process on some of our existing hosted applications.</p>
<p>For ICAL, this means we can can maintain more applications with less resources.  For customers, we can keep our costs lower while providing better service. We don&#8217;t have to pay people to check things 24 hours a day. We do have programs that can.</p>
<p>If you have business application needs <a href="../contactjs.html">Contact Us</a>.</p>
<p>Happy Computing!</p>
]]></content:encoded>
			<wfw:commentRss>https://www.ical.com/blog/?feed=rss2&#038;p=233</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ICAL hosts New England Xojo user group</title>
		<link>https://www.ical.com/blog/?p=254</link>
		<comments>https://www.ical.com/blog/?p=254#comments</comments>
		<pubDate>Fri, 11 Dec 2015 20:23:34 +0000</pubDate>
		<dc:creator><![CDATA[ical]]></dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[News and Events]]></category>

		<guid isPermaLink="false">http://www.ical.com/blog/?p=254</guid>
		<description><![CDATA[We would like to take the opportunity to thank our fellow New England Developers for stopping by on December 8th for the first New England Xojo Meetup. It was both interesting and fun. We were also duly impressed by the caliber of the people attending. The group shared projects that we never imagined being built <a href='https://www.ical.com/blog/?p=254' class='excerpt-more'>[...]</a>]]></description>
				<content:encoded><![CDATA[<p>We would like to take the opportunity to thank our fellow New England Developers for stopping by on December 8th for the first New England Xojo Meetup.</p>
<p>It was both interesting and fun. We were also duly impressed by the caliber of the people attending. The group shared projects that we never imagined being built with this tool set. Based on their experiences, Xojo has demonstrated itself as a versatile platform for building most software solutions that a company may need.<span id="more-254"></span></p>
<p>Part of the discussion focused on how Xojo could be used as key component within an enterprise. It had been used by the group as sort of a Swiss Army Knife for data conversion and presentation.</p>
<p>As techies, we sometimes get caught in our own little world. We forget that getting together once in a while helps us to be better and more successful at what we do. </p>
<p>Thank you ALL for making this successful. In particular, thank you Paul Lefebvre for taking the time to get down here and share some very helpful insights into Xojo and its future direction.</p>
<p>We look forward to hearing from all of you and getting together again. Please <a href="../contactjs.html">contact us</a> with your ideas for what you might like to do in the future. We look  to seeing you all again</p>
<p>Tom &amp; Arthur</p>
]]></content:encoded>
			<wfw:commentRss>https://www.ical.com/blog/?feed=rss2&#038;p=254</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
