₦airaland Forum

binger: Mass-terminate? Masate?

Mass-exterminate
Mass-contaminate
Mass-communicate

ItsModella: y'all still say that stuff?

Ogbunike

once onye Agba-enu, always onye Agba-enu.

So, i bu onye Agba-enu

CFCfan: Ok. Self service is a synonym for a word that starts with 'm' and ends with an 'e'.

male? manage? me?

ItsModella: Anambra

onye agba-enu
ebee n'Anambra

[quote author=acidosis™]pls what is 'sexual act' ?[/quote]An act that is intimate

Idowuogbo: Smh!

Mama wey dey young

CFCfan: Yeah, I've been here since the middle of August.

August visitor

ItsModella: mba o, I like rom nka, i yi onye di ime..e prefer'm nke ikpazu..

onye ebe ka ibu

binger: lmao!!

what? you don't like my pinshure
girls dey die for me o

xynerise: Are you an Albino?

https://upload.wikimedia.org/wikipedia/commons/thumb/9/9a/Albinisitic_man_portrait.jpg/230px-Albinisitic_man_portrait.jpg

shey i fine

xynerise: who is madam?

Oga, i think say na your wife o

xynerise: I will give you the loan when more come

6 and counting
madam, should i send my account number

xynerise: u forgot to tell him the other thing I ordered u. Report to my office first thing tomorrow morning.

oga...oga.. i no fit enter office tomorrow o...my wife dey for labour.
Infact oga i want ask you for loan. my wife don born quadruplets and the doctor say more are still coming

[quote author=e-talker]Why will my boss ask me to cut off my Banky W kind of beard? The guy dey look for my trouble oooo.[/quote]Wait, you came here to complain
If i see you with that nonsense in my office tomorrow eeee

toria1980: Can anyone help me with good site where I can download softwares free.....​am tired of buying fake from Otigba
Thanks all

Otigba doesn't sell FAKE, they sell Pirated. Its either you download pirated, free or you BUY.

FlowCab is a world class phone-in taxi service company operated by Flow Technologies limited.
Primarily established to provide hassle free movement to residents and visitors of Port-Harcourt, the garden city of Nigeria.
And also to provide chauffeur driven taxi services from Port-Harcourt to neighboring states.

There philosophy is anchored on two principles: Safety and Comfort.

The corporate mission of FlowCab is to provide convenient taxi cab service that is safe and comfortable to commuters with helpful drivers, reliable vehicles and supported by friendly staff.

They offer Cab services for every occasion and event:

Basic taxi runs
Airport pick-up & drop-off
Corporate taxi pooling
Daily taxi hire
Special taxi service
School runs
Domestic services
Social functions
Event rides
And more...

You can book online http://www.flowcabng.com
or call them on +234(0)8030541326, +234(0)8091405714 +234(0)8083779633




Meanwhile, give me feedback on the design. Thanks
by http://www.SpikesInteractive.com

