openinteract-dev

[Openinteract-dev] Need input on a new system

[Andrew H. <hu...@ll...>]

Hello,

   I'm probably going to end up writing a simple collaborative document 
review system, and want to use OI for the user accounts and security 
functionality.  I'm wondering if I should use OI2 or OI1 for this.  I 
expect to strip the system down pretty far, so that there are no extra 
packages when this goes live.  I seriously doubt it will see more than 1 
req/sec of traffic.  The document that people will comment on will be 
rather large though, about 100 pages, with upwards of a few thousand 
comments at its peak.  Time frame to live is about 3 weeks.

   What do you think?  Thanks for the input...

-Andrew

Re: [Openinteract-dev] Need input on a new system

[Andreas N. <an...@kl...>]

Hi Andrew,

if you need your system to run in production within the next couple of
months, then use OI 1. Try keeping the application logic out of the
handler code, for example by using the hooks in SPOPS. Doing this will
minimize changes when going to OI2.

hope that helps,

Andreas
On Fri, 2003-07-18 at 23:57, Andrew Hurst wrote:
> Hello,
> 
>    I'm probably going to end up writing a simple collaborative document 
> review system, and want to use OI for the user accounts and security 
> functionality.  I'm wondering if I should use OI2 or OI1 for this.  I 
> expect to strip the system down pretty far, so that there are no extra 
> packages when this goes live.  I seriously doubt it will see more than 1 
> req/sec of traffic.  The document that people will comment on will be 
> rather large though, about 100 pages, with upwards of a few thousand 
> comments at its peak.  Time frame to live is about 3 weeks.
> 
>    What do you think?  Thanks for the input...
> 
> -Andrew
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> openinteract-dev mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openinteract-dev

Re: [Openinteract-dev] Need input on a new system

[Chris W. <ch...@cw...>]

Andrew Hurst wrote:
>   I'm probably going to end up writing a simple collaborative document 
> review system, and want to use OI for the user accounts and security 
> functionality.  I'm wondering if I should use OI2 or OI1 for this.  I 
> expect to strip the system down pretty far, so that there are no extra 
> packages when this goes live.  I seriously doubt it will see more than 1 
> req/sec of traffic.  The document that people will comment on will be 
> rather large though, about 100 pages, with upwards of a few thousand 
> comments at its peak.  Time frame to live is about 3 weeks.
> 
>   What do you think?  Thanks for the input...

For purely selfish reasons I'd like you to use OI2 so you can let me 
know what problems you have with it :-) But if you're implementing 
it in three weeks then I'd probably say OI 1.x, agreeing entirely 
with the comments Andreas put forth.

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.

Re: [Openinteract-dev] Need input on a new system

[Andrew H. <hu...@ll...>]

At 12:12 AM 7/21/2003 -0400, Chris Winters wrote:
>Andrew Hurst wrote:
>>...
>
>For purely selfish reasons I'd like you to use OI2 so you can let me know 
>what problems you have with it :-) But if you're implementing it in three 
>weeks then I'd probably say OI 1.x, agreeing entirely with the comments 
>Andreas put forth.

Sounds good.  Now on to actual implementation details and questions, in the 
interest of doing this in the "OpenInteract" way :)  Its possible we could 
be able to release this code back. (Well, maybe.  After all the hubub about 
whether we can get code back to the community easy from here, my boss comes 
in with this job and says "hey, we need this done quick, you can do it 
however you like.  And we can probably open source it as well")  But we 
can't make any promises until its actually released back to the community, 
of course ;)

The way that I'm probably going to implement this is with a generic 'story' 
type mechanism.  I think of one big document that people can comment on 
much as a multi-part story on a site like kuro5hin or slashdot.  So this 
would probably require a few new pages, to post the full text and parse for 
comment sections (the current code looks for certain html tags and puts 
comments when it finds them), a page to show it all at once with comment 
links, and the ability to show only one section at a time with comments for 
that section.

I seem to recall you (Chris) talking about the comment module being able to 
attach to any object in the system, which is why I thought this way might 
work well.  Is that the case?

I will also need to add some features to the comment mechanism like topics 
for the comments, ability for a logged in user to only see their own 
comments, and a display of only comments in topics a person has permission for.

Thanks for the input!
-Andrew




>Chris
>
>--
>Chris Winters (ch...@cw...)
>Building enterprise-capable snack solutions since 1988.
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
>same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
>_______________________________________________
>openinteract-dev mailing list
>ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openinteract-dev

Re: [Openinteract-dev] Need input on a new system

[Chris W. <ch...@cw...>]

Andrew Hurst wrote:
 > ...
> quick, you can do it however you like.  And we can probably open source 
> it as well")  But we can't make any promises until its actually released 
> back to the community, of course ;)

It would be great, but I know that uphill battle that can be...

> ...
> I seem to recall you (Chris) talking about the comment module being able 
> to attach to any object in the system, which is why I thought this way 
> might work well.  Is that the case?

Correct. It really just treats the object as a class + ID pair and 
then uses that as an organizational point. Kind of like the ID for a 
thread beginning, but more useful so you can find all the comments 
for an object with a component call:

[% OI.comp( 'show_comment_by_object', object = news ) %]

For instance, I have the preceding on all 'news' objects on my 
website. And a few 'page' objects I have it as well, such as some 
random thoughts about matrix stuff. That call looks like:

[% OI.comp( 'show_comment_by_object', object = page ) %]

You can, of course, get all this data programmatically as well.

This way of working has always been part of OI but rarely explicit. 
With OI2 I think I'll include the 'comments' and 'object_link' 
packages which take advantage of this functionality. The 
'object_link' package just adds a layer of topics so you can link 
any two arbitrary objects (pages, news items, recipes, movie 
reviews, external links, etc.) by a topic and get a useful 'Related 
Items' listing of them.

> I will also need to add some features to the comment mechanism like 
> topics for the comments, ability for a logged in user to only see their 
> own comments, and a display of only comments in topics a person has 
> permission for.

Cool!

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.