Saturday, March 24, 2012

xml-motor ~ what it is; how & why should you use it

xml-motor ~ what it is; why & how you should use it

Download this article as pdf on what,why,how

or read it all here.....

Late 2011, I started with a new rubygem project for parsing xml, html content.
  @GitHub     :

Just created it to test out my work at compact, quick & easy xml-parsing algorithm... can see that

So, currently this is a non-native, completely independent less-than-250 ruby-LOC available as a simple rubygem to be require-d and use in an easy freehand notation and match with any node attributes.

Current Features:
  • Has a single method access to parse require xml nodes from content or file. Use it only if you are gonna parse that xml-content once. For using same xml-content more than once, follow the 3-way step mentioned in examples.
  • It doesn't depend on presence of any other system library, purely non-native.
  • It parses broken or corrupted xml/html content correctly, just for the content it have.
  • Can parse results on looking for node-names, attributes of node or both.
  • Uses free-freehand notation to retrieve desired xml nodes
    if your xml looks like,
      <book> <title>ABC</title> <author>CBA</author> </book>...
         <authors> <author>XY</author><author>YZ</author> </authors></book>...

    and you look for '',
    then, you'll get back ['CBA', 'XY', 'YZ'];
    what that means is the child-node could be at any depth in the parent-node.
  • Default return mode is without the tags, there is a switch to get the nodes.
    as you'd have seen in above example:
    'CBA' gets sent by default, not 'CBA'
  • To filter your nodes on the basis of attributes, single or multiple attributes can be provided.
  • These attribute searches can be combined up with freehand node name searches.
  • Readme (a bit weird):

Features To Come:
  • Work on making it more performance efficient.
  • Limit over result-nodes retrieved from start/end of matching nodes.
  • Multi-node attribute-based filter for a hierarchical node search.
  • Add dev-knows CSS Selector, it's already present using attribute based search... just need to add a mapping method.

EXAMPLES of usage:
example code to try:
  • say, you have an xml file 'dummy.xml', with data as
      <ummy>    <mmy class="sys">non-native</mmy>  </ummy>
        <mmy class="sys">      <my class="sys" id="mem">compact</my>    </mmy>
      <mmy type="user">    <my class="usage">easy</my>  </mmy></dummy>
  • its available at, install it as
      $ gem install xml-motor
  • include it in your ruby code,
      #!/usr/bin/env ruby
      require 'xml-motor'
  • get the XML Filename and/or XML data available
      fyl = File.join(File.expand_path(File.dirname __FILE__),'dummy.xml')
      xml =,'r'){|fr| }
  • One-time XML-Parsing directly from file
      XMLMotor.get_node_from_file(fyl, 'ummy.mmy', 'class="sys"')
         Result: ["non-native", "\n      compact\n    "]
  • One-time XML-Parsing directly from content
      XMLMotor.get_node_from_content xml, '', 'class="usage"'
         Result: ["easy"]
  • Way to go for XML-Parsing for xml node searches
      xsplit = XMLMotor.splitter xml
      xtags  = XMLMotor.indexify xsplit

      [] just normal node name based freehand notation to search:

        XMLMotor.xmldata xsplit, xtags, ''
        Result: ["compact", "easy"]
      [] searching for values of required nodes filtered by attribute:
        XMLMotor.xmldata xsplit, xtags, nil, 'class="usage"'
        Result: ["easy"]

      [] searching for values of required nodes filtered by freehand tag-name notation & attribute:

        XMLMotor.xmldata xsplit, xtags, '', 'class="usage"'
        Result: ["easy"]

      [] searching for values of required nodes filtered by freehand tag-name notation & multiple attributes:

        XMLMotor.xmldata xsplit, xtags, '', ['class="sys"', 'id="mem"']
        Result: ["compact"]

Monday, March 5, 2012

messQ ~ just a fun little project providing socket-based Queue service

messQ is a small project started to implement and improve in the areas of message queue mechanisms.

What it does currently? Just a Network Service to be connect and enqueue/dequeue messages.

What it requires? Ruby, terminal and your fingers :)

Git it:           $ git clone git://

Start messQ server:       $ ruby messQ.rb
  This starts a message queue server at  port 8888.

Enque new message:
  Open a connection at port 8888, then say "enq MESSAGE_TO_BE_QUEUED".

Deque oldest message:
  Open a connection at port 8888, then say "deq". It returns the dequed message.

 _  _   __   ___  ___     _____
||\/|| //_  //_  //_  _  //  //  messQ v0.0.1beta
||  || \\_  __// __//   //__//\\_  simplistic socket message Q