Predicting Future Outcomes by an Event Prediction Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Predicting Future Outcomes by an Event Prediction Community
# 1  
Old 06-21-2009
Predicting Future Outcomes by an Event Prediction Community

Tim Bass
06-21-2009 04:33 PM


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

change the year in the event prediction market

Can you change the year in the event prediction market Facebook Stock Will Be Over $70 a Share By the End of 2102? (Closes for placing Bits on 09-30-12 - 10:30 PM) (8 Replies)
Discussion started by: itkamaraj
8 Replies

2. Post Here to Contact Site Administrators and Moderators

Event Prediction - Euro 2012

Please add this new "event". (10 Replies)
Discussion started by: ni2
10 Replies

3. Post Here to Contact Site Administrators and Moderators

Event Prediction - New Sports Events

Hi, Some sports predictions suggestions. Although the Celtics are still playing the Heat. Just being optimistic that they will win. Otherwise, please change to Heat. (9 Replies)
Discussion started by: ni2
9 Replies

4. What is on Your Mind?

Predict Future Outcomes in Our Event Prediction Market

Folks love to predict the future, so we have enabled predicting the future for members. So, please enjoy placing your Forum Bits predicting future outcomes in our new Event Prediction Market. Current events you can predict include science, technology, M&A and other global events: Oracle... (0 Replies)
Discussion started by: Neo
0 Replies
Login or Register to Ask a Question
EVENT(3)								 1								  EVENT(3)

The Event class

INTRODUCTION
Event class represents and event firing on a file descriptor being ready to read from or write to; a file descriptor becoming ready to read from or write to(edge-triggered I/O only); a timeout expiring; a signal occuring; a user-triggered event. Every event is associated with EventBase . However, event will never fire until it is added (via Event::add ). An added event remains in pending state until the registered event occurs, thus turning it to active state. To handle events user may register a callback which is called when event becomes active. If event is configured persistent , it remains pending. If it is not persistent, it stops being pending when it's callback runs. Event::del method deletes event, thus making it non-pending. By means of Event::add method it could be added again. CLASS SYNOPSIS
Event final Event Constants o const integer$Event::ET32 o const integer$Event::PERSIST16 o const integer$Event::READ2 o const integer$Event::WRITE4 o const integer$Event::SIGNAL8 o const integer$Event::TIMEOUT1 Properties o publicreadonly bool$pending Methods o public bool Event::add ([double $timeout]) o public bool Event::addSignal ([double $timeout]) o public bool Event::addTimer ([double $timeout]) o public Event::__construct (EventBase $base, mixed $fd, int $what, callable $cb, [mixed $arg = NULL]) o public bool Event::del (void ) o public bool Event::delSignal (void ) o public bool Event::delTimer (void ) o public void Event::free (void ) o publicstatic array Event::getSupportedMethods (void ) o public bool Event::pending (int $flags) o public bool Event::set (EventBase $base, mixed $fd, [int $what], [callable $cb], [mixed $arg]) o public bool Event::setPriority (int $priority) o public bool Event::setTimer (EventBase $base, callable $cb, [mixed $arg]) o publicstatic Event Event::signal (EventBase $base, int $signum, callable $cb, [mixed $arg]) o publicstatic Event Event::timer (EventBase $base, callable $cb, [mixed $arg]) PROPERTIES
o $pending - Whether event is pending. See About event persistence . PREDEFINED CONSTANTS
o Event::ET - Indicates that the event should be edge-triggered, if the underlying event base backend supports edge-triggered events. This affects the semantics of Event::READ and Event::WRITE . o Event::PERSIST - Indicates that the event is persistent. See About event persistence . o Event::READ - This flag indicates an event that becomes active when the provided file descriptor(usually a stream resource, or socket) is ready for reading. o Event::WRITE - This flag indicates an event that becomes active when the provided file descriptor(usually a stream resource, or socket) is ready for reading. o Event::SIGNAL - Used to implement signal detection. See "Constructing signal events" below. o Event::TIMEOUT - This flag indicates an event that becomes active after a timeout elapses. The Event::TIMEOUT flag is ignored when constructing an event: one can either set a timeout when event is added , or not. It is set in the $what argument to the callback function when a timeout has occurred. PHP Documentation Group EVENT(3)