If you wanna know about someone , listen ,deal and observe , only you can say who I am

Hi all こにちわ皆さん :)
If you wanna know about someone , listen ,deal and observe , only you can say who I am
My name is Moustafa Mahmoud ( you had probably discovered that already ) . I am crazy , i am enthusiastic and i am dreaming . I believe that if it is not crazy enough , it doesn't worth to be done.
Currently i am a computer engineering student at cairo university, I Adore not only learning about new technologies,But also being a part of their development. Outside college and study I love the japanese culture and language , I also love and enjoy Martial Arts, Specially Aikido I love to write too :) hope you enjoy your time here :)

Latest

Future of Web-development :NodeJs Tutorial part 4 Useful request handlers

So far we successfully laid out the modules that we need for our application , and connected them together , Right now, we need to be able to make the request handles be able to send back something to the user ( reply ) , if you come from a PHP / python background you might want to prepare the content and return it up the layes till the server sends it back to the user , but then you are blocking all operations till the result return , and since the javascript doest generate a thread for every request , all the other users request will experience delay till the slow request returns .

so instead of sending the result generated by content handler to the server , we want to send the server to the request handler, ie. passing a reference from the response object to the request handler . and the request handler can use that reference to serve the content it needs to the user .

so here is how our modifications should reflect on our file :

first the server.js

var http = require("http");
var url = require("url");
function start(route, handle) {
function onRequest(request, response) {
var pathname = url.parse(request.url).pathname;
console.log("Request for " + pathname + " received.");
route(handle, pathname, response);
}
http.createServer(onRequest).listen(8888);
console.log("Server has started.");
}
exports.start = start;

router.js

function route(handle, pathname, response) {
console.log("About to route a request for " + pathname);
if (typeof handle[pathname] === 'function') {
handle[pathname](response);
} else {
console.log("No request handler found for " + pathname);
response.writeHead(404, {"Content-Type": "text/plain"});
response.write("404 Not found");
response.end();
}
}
exports.route = route;

Last the requestHandles.js

var exec = require("child_process").exec;
function start(response) {
console.log("Request handler 'start' was called.");
exec("ls -lah", function (error, stdout, stderr) {
response.writeHead(200, {"Content-Type": "text/plain"});
response.write(stdout);
response.end();
});
Building the application stack 47
}
function upload(response) {
console.log("Request handler 'upload' was called.");
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello Upload");
response.end();
}
exports.start = start;
exports.upload = upload;

Now our application can respond to requests without blocking and depending on each other .

Serving Something useful

now we connected the parts of our application together and we are ready to serve content to the user, we will discuss a simple example of handling post request ..

Handling POST requests

We will present a textarea that can be filled by the user and submitted to the server in a POST request. Upon receiving and handling this request, we will display the content of the textarea.

The HTML for this textarea form needs to be served by our /start request handler, so let’s add it right away, in file re-questHandlers.js

function start(response) {
console.log("Request handler 'start' was called.");
var body = '<html>'+
'<head>'+
'<meta http-equiv="Content-Type" content="text/html; '+
'charset=UTF-8" />'+
'</head>'+
'<body>'+
'<form action="/upload" method="post">'+
'<textarea name="text" rows="20" cols="60"></textarea>'+
'<input type="submit" value="Submit text" />'+
'</form>'+
'</body>'+
'</html>';
response.writeHead(200, {"Content-Type": "text/html"});
response.write(body);
response.end();
}
Building the application stack 51
function upload(response) {
console.log("Request handler 'upload' was called.");
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello Upload");
response.end();
}
exports.start = start;
exports.upload = upload;

I can guess that you are thinking that including view inside controller is ugly , but i didnt want to include that in this crash course and you can easily find how to do this abstraction using a simple search 🙂

lets rather now discuss how we are going to serve the post request in a non blocking way  Which makes sense, because POST requests can potentially be very large

