Private Messaging Suggestions

[Ideahoppers]

I am creating a site that will allow users to interact with each other via private messages. It can look like a message board - but should only be viewed by the two people that are involved in the conversation. What is the best tool for this? Can anyone link me to some tutorials or api's?

[Ernie1]

Here's an example:

CREATE TABLE IF NOT EXISTS `pm` (
  `id` int(11) NOT NULL auto_increment,
  `fm` varchar(12) default NULL,
  `to` varchar(12) default NULL,
  `sj` text,
  `bd` text,
  `date` datetime NOT NULL default '0000-00-00 00:00:00',
  `read` char(1) default NULL,
  PRIMARY KEY  (`id`)
);

php code

<?php

// for insert
if (! empty($fm) && ! empty($to))
{
    $request = mysql_query("INSERT INTO pm SET fm='$fm', `to`='$to', sj='$sj', bd='$bd', date='$date', `read`='n'") or die(mysql_error());
}

// for reading
$query = mysql_query("SELECT id, fm, sj, bd, date FROM pm WHERE id=$id AND `to` ='" . $_SESSION['login'] . "'") or die(mysql_error());

// update the table, set the message as read
mysql_query("UPDATE pm SET `read` = 'y' WHERE id=$id AND `to` ='" . $_SESSION['login'] . "'") or die(mysql_error());
// ...

[Jake Arkinstall]

Ernie, why abbreviate the field names so drastically?

It's much more readable if you used:

$query = mysql_query("SELECT ID, From, Subject, Body, Date FROM PrivateMessages WHERE ID=$id AND To ='" . $_SESSION['login'] . "'") or die(mysql_error()); 

[Cups]

Not sure if you want to use a very simple forum, but take a look at Vanilla, this permits 2 or more users to have conversations that only appear in each others version of the "thread".

This means that these users are "posting" but their side conversations remain private, not sure if that is what you mean. It could be worth looking at if your aim is more than the requirement you posted.

The default install is very stripped down, and you progressively add features if you need them.

I like it.

[XtrEM3]

ernie, i'm gonna have to second jake's sentiments: i can't stand abbreviated identifiers. i understand it's personal preference, but i prefer all my variables to be self-documenting -- i feel this assists the readability beyond just myself. while writing code i typically refactor any given variable 2-3 times; as a variable's role adapts and becomes more apparent, i clarify its purpose by refactoring the variable.

[offtopic]do you guys feel google wave replace the need for individual websites to code their own message systems? i'm hopeful that it will become fairly widespread and that all message systems will lead this route.[/offtopic]

[imaginethis]

ernie, i'm gonna have to second jake's sentiments: i can't stand abbreviated identifiers. i understand it's personal preference, but i prefer all my variables to be self-documenting -- i feel this assists the readability beyond just myself. while writing code i typically refactor any given variable 2-3 times; as a variable's role adapts and becomes more apparent, i clarify its purpose by refactoring the variable.

[offtopic]do you guys feel google wave replace the need for individual websites to code their own message systems? i'm hopeful that it will become fairly widespread and that all message systems will lead this route.[/offtopic]

While I agree with you on your self-documenting remark I'm overly anal about visual symmetry of my code and tend to abbreviate database columns and form variables. A stupid reason, but it annoys me. And its a pain in the tush having to be creative names. I'm no fan over used camel-casing, hyphens and so on -- only when it comes to forms and database table columns... Pet peeves and such ._.