₦airaland Forum

@Busta
Since your answer is still No why don't we hook up and let me give u some loving .

me i don call the babe o.
She is already taken so make all of una back out now now .

Busta:
answer: NO!!!!!!

Answer YES cos i am one of them.

U mean the North Circular or South Circular

Is there free food? the one i go to regularly in London has free item 7

the prices will still come down.

senorita u need a man ko

zebudaya:
I think a Nigerian girl that likes me is the easiest to decode. yankee chicks claim they like you, but you are one of the 10 guys they like. and every time you mess up the other guy rises up on the scale. You know the next man to bang your woman, you've met him shook his hand. He has ate your bread, drank your wine and he shall betray you,

Spot on bros. I myself am just sick and tired of all these Jand girls.
They give you so many conflicting signals that u just don't know were u stand with them. As long as a nija girl is single and not going out with anyone n shows a little bit of interest in me, i always believe i have a chance to go out with her wit all the fronting of this world. but the reverse is the case with all those stupid Jand Girls.

Abeg make una give 3 gbosas for our beautiful nija girls.

nuellabond:
I really do hope there still good guys out there because i'm tired of meeting the wrong people

Hiya babes. I am one of the nice one.would you like to meet ?

very crappy stuff i'll give 20%

Hi sbucareer.

sbucareer:

Once again Clocky, a Model in MVC is Acronym for Model-View-Controller. MVC was first widely defined in the book "Design Patterns" by Erich Gamma et al. It defines a separation of concerns in a program where the model defines the internal data structures of the program, the view defines how the model is rendered to the user, and the controller performs the actual actions in the program that affect the model.

You and i are talking the same thing. You have finally provided the correct definition for MVC.

sbucareer:


Lecturing about Java interfaces, well you got it right for once, they are frameworking or pattern for writing application. The only good thing about interface is it ability of encapsulating database and offering late binding in Java, which could boost the speed of your application.

Late binding is very difficult to code and debug, because all errors cannot be find at compile time, the errors show them selfs at runtime. Maybe you would lecture me about abstract class or Generics, or even inheritance, any case you lecture will be well taken, one can never know all.

Well java interfaces can be applied to any business logic task not only database operations.The simple advantage offered by interfaces is that it allows u to seperate the implementation of a method from its definition giving you the ability to change the implementation of a method without client programes noticing.

Late binding is a concept that used in Polymorphism

sbucareer:

You have one fixation about what Model is in MVC, remember people can interpret it differently depending on the application they are developing. Please NOTE that Model in MVC is simply describing the database model

I cannot emphasis this more. DAO are java classes packed with a design pattern, probably javabean, DAO that access the data Model of any application by providing the application an internal data structure.

Bravo you are spot on. My argument earlier was that the domain objects is the Model in MVC and the model as you have rightly pointed out is the database model (especially in a database driven app).

Check this link for a clearer defination of domain objects http://en.wikipedia.org/wiki/Domain_objects.

Yes DAO are java classes or PHP classes or VB classes or C++ classes that abstract access to database operations and usually return back results as objects(in this case the data model).

yea chizzle my nizzle

Good then you should be able to understand the concepts. If you really want to do Patterns you have to be prepared to read Java/C++ code because most books and tutorials are written in these langugues.

The pattern bible is available free online at http://lci.cs.ubbcluj.ro/~raduking/Books/Design%20Patterns/contfs.htm. Since u are confortable with C++ most of the examples there are written in C++.

web application oreinted patterns can be found at http://java.sun.com/blueprints/patterns/catalog.html although its in Java try to focus on understanding the concepts and you would better appreciate how you can apply it to PHP

The concept is fundamentally the same. You can easily substitute the java code with PHP. However, It is very important that you understand the concept and most books or tutorials on Patterns u would find around are in Java/C++ . Are u afraid of Java code ? Have a look at http://www.cakephp.org/ there are lots of examples with PHP code there

Sorry sbucareer. i was not tryin to diss u i was just trying to correct some of the stuff you wrote which were not entirely correct.

i have already defined MVC in my previous post but if you want more clarification just visit this link
http://en.wikipedia.org/wiki/Model-view-controller.

sbucareer:

Listen, any componet that access network layers, database or some sort of persistent storage or serializable objects are Model. Your so called Domain Objecta are the database. DAO, are javabeans or entity beans that maps each request object to serializable object.

Your definiation of a model is wrong. You are of the opinion that a DAO is a Java bean .While it is a Java class, it contains methods that you use to access the database. In defining a DAO u would have an interface and an implementation of that interface e.g

public interface CategoryDAO {
    public Category getCategory(String categoryID)
     
}