To make the whole process non-blocking, Node.js serves our code the POST data in small chunks, callbacks that are called upon certain events. These events are data (an new chunk of POST data arrives) and end (all chunks have been received).

We need to tell Node.js which functions to call back to when these events occur. This is done by adding listeners to the request object that is passed to our onRequest callback whenever an HTTP request is received. This basically looks like this:

now where to put this logic , i decided to put it in the server logic because it is up to the server to prepare the data of the request and send it along to the request handler .

lets start with server.js

var http = require("http");var url = require("url");function start(route, handle){function onRequest(request, response){var postData ="";var pathname = url.parse(request.url).pathname;
console.log("Request for "+ pathname +" received.");
request.setEncoding("utf8");
request.addListener("data",function(postDataChunk){
postData += postDataChunk;
console.log("Received POST data chunk '"+
postDataChunk +"'.");});
request.addListener("end",function(){
route(handle, pathname, response, postData);});}
http.createServer(onRequest).listen(8888);
console.log("Server has started.");}
exports.start = start;

Let’s add even more awesome to our app. On the /upload page, we will display the received content. To make this possible, we need to pass the postData on to the request handlers, in router.js:

function route(handle, pathname, response, postData) {
console.log("About to route a request for " + pathname);
if (typeof handle[pathname] === 'function') {
handle[pathname](response, postData);
} else {
console.log("No request handler found for " + pathname);
response.writeHead(404, {"Content-Type": "text/plain"});
response.write("404 Not found");
response.end();
}
}
exports.route = route;

And in requestHandlers.js, we include the data in our response of the upload request handler

function start(response, postData){
console.log("Request handler 'start' was called.");var body ='<html>'+'<head>'+'<meta http-equiv="Content-Type" content="text/html; '+'charset=UTF-8" />'+'</head>'+'<body>'+'<form action="/upload" method="post">'+'<textarea name="text" rows="20" cols="60"></textarea>'+'<input type="submit" value="Submit text" />'+'</form>'+'</body>'+
Building the application stack 56'</html>';
response.writeHead(200,{"Content-Type":"text/html"});
response.write(body);
response.end();}function upload(response, postData){
console.log("Request handler 'upload' was called.");
response.writeHead(200,{"Content-Type":"text/plain"});
response.write("You've sent: "+ postData);
response.end();}
exports.start = start;
exports.upload = upload;

One last thing for this topic: what we pass on to the router and the request handlers is the complete body of our POST request. We will probably want to consume the individual fields that make up the POST data, in this case, the value of the text field. We already read about the querystring module, which assists us with this:


 

var querystring = require("querystring");
function start(response, postData) {
console.log("Request handler 'start' was called.");
var body = '<html>'+
'<head>'+
'<meta http-equiv="Content-Type" content="text/html; '+
'charset=UTF-8" />'+
'</head>'+
'<body>'+
'<form action="/upload" method="post">'+
'<textarea name="text" rows="20" cols="60"></textarea>'+
'<input type="submit" value="Submit text" />'+
'</form>'+
'</body>'+
'</html>';
response.writeHead(200, {"Content-Type": "text/html"});
response.write(body);
response.end();
}
function upload(response, postData) {
console.log("Request handler 'upload' was called.");
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("You've sent the text: "+
querystring.parse(postData).text);
response.end();
}
Building the application stack 58
exports.start = start;
exports.upload = upload;

Well , You can now test your application , and i guess having that running , means that you are ready to go out there in the wild world and start learning and mastering NodeJs on your own , the community is getting bigger by the day and you wont find  difficulty finding more tutorials and material , this tutorial itself was taken from ” The Node Beginner Handboo”

More Sources to learn NodeJS

 

The official website and documentation

http://www.nodejs.org/

 

The NodeCloud directory  (contains a mega collection of sites related to Node JS )

http://www.nodecloud.org/

 

The NodeJs  community wiki

https://github.com/joyent/node/wiki

 

 

 

Future of Web-development :NodeJs Tutorial part 3 organizing the application

