Question 1

How do I handle WebSockets with SimpleBridge on a server like Inets?

Accepted Answer

Define handler functions like ws_init and ws_message in your module; SimpleBridge provides a uniform WebSocket layer even on servers without native support, as shown in the sample code. Configure via simple_bridge.config for the backend.

Question 2

What's the difference between SimpleBridge and EWGI?

Accepted Answer

SimpleBridge focuses on a simpler interface with built-in WebSocket and file upload support, while EWGI emphasizes middleware components. SimpleBridge is easier to extend for new servers but lacks middleware flexibility.

Question 3

How to migrate from SimpleBridge 1.x to 2.x?

Accepted Answer

Update deprecated functions (e.g., use sbw:set_status_code instead of status_code) and adjust for changes in return types for headers and parameters. The README has a detailed migration section with examples.

Question 4

Does SimpleBridge support HTTPS?

Accepted Answer

Yes, through the underlying servers; configure server-specific HTTPS settings in the simple_bridge.config file, as SimpleBridge abstracts the protocol handling uniformly.

Question 5

What are the performance implications of using SimpleBridge?

Accepted Answer

While it uses the server's optimized methods for static files, the abstraction layer may add slight overhead for high-throughput applications. Direct server coding might be more efficient for performance-critical use cases.

Question 6

Can I use SimpleBridge with only Cowboy, or is it overkill?

Accepted Answer

You can use it with only Cowboy, but if cross-server portability isn't needed, the abstraction adds unnecessary complexity; it's best suited for multi-server environments or framework development.

simple_bridge

What is simple_bridge?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions