<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Dmitriy&#039;s blog - Software category</title>
  <link>http://7bee.j2ee.us:80/blog/categories/SFTW/</link>
  <description>Thoughts, articles, reviews and more</description>
  <language>en</language>
  <copyright>Dmitriy</copyright>
  <lastBuildDate>Mon, 30 Aug 2010 03:21:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Spring, Ruby, Grails, Hibernate.. do we really need them?</title>
    <link>http://7bee.j2ee.us:80/blog/2010/08/13/1281743940000.html</link>
    
      
        <description>
          &lt;p&gt;
Perhaps nobody will argue against using frameworks. They improve code quality, take care of many routine tasks and suppose to speed up development time. However is it really faster and cheaper do development using popular web application development frameworks. Here are my thoughts. Most of frameworks, especially created on top of some language like Java, F# or C++ will require not only knowledge of the language, but also good knowledge of framework capabilities, API and so on. Using Hibernate isn’t eliminating a requirement of knowledge of SQL. A developer is still not isolated from knowledge of JavaScript, HTML, CSS and other web technologies even when GWT is used. However pushing on certain framework, you immediately get tied to a specific skill set and you need a developer with several years experience with certain framework or development tool. So far, only WebBee building blocks are complete web application development stack requiring only knowledge of Java, SQL and basic web technologies. So if you are passionate about just being used base technologies and interested in helping making WebBee better, then do not hesitate to contact e.
&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Software</category>
    
    <comments>http://7bee.j2ee.us:80/blog/2010/08/13/1281743940000.html#comments</comments>
    <guid isPermaLink="true">http://7bee.j2ee.us:80/blog/2010/08/13/1281743940000.html</guid>
    <pubDate>Fri, 13 Aug 2010 23:59:00 GMT</pubDate>
  </item>
  
  <item>
    <title>TJWS as virtual hosting solution</title>
    <link>http://7bee.j2ee.us:80/blog/2010/07/18/1279497840000.html</link>
    
      
        <description>
          &lt;p&gt;
I am really pleasant with result of using TJWS for hosting multiple web sites. I was originally skeptical and tried to use Apache-Tomcat, however ended by Tomcat crashing every 8 hours which was unacceptable for site with really low load I can’t monitor 24/7. So I decided to give a try TJWS and magic happened. All problems were gone. It looks solid rock. More important, some packets loss I observe for Apache-Tomcat were magically eliminated, so I do not suffer from incomplete page load anymore. So if you host some websites in virtual environment and face some instability problem, then you can try TJWS, however use only version 1.80, since previous version has security problem.
&lt;/p&gt;
&lt;p&gt;Try this &lt;a href=&#034;http://www.doopper.com&#034; target=&#034;_blank&#034;&gt;site&lt;/a&gt;. Yes, the Doopper is just a virtual host.
        </description>
      
      
    
    
    
    <category>Software</category>
    
    <comments>http://7bee.j2ee.us:80/blog/2010/07/18/1279497840000.html#comments</comments>
    <guid isPermaLink="true">http://7bee.j2ee.us:80/blog/2010/07/18/1279497840000.html</guid>
    <pubDate>Mon, 19 Jul 2010 00:04:00 GMT</pubDate>
  </item>
  
  <item>
    <title>Programmatic web browsing</title>
    <link>http://7bee.j2ee.us:80/blog/2010/06/11/1276304340000.html</link>
    
      
        <description>
          &lt;p&gt;
Unfortunately all web interfaced programs give us some webservices APi to use their nice features in different desktop or other web programs. In most cases the problem can be resolved just using some proxy software to discover data exchange protocol and then wrap it in few nicely designed classes.  Since not all vendors aware of using their software in strictly REST protocols, you need to deal with some data residing in JavaScript of web page to continue using product functionality. I found myself doing the same work as maintaining cookies, finding certain patterns and so on again and again. So I decided to create some utility package helping to break web application for programmatic use. I would like to hear other person experience in breaking different web applications. My library is here.

&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Software</category>
    
    <comments>http://7bee.j2ee.us:80/blog/2010/06/11/1276304340000.html#comments</comments>
    <guid isPermaLink="true">http://7bee.j2ee.us:80/blog/2010/06/11/1276304340000.html</guid>
    <pubDate>Sat, 12 Jun 2010 00:59:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>