Lets First talk a little why and discuss why do we even need to consider the asynchronous pattern of NodeJs

Event-driven asynchronous callbacks

Node’s approach isn’t unique, but the underlying execution model is different from runtime environments like Python, Ruby,PHP or Java.

Let’s take a very simple piece of code like this:

var result = database.query("SELECT * FROM bigtable");
console.log("Hello");

now the way we have written this code will require the interepter to first finish the query (which might take alot of time ) before printing the “hello” text , because this is sequential code . php / java / python code will work the same way if the code is written this way .

However, in the execution model of PHP, this would not become a “global” problem: the web server starts its own PHP process for every HTTP request it receives. If one of these requests results in the execution of a slow piece of code, it results in a slow page load for this particular user, but other users requesting other pages would not be affected.

The execution model of Node.js is different – there is only one single process. If there is a slow database query somewhere in this process, this affects the whole process – everything comes to a halt until the slow query has finished.

To avoid this, JavaScript, and therefore Node.js, introduces the concept of event-driven, asynchronous callbacks, by utilizing an event loop.

Now lets consider a modified version of this code :

database.query("SELECT * FROM hugetable", function(rows) {
var result = rows;
});
console.log("Hello World");

Here, instead of expecting database.query() to directly return a result to us, we pass it a second parameter, an anonymous function.

Now what just happened is that we told NodeJs to go and start executing the query and continue the flow of the problem and make note that at some point in the future when the query finishes i have to execute an anonymous function / any function i specify for it , so the Program flow is not blocked by the slow Database Query .

back to our HTTP server

var http = require("http");
function onRequest(request, response) {
console.log("Request received.");
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello World");
response.end();
}
http.createServer(onRequest).listen(8888);
console.log("Server has started.");

How our server handles requests

first we defined our function that will handle the request , when a call back happens our function gets triggered and two objects are passed to it the request and the reply , Those are objects, and you can use their methods to handle the details of the HTTP request that occured and to respond to the request (i.e., to actually send something over the wire back to the browser that requested your server).

Organizing our Application

right now we have a very simple http server in a file that we will rename server.js , it is common to have a main file called index.js in our website that is used to bootstrap and start our website by making use of other modules of the application  like our http (server) module .

How to create our modules

Making a code into a module is simply a matter or exposing its functionality , for our server module we need to export the functionality of starting a server , to make this possible we will put our server code into a function named start and export it .

var http = require("http");
function start() {
function onRequest(request, response) {
console.log("Request received.");
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello World");
response.end();
}
http.createServer(onRequest).listen(8888);
console.log("Server has started.");
}
exports.start = start;

this way we can create our index.js file and start the server from there , making our code cleaner and modular, the index.js file will contain this code :

var server = require("./server");
server.start();

That’s it. We can now start our app via our main script, and it still does exactly the same:

node index.js

Now we need to handle another important aspect of our application , we need to be able to serve the user in a different way according to the Url he is asking for , ie we need to handle “routing” in our applications , and we are going to moduleize that as well.

So, we need to look into the HTTP requests and extract the requested URL as well as the GET/POST parameters from them.It could be argued if that should be part of the router or part of the server (or even a module of its own), but let’s just agree on making it part of our HTTP server for now.

All the information we need is available at the request object but to access and tackle them we need extra NodeJs Modules called url and querystring

The url module provides methods which allow us to extract the different parts of a URL (like e.g. the requested path and query string), and querystring can in turn be used to parse the query string for request parameters

url1

Let’s now add to our onRequest() function the logic needed to find out which URL path the browser requested:

var http = require("http");
var url = require("url");
function start() {
function onRequest(request, response) {
var pathname = url.parse(request.url).pathname;
console.log("Request for " + pathname + " received.");
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello World");
response.end();
}
http.createServer(onRequest).listen(8888);
console.log("Server has started.");
}

exports.start = start

