<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="http://blog.linklogics.com/feed/rss2/xslt" ?><rss version="2.0"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Not your average Monitoring Solution!</title>
  <link>http://blog.linklogics.com/</link>
  <atom:link href="http://blog.linklogics.com:82/feed/rss2" rel="self" type="application/rss+xml"/>
  <description></description>
  <language>en</language>
  <pubDate>Thu, 29 Dec 2011 18:32:13 +0100</pubDate>
  <copyright></copyright>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Dotclear</generator>
  
    
  <item>
    <title>Launched!</title>
    <link>http://blog.linklogics.com/post/2010/03/01/Opened%21</link>
    <guid isPermaLink="false">urn:md5:78e1ee6a26782ddf065edb4458838449</guid>
    <pubDate>Mon, 01 Mar 2010 14:17:00 +0100</pubDate>
    <dc:creator>LinkLogics</dc:creator>
            
    <description>    &lt;p&gt;After several months of hard work, challenging the business plan, crafting
the technical architecture, making developments, evaluating mathematical models
of web performance, QA testing and organizing everything, it's time to open the
gates and offer the service to our customers. How exciting!&lt;/p&gt;
&lt;p&gt;When I started to evaluate this business opportunity and asked myself what
added value I could bring to the over-saturated market of web monitoring, I
just thought &amp;quot;quality&amp;quot;. As a web professional and software architect, I had to
deal with quality of service issues so many times I can't even count. It was
time to bring something new to this market. To create new metrics, to create
new ways of evaluating the performance of web applications.&lt;/p&gt;
&lt;p&gt;Competition are doing great thing, but to be alerted when a website is down
is inadequate, we need ways to prevent this to happening, to be alerted when
the quality of service degrades, because most of the time overhead and resource
contention can be predicted with an analytical model based on the monitoring
data collected.&lt;/p&gt;
&lt;p&gt;That's how our qMark and QoSoRP indicators were born: as accurate measures
of quality of service, specifically created for the web, that we can observe
reliably over time and use to assess quality and performance.&lt;/p&gt;</description>
    
    
    
          <comments>http://blog.linklogics.com/post/2010/03/01/Opened%21#comment-form</comments>
      <wfw:comment>http://blog.linklogics.com/post/2010/03/01/Opened%21#comment-form</wfw:comment>
      <wfw:commentRss>http://blog.linklogics.com/feed/atom/comments/490844</wfw:commentRss>
      </item>
    
</channel>
</rss>
