Technology Questions

- Notification messages to the user from an Android enabled device can be displayed using Intents.

- There are two types of Intents - Explicit Intent, Implicit Intent.

Implicit Intent:

- In case of Implicit Intent, an intent is just declared. 

- It is for the platform to find an activity that can respond to it.

- Since the target component is not declared, it is used for activating components of other applications.

Explicit Intent

- Explicit intent specifies the particular activity that should respond to the intent. 

- They are used for application internal messages.

An abstract class is defined with the keyword abstract Eg:
public abstract class MyClass { }

Because every component needs to indicate which intents they can respond to, intent filters are used to filter out intents that these components are willing to receive. One or more intent filters are possible, depending on the services and activities that is going to make use of it.

Use the buffer cache advisory over a given workload and then query the v$db_cache_advice table. If a change was necessary then I would use the alter system set db_cache_size command.

Specify android id, layout height and width as depicted in the following example.

<ListView android:id="@+id/ListView01" android:layout_height="wrap_content" android:layout_width="fill_parent"></ListView>

The create method in a stateless bean cannot have arguments, and can only have a single method called create(). While create in Stateful bean can have arguments and could be any method starting with create string eg. create(arg1, arg2, ...). Although it is not compiler checked but in stateless bean the ejb Passivate() and ejb Active() methods has to be empty as these functions are never called by EJB container. As conceptually in stateful session bean we might need to store the clients information hence arguments in createare necessary. While in stateless bean we don't hence no arguments are necessary. It's intutive isn't intutive isn't. I my life I haven't seen such a futuristic server programming tool as EJB.

It is similar to MacOS X architecture

It acts as an intermediary between the iPhone and iPod hardware an the appearing applications on the screen

The user created applications never interact directly with the appropriate drivers, which protects the user applications from changes to the hardware. 

Yes, it is possible to do that, such as when you want to create a background behavior for a particular activity. You can do this by using add(Fragment,string) method to add a fragment from the activity.