Now our application distinguishes between requests based on URL path requested , now lets write our router.
create a file called router.js and inside it we need the following contents
function route(pathname) {
console.log("About to route a request for " + pathname);
}
exports.route = route

our http server now needs to be wired into this router , and to do so , simple we need to modify our server.js to receive an object of router class and use it route the request .

var http = require("http");
var url = require("url");
function start(route) {
function onRequest(request, response) {
var pathname = url.parse(request.url).pathname;
console.log("Request for " + pathname + " received.");
route(pathname);
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello World");
response.end();
}
http.createServer(onRequest).listen(8888);
console.log("Server has started.");
}
exports.start = start;

we also need to modify our index.js to become

var server = require("./server");
var router = require("./router");
server.start(router.route);

Routing to our Request handlers

Let’s create a module called requestHandlers, add a placeholder function for every request handler, and export these as methods of the module:

function start() {
console.log("Request handler 'start' was called.");
}
function upload() {
console.log("Request handler 'upload' was called.");
}
exports.start = start;
exports.upload = upload;

Now we need to make a decision: do we hard-code usage of the requestHandlers module into the router, or do we want a bit more flexibility ?

Of course for many reasons we should go with the flexible solution because as our application goes bigger , hardcoding becomes more and more of a trouble .

This means we need to pass the request handlers from our server into our router, but this feels even more wrong, which is why we should go the whole way and pass them to the server from our main file, and passing it on to the router from there.to pass them we need a more elegent way that checking for each request with

if request == x then
call handler y

A varying number of items, each mapped to a string (the re-quested URL)? Well, sounds like an associative array would be a perfect fit. JavaScript objects are just collections of name/value pairs, how can they have methods? Well, the values can be strings, numbers etc. – or functions!

Let’s start with putting the object together in our main file index.js:

var server = require("./server");
var router = require("./router");
var requestHandlers = require("./requestHandlers");
var handle = {}
handle["/"] = requestHandlers.start;
handle["/start"] = requestHandlers.start;
handle["/upload"] = requestHandlers.upload;
server.start(router.route, handle);

After defining our object, we pass it into the server as an additional parameter. Let’s change our server.js to make use of it

var http = require("http");
var url = require("url");
function start(route, handle) {
function onRequest(request, response) {
var pathname = url.parse(request.url).pathname;
console.log("Request for " + pathname + " received.");
route(handle, pathname);
response.writeHead(200, {"Content-Type": "text/plain"});
response.write("Hello World");
response.end();
}
http.createServer(onRequest).listen(8888);
console.log("Server has started.");
}
exports.start = start;

Now lets modify the route function

function route(handle, pathname) {
console.log("About to route a request for " + pathname);
if (typeof handle[pathname] === 'function') {
handle[pathname]();
} else {
console.log("No request handler found for " + pathname);
}
}
exports.route = route;

 

What we do here is, we check if a request handler for the given pathname exists, and if it does, we simply call the according function. Because we can access our request handler functions from our object just as we would access an element of an associative array, we have this nice fluent handle[pathname]();  expression that would trigger the request handler .

 

In the next tutorial we will talk about how to make our request handlers actually respond and serve something useful for the users ..

Future of Web-development :NodeJs Tutorial part 2 , Hello World first Server

Now having  discussed what NodeJs is , lets get down to business and develop our first application

The HelloWorld Famous Program

to start and test your development environment all you have to do create a file called “hello.js” or anything you want ,and you will just write

console.log('Hello World!');

then invoke your script by navigating to the folder and using the Command Line type

node hello.js

You should see 'Hello World!' displayed in the console.

if  it displays an error telling you that it cant find the specified program (Node) make sure that the NodeJs path is added to the environment variable PATH , you can easily google how to do that 🙂

or if you are too lazy , just check the answer to this question

http://stackoverflow.com/questions/8768549/node-js-doesnt-recognize-system-path

First HTTP server

Now lets move on to creating our first http server , basicly that is all the code we need to start a basic http server

// Include http module.
var http = require("http");

