HAproxy features [closed] - haproxy

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
will anyone tell me how HAproxy actually works.i searched alot but i want a simple and easy explaination about overall HAproxy.

HAProxy is commonly used for load balancing, ie. you have a number of web servers and you wanted to distribute requests between them and seamlessly handle things like when a server goes down.
Configure HAProxy in front, and it'll forward connections (hence, it is a proxy) in such a way that connections will be spread between servers.
In practice, there are tons of configuration and complexities to fit specific needs. I'd start by taking a look at the docs. Here is an example of HAProxy being used as, well, a proxy to forward http connections. If you add more servers it'll load balance between those servers. There are more examples spread out through the documentation.

It's not very clear what you're looking for. Haproxy does many different things so there's no single response. I suggest you take a look at the architecture manual. It's quite old but will give you some concrete examples of what you can do with it.

Related

PJSIP and FreeRTOS [closed]

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I have been investigating the use of the PJSIP SIP stack on a small micro-controller such as the PIC32 MCU and I've come to realise that it may just be possible. I want only the absolute minimal SIP functionality so I just might be able to fit PJSIP on a small MCU. Of course, it's a VERY ambitious project but I'm gonna give it a try anyway. I just can't seem to wrap my mind around the right operating system for use so I'm gonna spend a good couple weeks on this subject. I'm gonna take a look at FreeRTOS. Any thoughts on the compatibility of FreeRTOS with something like PJSIP?
I think the project site itself answers your question:
On portability
On Size
The memory resources suggested would be at the upper end for most on-chip memory. The RTOS's listed are all significantly more fully featured than FreeRTOS which provides little more than thread scheduling, timer services, synchronisation and IPC. You'd need to understand what OS services it assumes. Presumably it uses the platform's network stack? FreeRTOS has no network stack - you'd have to provide that too - more resources again.

Client server ios Application [closed]

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
Whats the best way to do an application where an phone is the server and the others phones are the clients. The clients will do requests to the server and the server will respond..Requests maybe to the server sends the real time audio that they are capturing..Whats the best way to do this in ios? Using UDP Multicast? Or an TCP Socket per client?
Using UDP multicast will cast your messages to all devices in your network (hence the name). It also does not guarantee delivery and it does not garauntee delivery order (FOFI) either. In most situations, UDP isn't really a good idea.
TCP is a really great alternative, it's easy to use, and it does garuantee all those things and there are many frameworks or C libraries out there that can help you a lot.
Personally, I'ld recommend using libuv and attaching the uv runloop to NSRunloop, but you can use AsyncSocket too, if you'ld rather like to stick to Objective-C.

the best office chat? [closed]

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
It would be nice to be able to share some code snippets / random stuff with colleagues (15 people).
I was thinking to set-up an office chat, and I wonder if you have any system to recommend.
I can use a dedicated server for that.
Is IRC the way to go? or are there different technologies?
Openfire server and Pidgin client lets you chat and send files.
IRC is probably a really cheap way of doing this. Pretty much any client can XDCC and send files to other users like, XChat, chatzilla, pidgin, weechat, mIRC, etc. There's also a free server software that you can setup, like lightIRC, Unreal, Pjirc, Bahamut, etc.
But I think what you really want is project collaboration software. There's a lot of options here, some cost money and some are hosted as a service.

How do you make a REST API and upload files in Meteor [closed]

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
What is about a REST API? Is there already a way to define some routes and logic for the API on the server? I think this is nowadays a must-have feature.
And the same with File-Uploads. With express framework I can already handle uploads really easy. How do I do this in Meteor? The documentation says nothing about it. So are there some plans to implement it? Or is there already a way?
As far as REST goes: Meteor doesn't yet provide a supported API for serving HTTP from your application. This is intentional: in the not-too-distant future, your application server is likely to not be just a single process directly serving end users, but an arbitrarily parallelizable service behind a proxy tier. So we'll need to provide a supported API for responded to HTTP requests (for example, REST) that continues to work in such a setting.
If you really need to accept direct HTTP REST requests now, take a peek at how packages/accounts-oauth-helper/oauth_server.js uses __meteor_bootstrap__.app to hook into the Connect middleware framework. This will work for now, but we don't promise that Meteor will always be powered by Connect :)
Supporting REST endpoints is on Meteor's roadmap.
So is file uploads (that's what binary type refers to).
I have been using
https://github.com/crazytoad/meteor-collectionapi#readme
Which will create rest endpoints on your collections right out of the box. You can use meteorite to install it.

What type/category of web application(s) need to be distributed? [closed]

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
Are websites falling in social network category like LinkedIn, StackOverflow, Facebook, distributed applications ?
Does distributed in the web application's context just means running on multiple web servers ? What are the most important design differences in distributed & non-distributed web applications ?
Does distributed in the web application's context just means running on multiple web servers?
It depends what you mean by "multiple web servers." If you mean multiple HTTP servers, multiple proxies, multiple databases, multiple caching mechanisms (memcached, Redis, etc), load-balancing, then yeah, sure.
What are the most important design differences in distributed & non-distributed web applications ?
There's no way to answer this without more information (what kind of web application are you talking about here?). For one, you may be using different technologies, you're going to be doing much more rigorous unit testing, you'll (hopefully) write your code with fault-tolerance in mind.
Edit:
I believe that a website should be designed with expansion in mind. Again, it's hard to deal in abstractions but I'm assuming a start-up here. You can make a site (for cheap) using "crappy" technologies (lets say PHP - flame suit on) that are harder to scale than, say, Java. You can use a "simple" SQL solution or you can try to combine pgSQL with something like memcached or Redis so when (and if) your company and web presence expand, you won't have to redesign your entire subsystem.
I made this mistake with my first start-up and I think there's some value in thinking ahead. Conversely, you don't want to focus PURELY on "cool" technologies ("ooh, lets use memcached with a Redis cluster and Cassandra"), you also want to focus on the content.