Re: BXE Wishlist

On Sun, Nov 21, 2004 at 12:47:26PM -0500, Jean Pierre LeJacq wrote:

> I'm also concerned that BXE sometimes completely deletes a file when
> an error occurs.  A more transactional approach is really essential
> so that if BXE fails, we are left with at least the original
> content.

I don't see how BXE, running on the client-side as it does, could
possibly delete a file on the server-side, or do as you seem to
require.

I would've thought that it is the responsibility of whatever you have
on the server side, accepting content from BXE, to implement this
functionality, not BXE; that is to say that the "acceptor" on the
server side should check that the incoming content from the editor (be
it BXE or otherwise) is an appropriate replacement (e.g. not empty,
valid XML, and whatever other rules-u-like) for what's currently there
(if anything).

Short of inventing a protocol for two-phase-commit over HTTP (or
adopting IBM's RHTTP), implementing it in BXE and insisting that
server-side BXE-serving scripts implement it too (eek!), I don't see
how it could be done. This would seem like gross overkill to me and a
poor substitute for pretty simple defensive programming.

Cheers,

Emmet.

-- 
,----------------------=[ [email protected] ]=------------------------.
| Internet Software & Business Automation.           C, Perl, XML, SQL |
| Legal: http://netrogen.com/about/email.php       Unix/Linux, Windows |
`---------------------=[ http://netrogen.com/ ]=-----------------------'
-- 
bx-editor-users mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-users