// Create the server. Function passed as parameter is called on every request made.
// request variable holds all request parameters
// response variable allows you to do anything with response sent to the client.
http.createServer(function (request, response) {
   // Attach listener on end event.
   // This event is called when client sent all data and is waiting for response.
   request.on("end", function () {
      // Write headers to the response.
      // 200 is HTTP status code (this one means success)
      // Second parameter holds header fields in object
      // We are sending plain text, so Content-Type should be text/plain
      response.writeHead(200, {
         'Content-Type': 'text/plain'
      });
      // Send data and end response.
      response.end('Hello HTTP!');
   });
// Listen on the 8080 port.
}).listen(8080);

This code is simple. You can send more data to the client by using the response.write() , but you have to do that before calling response.end(). Save this code as http_hello.js and type this into your console:

node http.js

or you can create a file called (anything).bat – must be .bat make sure it is not .bat.txt” and inside it paste the

node http.js

line and you can just click it to run your server or any NodeJs application 😉

To test your app  you can open your browser and navigate to http://localhost:8080 you should see your message printed 🙂

Note : You have to use an empty port , if the port 8080 is occupied by any other program you have to change that

The Result 🙂 

http1

Analyzing our HTTP server

Well, then, let’s analyze what’s actually going on here.

The first line requires the http module that ships with Node.js
and makes it accessible through the variable http.
We then call one of the functions the http module offers: createServer. This function returns an object, and this object has a method named listen, and takes a numeric value which indicates

the port number our HTTP server is going to listen on.
Please ignore for a second the function definition that follows
the opening bracket of http.createServer.
We could have written the code that starts our server and makes
it listen at port 8888 like this:

var http = require(“http”);
var server = http.createServer();

server.listen(8080);

 

The really interesting part is the function definition is  right there where you would expect the first parameter
of the createServer() call. ie you defined the function in its place in the parameter list !!

Passing functions around

one thing about java is that you can do sth that would seem strange like that :

function say(word) {
console.log(word);
}
function execute(someFunction, value) {
someFunction(value);
}
execute(say, “Hello”);

 

This way, we don’t even need to give the function a name when we define it in its place in the parameter list , which
is why this is called an anonymous function.

 

In the next Tutorial We will discuss how to modulize your web application and start developing a complete web app using NodeJS

Future of Web-development :NodeJs Tutorial part 1

NodeJs

 

What is NodeJs and why would anyone use it ?
short answer : PHP and other scripting language can be  93% slower than Node.js!

Node.js is a server-side software system that is  designed for writing scaleble Internet applications, notably Web servers. Programs are written on the server side in JavaScript (Back-End)  using event-driven, asynchronous (Non-Blocking ) way to minimize  overhead and maximize  scalability. it is simply a platform built on Google Chrome ‘s JavaScript runtime  (V8 JavaScript runtime )  ,it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Node.js was created by Ryan Dahl starting in 2009, and its development and maintenance is sponsored by Joyent, his former employer.This is the link to its Wikipedia page where you could read more about it . Link

To start using Node.js, you must first understand the differences between Node.js and traditional server-side scripting environments (eg: PHP, Python, Ruby, etc).

Asynchronous Programming

Every function in Node.js is asynchronous. Therefore, everything that would normally block the thread is instead executed in the background. This is the most important thing to remember about Node.js. For example, if you are reading a file on the file system, you have to specify a callback function that is executed when the read operation has completed.

All is in your Hands

NodeJs is just an environment, so you mainly do everything with your hands , that might seem like a bit more work for you, but it allows you to have full control over your application, There is not a default HTTP server, or any server for that matter  One script handles all communication with the clients. This considerably reduces the number of resources used by the application.

for example here is a comparison between the run times of an application written using PHP and NodeJs

this is PHP version

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
$a = null;
$b = null;
$c = null;
$i = null;
$max = 1000000000;
$start = microtime(true);
for ($i = 0; $i < $max; $i++) {
    $a = 1234 + 5678 + $i;
    $b = 1234 * 5678 + $i;
    $c = 1234 / 2 + $i;
}
var_dump(microtime(true) - $start);

