14.9.07

Marshalling a.k.a Serialization

I have been wondering what Marshalling means for quite sometime. Got a chance today to google and found these 2 useful definitions.

Def 1: Marshalling is the process of transforming the memory representation of an object to a data format suitable for storage or transmission. It's typically used when data must be moved between different parts of a computer program or from one program to another.
Source: Wikipedia

Def 2: The process of gathering data and transforming it into a standard format before it is transmitted over a network so that the data can transcend network boundaries. In order for an object to be moved around a network, it must be converted into a data stream that corresponds with the packet structure of the network transfer protocol. This conversion is known as data marshalling. Data pieces are collected in a message buffer before they are marshaled. When the data is transmitted, the receiving computer converts the marshaled data back into an object.

Data marshalling is also required when passing the output parameters of a program written in one language as input to a program written in another language.
Source: Webopedia

2.8.07

Declarative Programming

Continuing from my earlier post, the J2EE framework that I was reading claimed about Declarative Programming. Although I have some idea about this, I tried googling to get more info and hit upon this nice article in Code Magazine http://www.code-magazine.com/Article.aspx?quickid=050053.

I have also saved a pdf version of the page here http://mukundhan.googlepages.com/Declarative_Programming.pdf, just in case the article is removed in the future.



If you have more comments about declarative programming or the article, please leave a comment.

Labels: ,

31.7.07

What is expected of a Software Developer ?

I was reading on the specification of a particular Oracle proprietary J2EE framework and came across this line -

The framework's declarative approach to building application user interfaces frees developers from the need to learn a vast array of changing technologies.

The words "frees developers from the need to learn new technologies" kind of puzzled me. It is like saying use this framework and you don't have to learn anything new after that. But doesn't that kill the creativity of the developer? For me creativity from a developer's perspective is thinking on the lines how to better use the framework and to analyse inherent problems in the framework. Also to check if there are other frameworks doing things in a better way.

Some of the marketing gimmicks used by these framework documentation are really silly. Anyway, I'm not going to consider that a plus in any framework.

Labels: ,

Back after a hiatus

I'm back to blogging after a big break. Will try to be more regular.

28.2.06

New Blog ... First Post !!!

This is my new blog. Just started it today. I definitely feel that a blog is the best way to voice one's intentions and get heard and also receive good/bad feedback on the same.

I'm NOT keen on hits or readership, I would be more happy if I get appealing feedback from just a few of you regularly.

I really want to post regularly and will definitely try to do that.