Browsers: Firefox, google chrome, comet bird
Email client: Thunderbird
Adobe Master collection CS5
AVG
Chess Titans
Huawei Mobile Partner
Notepad++
MS Notepad (for writing love letters )
Opera Mobile Emulator
Recuva (Clients doesn't care if you deleted a 2 months project folder )
Skype
Virtual DJ
Wamp


e don pass abi..
I never mention hardcore games ooooo

princenonny: @ spikes, u r a plain fool....chima took us 10 yrs forward Nonsense man. I bet u r an ebeano loyalist

thank you sir, am a humanist and never materialistic

And they're still using emails, can you imagine

Ok, make i advertise small

At Spikes Interactive

We have a Human Resource Management System (HRMS).
It's actually an Intranet with an internet based modules.
It has fully automated recruiting processes. The web based modules include but not limited to;

1. A company website
2. An e-recruitment form (The sweetest part)
During recruitment, the applicants apply online with custom inputs (And also upload a file based CV).
During filtering, you just select the inputs you require, sort it the way you like and choose the number of applicants you want for your next process
which might be background checks, 1st interview, cover letter filtering etc.

You don't need to download anything, everything is viewed securely in your intranet.
You can notify the applicants automatically too if need be.

The Intranet modules features include but not limited to;

1. Staff Management
2. File Management
3. Staff payroll
4. Staff training, performance and appraisal
5. Loan Management
6. Leave Management
etc.

Other customized modules include but not limited to;

1. Hotel Management
2. E-commerce Management
3. Housing Estate/Renting Management
etc.

We're also adding Staff attendance bio-metric roaster.
Whereby when a staff comes to work, he/she goes to the attendance table (an unmanned computer), and logs in for the day with his/her finger print.

To get more detailed info, don't hesitate to
Call us on : 08035553259
Email us: support at spikesinteractive.com
Or you can just use the contact form on our website: http://www.spikesinteractive.com/contact

We give wings to your dreams

What is wrong with you people self

Even in US, minors DO NOT PARTAKE IN CONTRACTS, all you have to do is provide a suggestion.

It's better to allow minors partake in the competition but come with their parents/guidance during legal stuffs. SIMPLE

binger: Wizard,ututu oma.

wetin u still dey do here..your mates dey for bed with them wives. leave these children for us nah

All the winchy winchy....
good morning

pak: Coding techniques differ. and different frameworks might implement things in diff ways.
Where I work, we use an in house developed framework for our apps.
In php for example, a loose code sample to deal with sessions might look like this in my app

to set

auth_obj = new testingClass(username, password) ;

$session[entityid] = auth_obj->getValidLogin() ; //techniques differ but here a value of 0 indicates invalid login, a value represents valid login and id of the entity

---------------


to retrieve user details after validating successfully logged in user on each page

$entitty_id = $_SESSION['entityid'] ;

$entity = new entityClass($entitty_id ) ;


// now with your entity object instantiated as local to your code, you can have access to any info you want about the entity without overusing sessions.

Just my two cents - more consistent, neater, easier to maintain
For brevity sake, i ignored stuffs like sanitizing inputs and so on . .. . .

Thats good, i have understood your concept.
But actually differs from what i thought you had in mind.

i would have loved it if the entityClass is the only one who knows what your session names are.
Therefore, you have only one place to edit the names if need be.

example

class entityClass(){

    private $user_id = 0;

    private function __construct($entity_id = 0){

        //the user probably checks for login before this
        if($entity_id = 0){$this->user_id = $_SESSION['USER_ID'];}

    }

}

example methods:

$entity = new entityClass();


$entity->get_id();
$entity->get_personal_details();

etc.

therefore, based on this your code.

$entitty_id = $_SESSION['entityid'] ;

$entity = new entityClass($entitty_id ) ;

I did rather just

$entity = new entityClass();

or

$a_different_entity = 2;

$entity = new entityClass($a_different_entity);

So, if it's a group development (which is the point of OOP )

No developer would include the $_SESSION variable in his code, except ofcourse, he knows what he's doing.




Finally, thanks for your tutorial. Really appreciate the time and effort. PHP lives on

SEUN, pls give us a CODE tag.

donsax: Where is that lucky girl to say hi to donsax? Add donsax on your bbm with 227D0592 only Lucky gal..

born2fuck was right, boys really need kitty cat

smh

UCAS registration is ending tomorrow, 15th January 2013. check to see whether your school requires it and register now.

Though as they said..

Applications received by the above deadlines are guaranteed to be considered by the universities and colleges. Applications received at UCAS after the deadlines, up until 30 June, will only be considered by the universities and colleges if they still have vacancies for the course(s) you have selected.

pak: I agree with most of what you wrote bro . . . .
but let me point out the parts I don't agree with.

Yes i do, when it is neccessary. Most of my codes use OOP technique. I am more comfortable dealing with object properties and methods. I'll rather have the logged in user as an object. It just makes your coding easier thru the life span of your app. E.g. a point might come when you might need to have access to a user whose id is coming from another source - e.g from post or as a output of some other computational activities. Just plug in the id to your class and you're good. Or maybe some unique situations/modules where you have two different entities you are dealing with at a time. Just create two instances and your data is better managed.

I think this is rather easy, encapsulation. You're just saying, do not access the session variables directly but through objects.
You don't wanna see $_SESSION variable lying around everywhere. That's a very good point, Thank you for this.

pak: I keep telling ma peeps , never set/use sessions IN your classes. (The operative word here is IN). If your session needs to interact with you class. Let them be introduced as ARGUMENTS not in the class/method definition itself but rather in the code that calls the methods. That way the modularity of your code is preserved.

Still makes a lot'a sense, seriously, you're teaching me OOP
But lets have an example, there's one class which cannot follow this rule. The session setter class(basically the login class. it needs to set the needed sessions, right?).
But maybe, as you might be thinking, the names and values of the sessions should be passed to a session setter class.
***I need your comment on this***

But without Java, ther's no android.... right?

Tashamania: Awwwww dear! Just take it easy, okay? Whatever it is, you'll be fine. Be rest assured about that. There's no problem without a solution and you're not the first such is happening to

now, give us a smile

you be winch
did he tell you what is exactly wrong with him

ah ah ah ah...Now i understand where you're coming from.
I am sorry for putting you in this mess of explanation, but atleast other people can learn from it.

pak: 1. global vs local - Its advisable to always use local variables as opposed to globals when you can (we shouldn't be going thru this again man . . ) Sessions are 'super globals'.

Yes, super globals are highly avoided but this can be wrong. There're a few basic things i store in my sessions.

.The logged in User's ID.
You can't actually get this variable from database without doing another username|password login (very bad to hold a user's password)

.The logged in flag (e.g $_SESSION['LOGGED_IN'] = TRUE)
.The logged in user's account status(e.g $_SESSION['ACTIVE'] = TRUE)
.The logged in user's email validation status(e.g $_SESSION['EMAIL_VALID'] = TRUE)
.The logged in user's username (e.g $_SESSION['USER'])if this is highly used around the application

Others might be unread messages count, unread notifications count etc.

The above are variables you use on every page load, do you expect someone to keep getting those data from the DB everytime.

pak: 2. code reuse/ modularity - I have seen cases where sessions are used inside functions and classes. I find it gross. The idea about modules is to ensure they can be used in several places and application when needed. If I do not have the same session bank as the module you were working on when developing the said class/function. then I'll be stuck reusing the said class in my module. I have had to refactor a lot of (other people's) code with this problem and it wasn't a nice experience

