[wp-trac] Re: [WordPress Trac] #8999: Completely New LiveJournal
Importer
WordPress Trac
wp-trac at lists.automattic.com
Wed Feb 4 18:30:09 GMT 2009
#8999: Completely New LiveJournal Importer
-------------------------------------+--------------------------------------
Reporter: beaulebens | Owner:
Type: task (blessed) | Status: closed
Priority: normal | Milestone: 2.8
Component: Import | Version: 2.7
Severity: normal | Resolution: fixed
Keywords: needs-testing has-patch |
-------------------------------------+--------------------------------------
Comment (by ryan):
Replying to [comment:18 beaulebens]:
> A couple points:
>
> 1. Most of the importers write to the filesystem in some way or another
(upload files etc)
They upload one file that goes through all of the various hooks and checks
and receive attachment IDs. I don't know of any importeres that write to
the filesystem outside of that.
> 2. I'm open to another way of doing it, but there's no way to handle
big imports from the LJ API that I could come up with other than files
since the data is very likely to exceed memory limits (especially when you
have to juggle multiple copies of things to re-thread comments, which
aren't threaded when you receive them)
> 3. I agree the var_export thing is kinda scary, but it performed
significantly better than serialize/unserialize (and assuming that it's
necessary to store things between steps, something needs to be used to
maintain array structure)
serialize is scary too. The main concern is doing a php include of this
stuff later. Can it not go through the options DB, where we have some
checks for proper serialization, at least, and where we don't have to do
includes.
> 4. I'm aware of the Snoopy issue, and am working on adding cookie
support to the HTTP API right now.
Okay.
--
Ticket URL: <http://trac.wordpress.org/ticket/8999#comment:26>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list