Event: DevMob 2010

Login or Register for Dates, Times and to Reply

 
Thread Tools Search this Thread
# 1  
Event: DevMob 2010

Register for Dev Mob 2010 - free London conference/barcamp giving developers interested in portable devices the opportunity to discuss their issues and find solutions.

If you would like to suggest or host a session (or just participate) on any kind of mobile development issue, please register at DevMob 2010 - Uniting mobile application developers in London

Event details:
3rd February 2010
10am-5pm
Science Museum, South Kensington, London
Registration is free and refreshments will be provided!

Plus: chance to win a netbook courtesy of ASUS (event sponsors)
Login or Register for Dates, Times and to Reply

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

dat_evd_post_se(3DAT)				     Direct Access Transport Library Functions				     dat_evd_post_se(3DAT)

NAME
dat_evd_post_se - post Software event to the Event Dispatcher event queue SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_evd_post_se( IN DAT_EVD_HANDLE evd_handle, IN const DAT_EVENT *event ) PARAMETERS
evd_handle Handle for an instance of the Event Dispatcher event A pointer to a Consumer created Software Event. DESCRIPTION
The dat_evd_post_se() function posts Software events to the Event Dispatcher event queue. This is analogous to event arrival on the Event Dispatcher software Event Stream. The event that the Consumer provides adheres to the event format as defined in <dat.h>. The first element in the event provides the type of the event (DAT_EVENT_TYPE_SOFTWARE); the rest provide the event-type-specific parameters. These parame- ters are opaque to a Provider. Allocation and release of the memory referenced by the event pointer in a software event are the Consumer's responsibility. There is no ordering between events from different Event Streams. All the synchronization issues between multiple Consumer contexts trying to post events to an Event Dispatcher instance simultaneously are left to a Consumer. If the event queue is full, the operation is completed unsuccessfully and returns DAT_QUEUE_FULL. The event is not queued. The queue over- flow condition does takes place and, therefore, the asynchronous Event Dispatcher is not effected. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The evd_handle parameter is invalid. DAT_INVALID_PARAMETER The event parameter is invalid. DAT_QUEUE_FULL The Event Dispatcher queue is full. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.10 16 Jul 2004 dat_evd_post_se(3DAT)

Featured Tech Videos