this is the NodeJs version

1
2
3
4
5
6
7
8
9
10
11
12
13
var i, a, b, c, max;
max = 1000000000;
var d = Date.now();
for (i = 0; i < max; i++) {
    a = 1234 + 5678 + i;
    b = 1234 * 5678 + i;
    c = 1234 / 2 + i;
}
console.log(Date.now() - d);
Now lets look at the results
Number of iterations Node.js PHP
100 2.00 0.14
10’000 3.00 10.53
1’000’000 15.00 1119.24
10’000’000 143.00 10621.46
1’000’000’000 11118.00 1036272.19

PHP is notably faster with a smaller amount of iterations, but that advantage quickly dissolves as the number of iterations increases. When all is said and done, PHP is 93% slower than Node.js!

Node.js is fast, but you will need to learn a few things in order to use it properly.

Modules

Node.js uses a module architecture to simplify the creation of complex applications. Modules are akin to libraries in C, or units in Pascal. Each module contains a set of functions related to the “subject” of the module. For example, the http module contains functions specific to HTTP. Node.js provides a few core modules out of the box to help you access files on the file system, create HTTP and TCP/UDP servers, and perform other useful functions.

Including a module is easy; simply call the require() function, like this:

1
var http = require('http');

Remember Node.js is only an environment; you have to do everything yourself.

The require() function returns the reference to the specified module. In the case of this code, a reference to the httpmodule is stored in the http variable.

Installation

Installation is very easy , you just download and setup NodeJs for your system form http://www.nodejs.org/

I don’t need a new Me

Moustafa Mahmoud

Me

well okay , let’s think this straight , I can’t just go on saying I need to change myself , get a new me , or I will stop making mistakes like these , because let’s face it , these are part of who I really am and these are not mistakes , I have to deal with who I am and what I do , so it won’t be a new me or anything like that , because let’s face it , I will never change , and I am learning , getting stronger every day and I am not losing a lot , In fact with every day I am winning , getting to master how  the special me functions , thanks for all who really cared about me and who stood by me while I was down , the words of this song ” we own it ” just keeps ringing in my head

”

I never feared death or dying

I only fear never trying

I am whatever I am,

Only God can judge me,

“- 2 Chainz & Wiz Khalifa – We Own It

I mean why would I regret something I wanted at some point in my life , it is not a weakness in me , on the contrary it is me being strong and going after something I desire , this is absolutely strength and if I don’t get it , then screw it , the thrill of trying is enough for me , I am who I am , I live fast , I can risk anything , I don’t care , as long as I would feel happiness doing it then I am doing it , when I lose something that means it was never mine to get from the start or it is not the time yet to get it , so why being sad 😀 .

It will be just me , I will have fun , chase my old dreams , maybe get some action in my life , and about things that fell from my life and I got sorry about them , weight cut , just weight cut from my back , only from now on I will take care more where I put my effort …

someday

iStock_000016097473XSmall1

Someday everything will all make perfect sense. So for now laugh at the confusion, smile through the tears, and keep reminding yourself that everything happens for a reason Every action has a reaction, Always remember that whats meant to be will always find a way to come about and sometimes good things fall apart so better things can fall together so Live with intention. Walk to the edge. Listen hard. Practice wellness. Play with abandon. Laugh. Choose with no regret. Appreciate your friends. Continue to learn. Do what you love. Live as if this is all there is , you may not know why or how, but God does & that is all that matters! have trust in god that Everything will be all right in the end If it s not all right then it s not the end .

Make your life better in 30 steps

