PPL

Contact Import should be background syncing

Registered by Christopher Adams

Imports should be placed into the background and update on the main page as they come. All imports should be background queues. The dashboard should ideally update as new contacts come in. There should also be feedback on the dashboard that this is happening. Lets try this first with contacts. If you have over 5000 contacts, its really slow to import.

Blueprint information

Status:
Not started
Approver:
None
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Bassel Safadi
Definition:
Discussion
Series goal:
None
Implementation:
Not started
Milestone target:
milestone icon 0.4

Whiteboard

Bassel, we need to spec out how to do this.

One way would be with a web-based chron, say fire off some small tasks each time someone hits the site, or based upon time.

The other idea is to write some daemon/queue controller that can run in the background on the server. That is how status.net does it. you might talk with @brionv on statusnet about this design...it works really well and is scalable.

However, I would say that the highest priority should be the simplest solution...we don't need web scale on this thing since its intended for single owners.

I think how wordpress handles background tasks with a fake type of chron is a good solution. Thoughts?

In chrome the loading problems not so bad, its mainly in firefox I found this.

###

I think this has to be more specific, like, contact imports takes too long and needs to be put into the background.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.