Real Estate Transport Protocol Abstract

For my next conference paper, I plan to submit the following abstract on one of the two internet protocols I invented not too long ago. Real Estate Transport Protocol (RETP) is the messaging and provisioning protocol for an eventual global multiple listing service in the not so distant future. The diagram depicts the actors and message flows. Full explanation will be discussed in the conference paper.

Title: Real Estate Transport Protocol: The Internet’s Multiple Listing Service Messenger

Abstract

Today’s multiple listing services (MLS) are antiquated, legacy systems due to tight coupling to their localized market and lack of interoperability. Moreover, these same MLSs are operated as controlled gateways eliminating public access, competition and global network distribution. This paper discusses a new internet protocol called Real Estate Transport Protocol (RETP) that resolves these inefficiencies. Using reserved internet port 32811, RETP provides a fire-and-forget messaging protocol for sending and receiving listings over the Internet to geographically distributed MLSs known as registrars. RETP creates a hub-and-spoke network topology for provisioning listings from a centralized registry to authorized registrars securely. Three messaging scenarios are discussed for demonstrating RETP’s operations: registrant to registrar, registrant to registrar to registry, and then finally, registrant to registrar to registry to multiple registrars.

Keywords: multiple listing service, internet protocol, distributed computing, network theory

--Corey

Happy First Birthday WWMLS

Last Saturday marked the first birthday for the World Wide MLS (WWMLS). Since then, the follow progress has been made towards WWMLS:

• Presented Multiple Listing Service Network (MLSN) Protocol at the University of Central Florida 2011 Research Fair


• Ongoing data research and collection of legacy mls numbers on the World Wide Web (WWW)


• Development integration with Red Hat's Openshift Platform as a Service (PaaS)


• Accepted Exhibition of MLSN Protocol at Nonprofit Technology's (NTEN) 2012 Confernece and Science Fair in San Francisco
  
• Accepted MLSN Abstract Paper for presenting at American Real Estate Society (ARES) in April of 2012

As MLSN is presented to different groups such as academics and technologists, I am confident with the two upcoming presentations in 2012, especially in St. Petersburg at ARES, that the MLSN Protocol and WWMLS framework will alter others' thought processes of not only the dysfunctional aspect of today's legacy MLS, but also future directions in how real estate consumers interact and expect a specific quality of service (QoS) from real estate professionals. The main intention is integrate WWMLS in every aspect of the future of real estate.

Moving foward, the second phase for WWMLS will be the introduction of the messaging language called Real Estate Metadata Language (Remetal). This XML language will be used to markup properties in a self-describing, yet simple language for sending and receiving between the main OpenMLS Registry and accredited OpenMLS Registrars. I plan to propose Remetal to additional call for papers (CFP) on the academic and technical levels in 2012.

The third yet most important phase will be for the Real Estate Transport Protocol (RETP). This protocol defines the type of messaging, the distribution channels, error correction system, etc. Again, RETP papers will be proposed along with exhibitions at national and if necessary global science fairs.

The future of real estate is bright and changing.

And as the cliche goes, please stay tuned...

--Corey

Servicemix-file Message Flow Diagram

For the last few weeks, I've been head down in ESB concepts and programming. Below is a diagram I created using creately.com. The diagram depicts the message flow of a file within a directory which is then passed to the "bus". It's routed through servicemix service engines (eip, http, camel, saxon) and then finally written to an "out" directory on the file system.

[caption id="attachment_90" align="aligncenter" width="632" caption="Servicemix-file messaging flow diagram"][/caption]

JBoss Messaging Installation Hack

To use JBoss ESB, I needed to install a messaging system within JBoss 5.0 GA. I chose JBoss Messaging 1.4.4 and swallowed the red pill.


RTFMing the docs, I cd'd to the util directory and then ran: ant -f release-admin.xml. First try failed with the following error message:

BUILD FAILED
Warning: Could not find file ...\path\to\jms\jms-ra.rar to copy

So I vi'd release-admin.xml and read the copy command found on line 116. Looks like it wanted a jms-ra.rar in a directory called jms. I examined my jboss installation and didn't find a jms directory present within my developmental server so I created a jms/ directory and copied an available copy of jms-ra.rar into the jms directory.

Unfortunately, you cannot just simply rerun the install file, release-admin.xml, straightaway. You must remove the messaging/ directory completely before reinstalling.

rm-rf messaging/
(I know, I know, this is a no no but my first red bull of the day was still in full circulation. :) )

After removing the messaging/ directory, I retried:

ant -f release-admin.xml

Success! The build was successful and now it's on to JBoss ESB and the helloworld.esb for testing messaging and eventual soap client service.