1.Don’t compare your life to others’. You have no idea what their journey is all about.
2.Don’t have negative thoughts of things you cannot control. Instead invest your energy in the positive present moment
3.Don’t overdo; keep your limits
4.Don’t take yourself so seriously; no one else does
5.Don’t waste your precious energy on gossip
6.Dream more while you are awake
7.Envy is a waste of time. You already have all you need.
8.Forget issues of the past. Don’t remind your partner of his/her mistakes of the past. That will ruin your present happiness.
9.Life is too short to waste time hating anyone. Don’t hate others.
10.Make peace with your past so it won’t spoil the present.
11.No one is in charge of your happiness except you.
12.Realize that life is a school and you are here to learn.
13.Problems are simply part of the curriculum that appear and fade away like algebra class but the lessons you learn will last a lifetime.
14.Smile and laugh more
15.You don’t have to win every argument. Agree to disagree.

Community:

1.Call your family often
2.Each day give something good to others
3.Forgive everyone for everything
4.Spend time with people over the age of 70 & under the age of 6
5.Try to make at least three people smile each day
6.What other people think of you is none of your business
7.Your job will not take care of you when you are sick. Your family and friends will. Stay in touch.

Life:

1.Put GOD first in anything and everything that you think, say and do.
2.GOD heals everything
3.Do the right things
4.However good or bad a situation is, it will change
5.No matter how you feel, get up, dress up and show up
6.The best is yet to come
7.Get rid of anything that isn’t useful, beautiful or joyful
8.When you awake alive in the morning, thank GOD for it

While you practice those steps, share them with other people …
Not only will it enrich YOUR life, but also that of those around you.

I don’t want the world to end on Friday 21-12-2012

They say the world would end on Friday 21-12-2012 , even thought i want it to end , even though i am under immense pressure , and that i am really breaking down , because of college and stuff , but u still have hope , i still have dreams that i have been dreaming of , hopes i want to see real , i don’t want the world to end next Friday ,  I still have goals to achieve , people  to be near to  , happiness to feel , happily ever after to get , i don’t deny that i curse life most of the time , i feel depressed and i don’t want to live , because i feel like living in a wrong world , i have lost faith in my dreams and hopes several time , and each time , just before i completely give up , god throws me a hand , i see a sparkle of hope shining , a piece of rope that i could hold on to live for another day ,to fight another day , and to reach the edge of my breakdown later , sometimes i feel like god is helping me to become a special person , to shape me into someone special , but sometimes i feel like god is giving me hell on earth , every possible torture is being given to me while i am still alive ,i laugh like 100 times/ day , just to cover up my troubles and pain , it is strange that among all of that i felt love , dunno how , don’t know why , how could the feeling of love reach someone like me , and somehow i still have hope , even if it is very little , but somehow i cant kill it , i don’t want the world to end just yet , i just want everything to change on Friday 21-12-2012.

Not For Long

Dying quietly, screaming with pain, but not for long ,
I am dying inside , wondering if in your heart will i ever  belong ,
Patience has a limit and soon my actions you will behold.

I gave you your time , i am willing to give you much more ,
waiting for you to find words , for your mind to settle down,
To make up your mind if giving me a chance is right or wrong.

Will you give me a chance to get closer to you , or is it sure that you won’t ?

Cmpsamurai 17-12-2012 11:12 PM

Hope For More …

Ignore me, keep me at a distance and treat me unfair ,
Whatever you try to do to push me away , i will always be there ,
Reply to my 100 word messages  with just a pair ,
I will never lose interest , i will always care .

All unplanned ,i did not prepare ,
I never  chose your place in  my heart,
I just pray and hold on to faith instead of despair .
Is there any hope or was it doomed from the start  ,

Loving you is like an addiction i tried so long to get a cure for,
I don’t know exactly why it started , I don’t know if the ending will be happy or ,
I cannot predict anything , it is like going into the third world war ,
Crazy in love with you , Everyday i think of you and yet all of that you ignore ,
I just will not accept that all my feeling ,hopes , care and trials will be swept offshore .

Cause i really love you ,i don’t want all your attention now , i just hope for more

Cmpsamurai – 16/12/2012 12:16AM

Create your own website, free on WordPress.com.Create your own website.
Start free