ezcollaboration feature -- any kind of doc available ?

Author Message

Volker Lenz

Thursday 13 February 2003 3:58:40 am

ezp3-rc2 includes some collaboration functionality. However, I can't find any description on what this is and how to make it work. Can anybody provide a hint on where to look ?

Regards

Volker

Volker Lenz

Thursday 13 February 2003 4:50:00 am

> ezp3-rc2 includes some collaboration functionality. However,
> I can't find any description on what this is and how to make
> it work. Can anybody provide a hint on where to look ?
>
> Regards
>
> Volker

I guess this collaboration feature is designed to become the foundation for things like forums etc. If so, I would really appreciate this. In the moment, forums with possibly thousands of messages are treated as ordinary content objects hanging around in the content node tree together with articles etc. So it's simply a question of time when your article-view-performance decreases due to a pollution of the node-tree with myriads of temporary forum messages. Is this consideration behind the introduction of "collaboration" as a new kernel module?

Jan Borsodi

Monday 17 February 2003 6:34:10 am

> > ezp3-rc2 includes some collaboration functionality.
> However,
> > I can't find any description on what this is and how to
> make
> > it work. Can anybody provide a hint on where to look ?

There's not much documentation now for this system, it's primarily been created for approval events for now but will be expanded in the future with documentation.

> I guess this collaboration feature is designed to become the
> foundation for things like forums etc. If so, I would really
> appreciate this. In the moment, forums with possibly
> thousands of messages are treated as ordinary content
> objects hanging around in the content node tree together
> with articles etc. So it's simply a question of time when
> your article-view-performance decreases due to a pollution
> of the node-tree with myriads of temporary forum messages.
> Is this consideration behind the introduction of
> "collaboration" as a new kernel module?

The reason for the collaboration system was to replace the current task system which had a unsatisying design. Also the collaboration system will embrace a larger set of functionality than just tasks and approvals. The new system allows the specific item handlers to do mostly whatever they want to do.

The main idea of the collaboration system is to link different users together on specific items, it can be used to give out tasks, discuss items, send messages, approval.
The difference from normal content objects is that collaboration only works between a given set of selected users, while content objects are for anyone to see and use (if policy allows it).
A private forum is possible with the collaboration system and is good idea for private discussions on items, however normal forums don't fit into it unless you add invitation support.

The closest analogy is your email client, you receive incoming items (mails) that you categorize personally.

We've worked a lot with the content object tree structure to ensure that it can scale to lots of objects and we will continue with this for future releases.
eZ publish is already used on a site with thousands of objects and it should not be a problem with thousands of forum messages.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Volker Lenz

Tuesday 18 February 2003 3:00:13 am

> > > ezp3-rc2 includes some collaboration functionality.
> > However,
> > > I can't find any description on what this is and how
> to
> > make
> > > it work. Can anybody provide a hint on where to look ?
>
> There's not much documentation now for this system, it's
> primarily been created for approval events for now but will
> be expanded in the future with documentation.
>
> > I guess this collaboration feature is designed to become
> the
> > foundation for things like forums etc. If so, I would
> really
> > appreciate this. In the moment, forums with possibly
> > thousands of messages are treated as ordinary content
> > objects hanging around in the content node tree together
> > with articles etc. So it's simply a question of time
> when
> > your article-view-performance decreases due to a
> pollution
> > of the node-tree with myriads of temporary forum
> messages.
> > Is this consideration behind the introduction of
> > "collaboration" as a new kernel module?
>
> The reason for the collaboration system was to replace the
> current task system which had a unsatisying design. Also the
> collaboration system will embrace a larger set of
> functionality than just tasks and approvals. The new system
> allows the specific item handlers to do mostly whatever they
> want to do.
>
> The main idea of the collaboration system is to link
> different users together on specific items, it can be used
> to give out tasks, discuss items, send messages, approval.
> The difference from normal content objects is that
> collaboration only works between a given set of selected
> users, while content objects are for anyone to see and use
> (if policy allows it).
> A private forum is possible with the collaboration system
> and is good idea for private discussions on items, however
> normal forums don't fit into it unless you add invitation
> support.
>
> The closest analogy is your email client, you receive
> incoming items (mails) that you categorize personally.
>
> We've worked a lot with the content object tree structure to
> ensure that it can scale to lots of objects and we will
> continue with this for future releases.
> eZ publish is already used on a site with thousands of
> objects and it should not be a problem with thousands of
> forum messages.

Thank you very much for this detailed explanation. Now I think I am going to trust the concept of the content node tree again.

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 30 2025 21:38:14
Script start
Timing: Jan 30 2025 21:38:14
Module start 'layout'
Timing: Jan 30 2025 21:38:14
Module start 'content'
Timing: Jan 30 2025 21:38:14
Module end 'content'
Timing: Jan 30 2025 21:38:14
Script end

Main resources:

Total runtime0.0229 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0050 588.3828151.2422
Module start 'layout' 0.00510.0039 739.6250220.7500
Module start 'content' 0.00900.0123 960.37501,005.8672
Module end 'content' 0.02130.0016 1,966.242237.9922
Script end 0.0229  2,004.2344 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002711.6000140.0002
Check MTime0.00114.9618140.0001
Mysql Total
Database connection0.00062.778810.0006
Mysqli_queries0.002812.367530.0009
Looping result0.00000.047810.0000
Template Total0.00115.010.0011
Template load0.00093.878110.0009
Template processing0.00031.095110.0003
Override
Cache load0.00062.787210.0006
General
dbfile0.00020.958980.0000
String conversion0.00000.031240.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs