[Typo3-dev] LPE-some ideas

[Thomas Murphy]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Sebastian,

Sebastian Kurfuerst wrote:
| I had some thoughts about a LPE because I will need it in a project and
| so I made a concept for me how to do it. I try to explain my thoughts to
| you because I hope you can make comments what's missing, what's good and
| maybe you want to help implementing it because I think it's a lot of work.

I may be interested, even if i have some other work to do right now and
an extension work-in-progress, so i can't promise anything. But i did
have some thoughts about that i want to share.

| ?? Do we need a field where the server id of the records is stored?

Definitely. On a per-page and per-content basis i think. That would give
us a much higher flexibility. Think about someone editing a page on the
server (which should still be allowed to enable people to edit the
content from different locations) and someone creating a new page on the
client at the same time with the same page-id or content-id.

The theory behind CVS or other version systems may be helpful for this
concept, basicly it's good old branching and merging stuff.
Maybe if a user logs in to the client, a "working-copy" is fetched from
the server which updates all changed tables. On a "reload page-tree"
this is done again, to show if something else changed which interferes
with the client-side changes.

| ?? Is it a good idea to use public-key encription=?

Do we really need encryption like that at all? It sounds as sexy as the
term "XML" - i agree, but when we are just sending the appropriate
backend user information through SSL, wouldn't that be enough?

| ?? Should the checksum of the answer be sent back to the server to make
| sure the transmission was successful or isn't that necessary?

It seems to be a good idea. At least for debugging.

| **Server**
| The server is a kind of "stupid", so it just does what the client tells
| him and the logic which data shall be transmitted will be on the client.

Still you need some logic on the server to handle the requests and to
the encryption stuff. My thought on this was an extension which is
installed both on the client and the server. They are like gateways to
the rest of typo and we always know where the scripts are installed
(typo3conf/ext/...)
A part of those scripts however is not directly linked to nor recognized
by typo - these scripts are triggered to do the neccessary changes to
the tables, while the other scripts just do the new icons and click-menu
entries in the page-tree.

| -exclusion table, to make sure that not all the records are transmitted
| (like be-users)

Would this be neccessary? I mean you can exclude tables to BE-Users and
they just would not be shown to the user. And if only individual records
are transmitted to the server, that would only be those he is able to see.

| On later versions, it could be possible to make a sync between the
| server and the client, but I don't know if it makes any sense. What do
| you think?

I think it would, because on complex sites, it may be difficult to get
an overview about all changed pages, an "sync all" option would be a
great feature, maybe just below the "Reload-page-tree" link.

| The problem is how to transmit data on the file system. Do you have any
| thoughts how to deal with that effectively?

FTP? The table data can be passed to the above mentioned scripts, and
the "fileadmin" resources could be transferred by FTP. Maybe with
builtin zip functionality.

| I hope you understood me, I'm no native speaker.

Ich auch nicht. :)

bye,
Murphy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAONF/wO0pDATctOARAp/iAJ9BpWpkAeNgyX0wBnnqSV9AaHNWvwCghq2t
2TFx9Z2UtcGNgUi2K86T+nc=
=22aZ
-----END PGP SIGNATURE-----