public class OracleCategoryDAO implements CategoryDAO {
public Category getCategory(String categoryID) {

   1 . select *from category where categoryId =categoryId

   2. create the category object and populate it with all the values returned

  3. reeturn the category object
}

u can see that the DAO is just an abstraction of the underlying database access. It is not the Model it is just a pattern for defining your business logic which in this case is the database access.The beauty about the approach is that it allows you to change the backend database implementation whichout the rest of the application noticing those saving large amounts of developer time . A more detailed explanation can be found at http://java.sun.com/blueprints/patterns/DAO.html


A model on the other hand would be a CategoryObject e.g

public class Category{

private string Categoryname;

public String getCategoryname(){
}
public void setCategoryName(){
}
}

Now in true MVC style what happens is that the model is the glue bettwen trhe contoller and the view as it gets passed around .For example if on the web page u wanted to save a Category u input all the values in the form and then the controller which u correctly identified as a servlet gets all the forms parameters and then creates the Catalog object populates it with values and calls the business logic in this case the DAO which then is responsible for connection to the database and saving the object. It is the same logic vice versa if u are trying to display a catlog on the page. It first gets selected from the database in the DAO and then gets passed to the controller which then forwards to the view which could be a html or jsp or PHP file.

sbucareer:


Middleware, hmm,  where do your Controller lives? View? or Model? Well they can only live in the middleware components. Don't try and tell me the meaning of these things, Basically Controllers in Java are the servlet/JSP. I don't use Servlet on front-end that make Servlet a good candidate for Controller. It maps all the URL request Objects to a properties file that has pair=value i.e

Yes in Java the controller is usually a Servlet which is responsible for mapping URL requests to their respective views.For example in Struts doing somethin like  <action path="/login"
            type="org.apache.struts.actions.ForwardAction"
            scope="request"
            parameter="/WEB-INF/jsp/home.jsp"/>
means that when the servlet encounters /login in a request it should forward to the home.jsp

Yes all the code for the controller, view and model resides in the middleware but i was just trying to correct what u said about the middleware beign the controller. However u most note that the middleware services exists only in fully J2EE compliant servers like JBoss Weblogic etc.

sbucareer:

You need to develop more application from inception to deployment before you can say I am wrong. I wonder how you package and deploy your application?

Na wa o . But this has gat nothing to do with the topic we are discussing

But fronting is good na. I generally like girls that front and play hard to get . For me its is a test of how good i am in wooing a girl. Basically, for me the part i enjoy most in a relationship is when i am trying out all the tricks in the book to woo a girl and the joy i get in seeing her melt to my charms. After that it gets boring for me

I generally dont have any form of respect for girls that dont form. I generally just have sex with them and run for my dear life afterwards.

I never believed in the concept of Artifical intellegence. I think a lot of research had gone into these area with very little succesful commercial applications conmesurate with the amount of funds of research.

recent ones:
Hustle and Flow
Hurricane

Old school:
Juice
Higher Learning
Malcom X
2 can play that Game
and ofcourse Roots

both off them are damn ugly but segun is uglier

sbucareer:


It is horrible, that is all I can say. No controller, No Model, you would have to go through a lengthy peace of code to figure out what is going on.

PHP has some very decent MVC frameworks. The one i have tried is http://www.cakephp.org which has pretty much every design pattern in the book.

sbucareer:


It would be nice to have DAO (Data Access Object) in one file, which is the Model. Have the middleware on one file, which is the controller. Lastly, have the View permanently separated from any form of programming including CSS and JavaScript. Have the CSS written separately and Javascript written separately.

Modularize the whole application, that is what I think a design pattern is. You would also find that most of these components could be reused in another design saving time and money.

The design pattern you choose depends on the application in question.

Correction   a DAO is not the model. A DAO is basically an efficent Data access strategy that helps abstract data access code from business logic. The model is the Domain objects of the application .


The controller is not the middleware. The controller in a web app is basically the code that is responsible for directing users  to various views. For example a controller for an example login page would be responsible for calling the back end business logic, and then directing the user to the next view which could be the home page.

The view is the individual html, PHP or jsp files that is rendered in the browser.

The MVC pattern is a proven way of modularizing a web app however there are various other design patterns that can be applied especially in the business logic layer which can help in efficent reuse of code across projects (eg . DAO).

check out
http://www.cakephp.org/

They have a farely robust implementation of the front controller, MVC , active recorder and DAO patterns .
I have played around with it and it is really awesome !

Shinor:
Guys i just read an article today 9/7/2006 that the FCT Minister is about to release some funds for an abuja rail system to take off. hmmmmm. They must have read these postings.
Also OBJ has just signed some stuff with some canadians to help sort things out, Thanks for the circle line angle

Really, Thats great.

Badman888:
yup its not too late to build a tube, but hey maintainance another problem, it can be used for robbery and so many different disadvantages.

it doesnt even need to be underground. It can be a surface rail. The Light railway network is one of the most effective rail netwoks that can be constructed. It is not only cost effective, it can be constructed relativly easily and its far more easier to maintain and manage.

Since the main problem we have is the fact that government just can't maintain infrastructure, the problem of maintainance can be solved if these rail networks are built on a public-private partnership. While the government provides the necessary framework the private sector would construct and maintain. For example the various lines in london are maintained by various private companies but the whole underground network is managed and controlled by the British transport police and the London underground.