multi-user

In my chatting application I want to implement Group Chatting functionality. For the same I want to create rooms and send the invitations to my friends to join the room. Here is my code to join and invite the friend to room. To Create the Room //Create Room btn_CreateRoom = (Button)findViewById(R.id.btn_usermenu_CreateRoom); btn_CreateRoom.setOnClickListener(new View.OnClickListener() { @Override public void onClick(View arg0) { // TODO Auto-generated method stub try { muc = new MultiUserChat(connection, "room1@conference.abc.com"); muc.join("Sunil","123456"); muc.sendConfigurationForm(new

I'm developing a php / mysql application that handles multiple simultaneous users. I'm thinking of the best approach to take when it comes to locking / warning against records that are currently being viewed / edited. The scenario to avoid is two users viewing the record, one making a change, then the other doing likewise - with the potential that one change might overwrite the previous. In the latest versions of WordPress they use some method to detect this, but it does not seem wholly reliable - often returning false positives, at least in my experience. I assume some form of ajax must be in

I really don't want to re-invent the well here, so I'm asking for ideas to implement a simple (row) lock mechanism in a multi-user DB application. Suppose I have a Table called Products which of course has an ID (PK), and also a rowversion column (which is not used so far), and I want to allow only one user to be able to Edit a specific row. While this users is editing the record (after a "check in"), other users can only View this record (read-only), but not modify or delete it. when the user is done and saved the record ("check out") this record will be again available for editing/deleting

I have created an MS Access 2003 application, set up as a split front-end/back-end configuration, with a user group of about five people. The front end .mdb sits on a network file server, and it contains all the queries, forms, reports, and VBA code, plus links to all the tables in the back end .mdb and some links to ODBC data sources like an AS/400. The back end sits on the same network file server, and it just has the table data in it. This was working well until I "went live" and my handful of users started coming up with enhancement requests, bug reports, etc. I have been rolling out new

I have a web page that shows a large amount of data from the server. The communication is done via ajax. Every time the user interacts and changes this data (Say user A renames something) it tells the server to do the action and the server returns the new changed data. If user B accesses the page at the same time and creates a new data object it will again tell the server via ajax and the server will return with the new object for the user. On A's page we have the data with a renamed object. And on B's page we have the data with a new object. On the server the data has both a renamed object