RE: [Phpgroupware-developers] shared memory (was documentation)

[sigurdne]

>===== Original Message From address@hidden, 
address@hidden =====
>http://us2.php.net/manual/en/ref.shmop.php
>as far as I can tell, it spans not only session, but programs.  As
>long as you know the key you can read the data from anything.  It
>doesn't survive a reboot, but that's it.
>
>it's not a guarentee to be availble, so it's one of those things were
>we'd have to detect it and use it only if available, thus adding more
>conditionals to the code.  Probably worth doing anyway.
>
>Since it uses standard shared memory through a C api, memory leaks
>aren't likely as it's a mature interface, and this isn't memory that
>will change much, which is the point.
>
>

How can one assure that the shared memory block is deleted (shmop_delete) if 
the user just quits without logging off ? (the memory consumption would pile 
up?)

Sigurd


>On Wed, 17 Nov 2004 22:25:17 +0100, Sigurd Nes <address@hidden> wrote:
>> Kai Hofmann wrote:
>> > Hi Sigurd,
>> >
>> >
>> >>Some time ago there was a discussion on how to document the
>> >>code - I can't
>> >>really remember if there was a conclusion.
>> >>Is the Pear version of PhpDocumentor a good alternative? (or
>> >>HeaderDoc? - or
>> >>the wiki?).
>> >
>> >
>> > For API (inline) documentation phpdocumentator (http://www.phpdoc.org/)
>> > should be used.
>> > For other kind of documentation, like install docs, how tos etc.
>> > the phpgw wiki is the right place.
>> >
>> > For the phpdoc's I have already written a script (that has not yet
>> > applied), which can extract these kind of docs every night from cvs.
>> >
>> >
>> >>Is performance affected by inline documentation when using a
>> >>precompiler as  mmcache?
>> >
>> >
>> > mmcache will always speed up performance, because it precompiles php
>> > scripts written in ascii to an internal presentation that is faster,
>> > because it does not need again scanning and parsing.
>> > Think of it like java vs. byte-code.
>> >
>> > I have not found that inline docs (comments) or tabs vs. spaces
>> > will influence the performance of php in a way you can feel or
>> > even measure.
>> > Nearly all performance problems come from bad code/architecture that does
>> > things like
>> > reading the same value for every http request from the database (instead 
of
>> > caching it via shared memory).
>> >
>> The remark on shared memory is very interesting - I can't see that shmop
>> is used at all in phpgroupware.
>>
>> Will the shared memory live trough a session - or is it only sustainable
>> within the transaction?
>>
>> How about memory leaks?
>>
>> > On the other hand there are toold with which you can strip comments from
>> > the code for your runtime environment. So you should not worry about
>> > performance when using inline docs.
>> >
>> > Greetings
>> >
>> >    Kai/PowerStat
>> >
>> >
>> Thanks for the feedback - I go for phpDocumentor (v1.3.0RC3)
>>
>> Sigurd
>>
>> _______________________________________________
>> Phpgroupware-developers mailing list
>> address@hidden
>> http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
>>
>>
>
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://lists.gnu.org/mailman/listinfo/phpgroupware-developers