Simple Replication

Greetings,

I am building a system that requires a small database to be replicated.

The DB is made up of a few tables that do not change much, primarily by user-input or triggers on those tables, and one constantly growing table for incoming messages with rows constantly being added to it.

We require having two systems (System=Hardware&OS/SQLDB/Application) running in parallel where one could act as a failover to the primary system. Both systems would be run in the same site and have a direct network link.

My goal is to have both systems maintain identical databases and to be able to "re-synchronize their data after a failure in some recovery state.

I am looking at:

1. SQL Server Replication Methods (Publishers/Subscribers)
A possible scenario i need to support:
ServerA: primary server acts as publisher
ServerB: secondary failover server acts as subscriber
ServerA: Fails!
ServerB: Assumes role of primary server (i.e Publisher)
ServerA: recovers later, becomes subscriber to ServerB(secondary)

Q: Can Roles Be Switched or A server be a subscriber and
a publisher at the same time?

2. Use ServiceBroker Queues and Have Each server SEND a message
to the other server whenever it gets incoming data?

3. Use Transact-SQL in ServerA to write data to ServerA
and ServerB and vice versa.

4. Not worth replication, just have the application write data
to both servers in two seperate requests.

Which is the preferred way to accomplish this?

Thanks,
-ali