Re: Re: Extra (persistant) tier

david forums wrote:

To make persistant object with php use serialize and include the object into session. it's the only way with php

tell it to Mr. Rethans: http://talks.php.net/show/srm-ffm2004 and also read here to get a better understanding of the possibilities/ limitations: http://php.net/manual/en/ref.sem.php Catalin has a point in that its likely that any persistence layer you manage to add that is not native C will probably be lacking the required performance. Have you tried running the code on a Quad-CPU box with 12Gigs of RAM and 15K drives? that may sound sarcastic but its not meant to be - hardware is very cheap compared manhours (i.e. your development time) from a business perspective (regardless of that fact that its seems to take forever to earn enough money to buy a new laptop ;-/ )

regards david Le Wed, 22 Jun 2005 14:43:51 +0200, Catalin Trifu <catalin@isp-software.de> a écrit:

    Hi,

    Basically you can take your mind off object persistance in PHP

unless you code a C extension yourself which would do such a thing.

    Besides code accelerators and caching techniques there isn't much

to play with; at least none that I know of. Catalin Evert | Rooftop wrote:

Hi, I'm writing a big web application, and trying really hard to seperate business logic and presentation, which been no problem up to now. Because I abstracted the business logic so much the framework became heavier, sometimes a simple action can take up to 2 mb memory and several extra milliseconds. I know this doesn't sound much and I'm applying all kinds of technique's to reduce resource-usage and increase speed. The thing is, I feel like I need to split the business tier up in 2 tiers, one of them being my persisitant object manager. The main reason is because every script that is executed must do some initialization and database calls, and I think I could reduce this by making a persistant tier, but there doesn't seem a good way to do this using php except when I would use sockets. Shared memory doesn't really seem like an option, because I would still need to include all the classes to manage it, and when I use shared memory, the memory would still be copied into the php memory + having a central manager seems like a good idea. I know I'm pretty vague in my requirements, but I think it should be enough to explain what kind of solution I´m looking for, because this seems like a big advantage of java over php, or am I mistaken? If you have any ideas, let me know :) grt, Evert Collab