system or global causeEvent

For questions and postings not covered by the other forums
ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

system or global causeEvent

Postby ConvertFromOldNGs » Fri Aug 07, 2009 1:22 pm

by Scott >> Tue, 19 Aug 2008 10:10:05 GMT

It best use system or global causeEvent? What disadvantage? What advantage? Or make no difference?

Await your comment.

ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

Re: system or global causeEvent

Postby ConvertFromOldNGs » Fri Aug 07, 2009 1:22 pm

by Murray Symon >> Tue, 19 Aug 2008 10:41:07 GMT

Your question is rather vague and broad in scope. Can you be
more specific on what you want to know, or what you are trying
to achieve?

You use causeEvent on an Object that has notifications subscribed.
So you need to consider causeEvent in relation to the notification strategy that is employed. You need to consider which objects
need to receive the notification - whether it is just a few, or
all objects in the system.

ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

Re: system or global causeEvent

Postby ConvertFromOldNGs » Fri Aug 07, 2009 1:22 pm

by Torrie Moore >> Tue, 19 Aug 2008 21:31:06 GMT

One thing to consider is whether you are using multiple schemas. Jade creates a new global object for each schema where there is only one system object. If you are running applications from multiple schemas that need to respond to the notification you might be better to use the system object.

Torrie

ConvertFromOldNGs
Posts: 5321
Joined: Wed Aug 05, 2009 5:19 pm

Re: system or global causeEvent

Postby ConvertFromOldNGs » Fri Aug 07, 2009 1:22 pm

by Scott >> Fri, 22 Aug 2008 9:24:10 GMT

Sorry, mean notification all users.

eg: Message say logoff for shutdown.

I will system.causeEvent so work multiple schemas.

Thanks your time.


Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 33 guests

cron