Deprecated - Performance and scalability

Hi All.

I want to do this when I search something: that the search results come inside a view [views module], a table view, always the same view... by default, the results are shown as a teaser list, any help?

Other question:
How I do that the empty tags (of free tagging) deletes automatically if its don't have content or nodes asociated...?

Another question:
Is possible to automatic create a table view [views] for a new tag that is created? or, that when I list a category, it shows inside a view (like the question 1)?

Thanks,
Alejandro.

Hi there,

Is it really true that Drupal will cripple with 50 logged in users
on a dedicated box with 1Gb Ram?..

50 Users, many forums and communities have thousands of logged in
users, how many servers would a site with 1000 logged in users require?

We are evaluating the CMS for us, but judging by the extremely small
number of logged in users on a dedicated, drupal aint that appealing anymore.

Hello all,

I recently took a look at the file size for some transfers from various sites including Drupal.org and I noticed that many web sites compress text files (scripts, html, etc) before they transmit it. This is very interesting.

I noticed that Drupal was able to compress an 88Kb transfer down to about 18Kb. Nice. What I am wondering is how that is done...

Is that some sort of server side utility? If so what are some of the ones available that would work with Drupal?

Does the actual compression slow down the servers and if so to what extent?

I wanna user Ajax form builder modules but i m unable to download JSON.zip
http://sandbox.jodhpuriguy.com/files/JSON.zip
which is required to use this module and mentioned in Form builder module.
Can anyone send me these files.

Issue:
After browsing as anonymous and then logging in, the cached pages would still be served (thus showing one as not logged in).

I've spent hours researching this, focusing mainly on boostrap.inc. The issue was with Apache and the mod_expires-module.

I realize this could be Apache version specific, so this problem does not necessarily affect everyone. I've read enough about this problem in Drupal Forum (the issue, no solution) to know I'm not the only one who has been experiencing this.

What I did:

in .htaccess:

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
  # Enable expirations.
  ExpiresActive On
  # Cache all files for 2 weeks after access (A).
  ExpiresDefault A1209600
  # Do not cache dynamically generated pages.
  ExpiresByType text/html A1
</IfModule>

Directly after the line starting with "ExpiresByType" I added the following:


# Set up 2 Hour caching on commonly updated files

ExpiresDefault A7200


# Force no caching for dynamic files

ExpiresActive Off

/code>

First I change the default for some file types that I update regulary (css updates that my users did not see in two weeks was..ugh).
Next, I turn off setting the Expires-headers for php-files as this is done by Drupal.

Atle

Since I have been struggling with this for a while, I think it's time I do something about it. I've seen that other people have tred to address the issue, but no clean solution has yet been found.

Bbackground: a client needs to set up e-mail addresses for her website users. On my server I have an installation of Postfix Admin (http://sourceforge.net/projects/postfixadmin/) that she can surely use, but this poses two problems:

1. she will have 200+ users, and Postfix Admin allows creation of one account at a time. A real pain;
2. the created accounts will still be disconnected from the users' Drupal accounts, which might confuse most users.

I have thought of a couple of solutions where custom-made PHP pages would tap into the Postfix database, but they would end up being very unclean, not scalable, ultimately undrupallike (assuming that's a word).

The best solution would be to take Postfix Admin and make it into a real Drupal module. I am aware of most (if not all) difficulties, among which:

• Postfix Admin manages multiple domains;
• the Postfix database is, obviously, different from the Drupal database;
• Postfix tends to store cleartext passwords (someone correct me if I'm wrong – although I've found a small workaround for this).