Saturday, October 30, 2021
All Mobile Gprs Settings
Thursday, December 24, 2009
All Mobile Gprs Settings
Airtel Live
Profile Neme: Live
Homepage: http://live.airtelworld.com
Username: blank
Password: blank
APN: airtelfun.com
Proxy and Server Adress or IP: 100.1.200.99
Port: 8080
Data bearer - GPRS or Packet Data.
Authentication: normal
Airtel GPRS or Mobile Office
Profile Neme: mo
Homepage: http://google.com
Username: blank
Password: blank
APN: airtelgprs.com
Proxy and Server Adress or IP: 202.56.231.117
Port: 8080
Data bearer - GPRS or Packet Data.
Authentication: normal
IDEA
Profile Neme:Idea
Homepage: http://wap.ideafresh.com
Username: blank
Password: blank
APN: imis
Proxy and Server Adress or IP: 10.4.42.45
Port: 8080
Data bearer - GPRS or Packet Data.
Authentication: normal
Smart SMARTWAP:
* Account name : SMARTWAP
* Access point name: SMARTWAP
* Home page: http://wap.rworld.co.in/gsm/index.wml
* Wapgateway proxy IP address: 97.253.29.199
* Port: 8080
Smart SMATRNET:
* Account name: SMARTNET
* Access point name: SMARTNET
* Home page: http://www.google.co.in
* Wapgateway proxy IP address: 97.253.29.199
* Port: 8080
Smart MMS:
* Account name: RTLMMS
* Access point name:MMS
* Homepage: http://10.114.0.5/mms/
* Wapgateway IP: 10.114.0.13
* Port: 9401
Vodafone live Settings:
Account Name - Vodafone Live
User Name - leave Blank
Password - leave Blank
Proxy - Enabled/yes
Access Point Name - portalnmms
Proxy - Enabled/yes.
Proxy and Server address - 010.010.001.100
Proxy and Server Port - 9401 or 8080
Homepage - http://live.vodafone.in
Authentication Type - Normal
BSNL gprs Settings:
Account Name - bsnlwap
Username - leave blank
Password - leave blank
Proxy - Enabled/yes
Homepage - http://wap.cellone.in
Proxy and Server address - 010.132.194.196
Proxy and Server Port - 8080
Acces Point Name - wapnorth.cellone.in
Data bearer - GPRS/ Packetdata
Authentication Type - Normal
Need Aircel GPRS/Internet free Setting for Chinese Mobile:
Using Internet through Mobile:
* Account name: Aircel Online
* Home page: http://myaircel.com
* Access point name: aircelwap
* Wapgateway IP: 172.17.83.69
* Port: 8080
*Username - leave blank
*Password - leave blank
Using Internet through Mobile:
* Account name: Aircel Online
* Home page: http://www.google.com
* Access point name: aircelweb
* Wapgateway IP: leave blank
* Port: leave blank
*Username - leave blank
*Password - leave blank
Spice
* Account name: Spice wap
* Home page: http://wap.spicetele.com
*Dial up number: 6830
* Wapgateway IP: 10.200.200.3
* Port: 8080
* Carrier type: Data GSM
*Username - +91 followed by users no.
*Password - spice
BPL
Account Name - BPL WAP
1. Username - leave blank
2. Password - leave blank
3. Proxy - Enabled/yes
4. Homepage - http://wap.mizone.bplmobile.com
5. Proxy and Server address - 10.0.0.10
6. Proxy and Server Port - 8080
7. Acces Point Name - mizone
8. Data bearer - GPRS/ Packetdata
9. Authentication Type - Normal
Tata Docomo
Account Name - Tata Docomo Divein
1. Username - leave blank
2. Password - leave blank
3. Proxy - Enabled/yes
4. Homepage - http://divein.tatadocomo.com
5. Proxy and Server address - 010.124.094.007
6. Proxy and Server Port - 8080
7. Acces Point Name - TATA.DOCOMO.DIVE.IN
8. Data bearer - GPRS/ Packetdata
9. Authentication Type - Normal
Tuesday, November 24, 2009
Important New Concepts in WPF
LISTING 3.1 A Simple About Dialog in XAML FIGURE 3.1 The rendered dialog from Listing 3.1.Logical and Visual Trees
Title="About WPF Unleashed" SizeToContent="WidthAndHeight"
Background="OrangeRed">
product.
FIGURE 3.2 The logical tree for Listing 3.1.
Not all logical tree nodes appear in the visual tree; only the elements that derive from System.Windows.Media.Visual or System.Windows.Media.Visual3D are included. Other elements (and simple string content, as in Listing 3.1) are not included because they don't have inherent rendering behavior of their own.
Figure 3.3 illustrates the default visual tree for Listing 3.1 when running on Windows Vista with the Aero theme. This diagram exposes some inner components of the UI that are currently invisible, such as the ListBox's two ScrollBars and each Label's Border. It also reveals that Button, Label, and ListBoxItem are all comprised of the same elements, except Button uses an obscure ButtonChrome element rather than a Border. (These controls have other visual differences as the result of different default property values. For example, Button has a default Margin of 10 on all sides whereas Label has a default Margin of 0.)
TIP XamlPad contains a button in its toolbar that reveals the visual tree (and property values) for any XAML that it renders. It doesn't work when hosting a Window (as in Figure 3.1), but you can change the Window element to a Page (and remove the SizeToContent property) to take advantage of this functionality.
Because they enable you to peer inside the deep composition of WPF elements, visual trees can be surprisingly complex. Fortunately, although visual trees are an essential part of the WPF infrastructure, you often don't need to worry about them unless you're radically restyling controls (covered in Chapter 10, "Styles, Templates, Skins, and Themes") or doing low-level drawing (covered in Chapter 11, "2D Graphics"). Writing code that depends on a specific visual tree for a Button, for example, breaks one of WPF's core tenets—the separation of look and logic. When someone restyles a control like Button using the techniques described in Chapter 10, its entire visual tree is replaced with something that could be completely different.
WCF-Basic Concept
Basic WCF Concept and Terminologies
Windows Communication Foundation was official released with .NET 3.0 a couple of months ago. For those people who're doing connected, distributed systems or are in any way interested in communication aspects of systems, this ought to be a God-send. WCF basically rolled all the different Microsoft messaging formats into one, making it extremely easy to architect the communication layer of simple to complex applications. This tutorial aims to explain the basic concepts behind the common terminology used in WCF development and design.
Below is a quick overview of the WCF architecture
WCF Programs
WCF programs are basically divided into 3 different types of programs. They are common known as
- Clients
Clients are program that consumes the services, they are normally the ones that initiate the messenging to the service. Depending on the designed architecture of your application, it is possible that a service behaves as a client as well. - Services
Services are the programs that offers the services to the consumers. They are the ones that react and process the messages, similar to the backend of the application. They can be viewed as the equivalence of web services in .Net 2.0.
All services have to have endpoints specified in order to work. A good way to remember proper endpoint configurations is ABC. A being Address, B being Binding and C being Contracts.- Address
Address are the expose points of services. Services have to tell the world that where they are via addresses. - Bindings
Bindings will describe to the world on how they will communicate with the world. They contain information such as transport way, how they are encoded, are they reliable etc. - Contracts are of (but not necessary all have to be present) 3 different kinds
- Service Contract
Describes what the service does. - Data Contract
Define custom messaging structure. - Message Contract
Define the message format that is passed between services.
- Service Contract
- Address
- Intermediaries
Intermediaries are programs that act as "middle-man", their basic roles can be similar to providing a firewall, routing, gateway etc. They are commonly invisible to the client and services.
Messages
All services and clients communicate via messages, which are made up of one body, and one or more header. All WCF messages are XML formatted and transport neutral. In other words, you can specify different forms of transport (HTTP, MSMQ, Named Pipes etc) for different messages. Within each application, you can specify different messaging transport depending on the communication needs of the system. Basically, messages can be divided into
- Simplex
One way messaging. Simplex in short means "fire and forget" - Duplex
Asynchronous two-way messaging. In short this means that once fired, the application will carry on doing its own thing. Upon the return results, it will then handle it. - Request Reply
Synchronous 2 way messaging. This is the common communicate method whereby you'll fire a request, and wait for the response before continuing.
Channels
Before a client and service can talk to each other, they have to go through a channel. Imagine a channel as a pipe, with one end being the input message and the other end with the results of the message. There're different channels that can be stacked onto each other, they are commonly known as Channel Stacks. They can be of these different types:
- Reliable Sessions
- TCP Transport
- Binary Message Encoder
- Windows Security
- Request Reply
The way in which messages are sent through the pipe (Channel) is known as a Transport and they way at which they are encoded are known as Encodings. Transport can be made up of the following:
- HTTP
- TCP
- MSMQ
- Named Pipes
I hope this quick overview will be helpful for you.
Friday, October 16, 2009
Tuesday, August 4, 2009
After Triiger Note
SQL Server 2005 Audit Log Using Triggers
Once a database row has changed how do you retrieve the original data? There are many ways to do this, but for the application I'm working on I decided to use triggers.
Creating triggers in SQL Server 2005 is fairly easy. When you create a trigger you are presented with a template that you can modify to meet your needs. In the template there is a line that reads: SET NOCOUNT ON; with the explanation that tells you why: SET NOCOUNT ON added to prevent extra result sets from interfering with SELECT statements. it looks like this:
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON ;
When using triggers to update another table you need to leave this statement in or you will not be able to update your audit table, from triggers, and you will get the following error message:
The row value(s) updated or deleted either do not make the row unique or they alter multiple rows.
Here are the SQL Statements required to create a table, an audit table, and the triggers :
USE [db]
GO
CREATE TABLE [dbo].[table1](
[table1_id] [int] IDENTITY(1,1) NOT NULL,
[table1_date] [datetime] NULL CONSTRAINT [DF_table1_table1_date] DEFAULT (getdate()),
[table1_data] [varchar](50) NULL,
CONSTRAINT [PK_table1] PRIMARY KEY CLUSTERED
(
[table1_id] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[table1audit](
[table1audit_id] [int] IDENTITY(1,1) NOT NULL,
[table1audit_table1id] [int] NULL,
[table1audit_date] [datetime] NULL,
[table1audit_data] [varchar](50) NULL,
[table1audit_type] [varchar](50) NULL,
[table1audit_performed] [datetime] NULL CONSTRAINT [DF_table1audit_table1audit_date] DEFAULT (getdate()),
CONSTRAINT [PK_table1audit] PRIMARY KEY CLUSTERED
(
[table1audit_id] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
CREATE TRIGGER dbo.table1auditdelete
ON dbo.table1
AFTER DELETE
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
INSERT INTO table1audit(table1audit_table1id, table1audit_date, table1audit_data, table1audit_type)
SELECT table1_id, table1_date, table1_data, 'DELETE'
FROM deleted
END
GO
CREATE TRIGGER dbo.table1auditupdate
ON dbo.table1
AFTER UPDATE
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
INSERT INTO table1audit(table1audit_table1id, table1audit_date, table1audit_data, table1audit_type)
SELECT table1_id, table1_date, table1_data, 'UPDATE'
FROM inserted
END
GO
CREATE TRIGGER dbo.table1auditinsert
ON dbo.table1
AFTER INSERT
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
INSERT INTO table1audit(table1audit_table1id, table1audit_date, table1audit_data, table1audit_type)
SELECT table1_id, table1_date, table1_data, 'INSERT'
FROM inserted
END
GO
