PHP serialize recursive (circle) referencing objects.

Problem:

object1->ref = object2

object2->ref = object1

serialize(object1) & unserialize it failed in PHP

Solution: http://www.phpclasses.org/browse/package/5336.html

or check this file: recursive-serialize.zip (download, rename to .zip and extract)

Common issues of Web application

validate

session/server state & observer

ajax

template

cache

resource compress

client & observer

Common issues of Winform Application

validate & exception (multi-actions per click).

status/error/result message.

transaction.

fullload/lazy load, multi referencing, client & db & sever syn.

navigator.

transaction.

multi-threading and synchronize

worker thread

exception handling

undo/redo.

binding data.

Some note for ORM select

inheritance? (multi-table? single-table)

relation?

behavior?

soft delete? (mark = id –> ensure unique constraints)

cascade delete?

generate class from db or vice verse?

validation?

performance?

Some note for Roles & Task

for PM Role:

• Ensure document enough for reference (specifications, database, business rule, code sample document – some thing like how to implement … in this project) (follow up work-flow, and ask what data, how, why, when, what, any differ from, how to handle if status/value = enums).
• Avoid conflict between business rules/requirement.
• Split tasks, set expected finish date, track progress (percent of finish, problem).
• Assign task based on previous works & available time (tasks should related)
• Ensure code consistency, follow patterns, convention, backward compatible (with Senior/TA to suggest & approve model, code review (1)).
• Each code sample should be approved based on 2 options(better from 2 dev/senior).
• Avoid multi-track of code (one issue but handle my more than one place).
• Ensure process of task (review reference code if new task before implement, implement, video test).
• Valuate performance base on the arguments in team (=> have to track it), and work result (deadline, idea, code quality, team co-working).
• Ensure enough scenarios in check list form.

for Senior/TA Role:

• How to handle common issues (log, display error, transaction) consistency
• Functional programming => easy extend/modify in future.
• Apply design pattern as possible, choose which model so that general enough, less & template work/care for devs, performance, flexibility (1), backward compatible.
• Keep in my, this code/business rule can be change in future.
• Flow best practice of framework.
• Implement & document sample code (some thing like how to … in this project).
• Ensure code consistency, follow patterns, convention (with Senior/TA to suggest & approve model, code review).

for Dev Role:

• code follow samples (how to implement in this project document).
• Keep in mind about the convention.
• Functional programing & self-comment code.
• Test carefully and record video.
• Suggest better model, alarm conflict/duplicate between business rules, code model.
• reported implemented cases/scenarios, in check list form.

some note for cross browser

1. float & display order.

2. double margin + float in ie6.

3. css selector base on attribute [name=value] on IE6.

4. max-height, max-width on ie6.

5. png transparent backgroud in IE6.

6. opacity issue (filter vs opacity vs -moz-opacity)

7. clear break & overflow: auto

8. body center-align: margin-left: auto; margin-right: auto;

9. table-less form: use div.form-row and clear: both, fix focusable div in ff2