The OOP/reusable code problem. actually people don't use session variables in distributed codes, unless the particular module sets and uses it. You don't expect a session management class or even a login management class not to set, use and insert $_SESSION variable in their code....(maybe am misunderstanding you here)

pak: 3. The browser issue I talked about involves a situation where some browsers store session information across every open tab while some don't. Yes, some versions of IE and some other browser actually keep session information on different tabs seperate. So if information about the current user is stored in a session, things can get quite messy. believe me I have been there. The issue is that with local variables you have ABSOLUTE control over how your variables are passed around.

Now, i think you're misusing setting cookies and setting sessions.
My chairman, if the browser doesn't return the session ID, PHP will not identify the user, and your application will ask the user to login again.
Via setting cookies, always check if your cookie is set first and sanitise the returned value before using it.

pak: 4. Classes/DB - Best practice, IMHO is to only use sessions to store the IDENTITY of the current user/state. Info about the user should be retrieved from DB and preferably stored as an object. You get neater easier to maintain codes that way and most importantly. Variables don't just jump at the developer from anywhere . Don't u just get mad when you're working on someone else's code and you just start to wonder where a var suddenly appears from/ where it was set. Thats the 'effect' of session misuse. You just get variables lying around in your applications without knowing how they got there or what they hold. Making teamwork a nasty experience. Even with register_globals off. Its still sickening to have a session value being used in application without knowing exactly how it is set. As I said above best practice is to only store the IDs and use classes/DBs to fetch other info you need. This ensures that all the variables you are working with are actually local to module you're working on at that time.

Exactly, store only IDENTITY.

This part makes a whole lot'a sense and i can tell you, am guilty of this crime a few times (I think just once, am still trying to refactor that code)
I believe, that sessions should be used to store only sitewide/general application data
(e.g user's prefered display language, user's ID, logged in details)
Not modular application's variables (with exemptions like variables needed on every pageload (USE NAMESPACING))

But lets talk practical.
Database: the biggest problem in application development. DB is costly, very costly...this is why most developers store slightly reusable variables in sessions. Something that might be used only on even 2 or 4 seperate pages.
It's like debating DB normalization. In theory, it should be, practically, na your server go hear am

Another thing is documentation. A very important thing that is always left out.
It doesn't take much to describe what your super global variables are, when they're set and when they're used

[quote author=gree-die]ah ah.... im good naw.. y r u mean to me who is spreading lies abt me? [/quote]uhh sorry sweety, just pushing ur legs
Oya smile for me

Sijo01: .....wtf are you talking about?

Mr. hamattan catching your legs nah

Sijo01: I don kno o....d tin seems powerful, it has turned my legs to an unknow colour.

what? red color? he has broken ur ********