解惑

解己之惑,解人之惑

2005年7月 (第1页共2页)

RPM常用命令

  1. 安装:rpm -ivh xxx.nn.m.i386.rpm
  2. 卸载:rpm -e xxx
  3. 升级:rpm -Uvh xxx.nn.m.i386.rpm
  4. 查询:rpm -q xxx
  5. 信息:rpm -qi xxx
  6. 文件:rpm -ql xxx
  7. 编译:rpm -ivh –rebuild xxx.src.rpm
  8. 签名:rpm –checksig xxx

ip-sysctl.txt

/proc/sys/net/ipv4/* Variables:

ip_forward - BOOLEAN
0 - disabled (default)
not 0 - enabled

Forward Packets between interfaces.

This variable is special, its change resets all configuration
parameters to their default state (RFC1122 for hosts, RFC1812
for routers)

ip_default_ttl - INTEGER
default 64

ip_no_pmtu_disc - BOOLEAN
Disable Path MTU Discovery.
default FALSE

IP Fragmentation:

ipfrag_high_thresh - INTEGER
Maximum memory used to reassemble IP fragments. When
ipfrag_high_thresh bytes of memory is allocated for this purpose,
the fragment handler will toss packets until ipfrag_low_thresh
is reached.

ipfrag_low_thresh - INTEGER
See ipfrag_high_thresh

ipfrag_time - INTEGER
Time in seconds to keep an IP fragment in memory.

ipfrag_secret_interval - INTEGER
Regeneration interval (in seconds) of the hash secret (or lifetime
for the hash secret) for IP fragments.
Default: 600

INET peer storage:

inet_peer_threshold - INTEGER
The approximate size of the storage. Starting from this threshold
entries will be thrown aggressively. This threshold also determines
entries' time-to-live and time intervals between garbage collection
passes. More entries, less time-to-live, less GC interval.

inet_peer_minttl - INTEGER
Minimum time-to-live of entries. Should be enough to cover fragment
time-to-live on the reassembling side. This minimum time-to-live is
guaranteed if the pool size is less than inet_peer_threshold.
Measured in jiffies(1).

inet_peer_maxttl - INTEGER
Maximum time-to-live of entries. Unused entries will expire after
this period of time if there is no memory pressure on the pool (i.e.
when the number of entries in the pool is very small).
Measured in jiffies(1).

inet_peer_gc_mintime - INTEGER
Minimum interval between garbage collection passes. This interval is
in effect under high memory pressure on the pool.
Measured in jiffies(1).

inet_peer_gc_maxtime - INTEGER
Minimum interval between garbage collection passes. This interval is
in effect under low (or absent) memory pressure on the pool.
Measured in jiffies(1).

TCP variables:

tcp_syn_retries - INTEGER
Number of times initial SYNs for an active TCP connection attempt
will be retransmitted. Should not be higher than 255. Default value
is 5, which corresponds to ~180seconds.

tcp_synack_retries - INTEGER
Number of times SYNACKs for a passive TCP connection attempt will
be retransmitted. Should not be higher than 255. Default value
is 5, which corresponds to ~180seconds.

tcp_keepalive_time - INTEGER
How often TCP sends out keepalive messages when keepalive is enabled.
Default: 2hours.

tcp_keepalive_probes - INTEGER
How many keepalive probes TCP sends out, until it decides that the
connection is broken. Default value: 9.

tcp_keepalive_intvl - INTEGER
How frequently the probes are send out. Multiplied by
tcp_keepalive_probes it is time to kill not responding connection,
after probes started. Default value: 75sec i.e. connection
will be aborted after ~11 minutes of retries.

tcp_retries1 - INTEGER
How many times to retry before deciding that something is wrong
and it is necessary to report this suspicion to network layer.
Minimal RFC value is 3, it is default, which corresponds
to ~3sec-8min depending on RTO.

tcp_retries2 - INTEGER
How may times to retry before killing alive TCP connection.
RFC1122 says that the limit should be longer than 100 sec.
It is too small number. Default value 15 corresponds to ~13-30min
depending on RTO.

tcp_orphan_retries - INTEGER
How may times to retry before killing TCP connection, closed
by our side. Default value 7 corresponds to ~50sec-16min
depending on RTO. If you machine is loaded WEB server,
you should think about lowering this value, such sockets
may consume significant resources. Cf. tcp_max_orphans.

tcp_fin_timeout - INTEGER
Time to hold socket in state FIN-WAIT-2, if it was closed
by our side. Peer can be broken and never close its side,
or even died unexpectedly. Default value is 60sec.
Usual value used in 2.2 was 180 seconds, you may restore
it, but remember that if your machine is even underloaded WEB server,
you risk to overflow memory with kilotons of dead sockets,
FIN-WAIT-2 sockets are less dangerous than FIN-WAIT-1,
because they eat maximum 1.5K of memory, but they tend
to live longer. Cf. tcp_max_orphans.

tcp_max_tw_buckets - INTEGER
Maximal number of timewait sockets held by system simultaneously.
If this number is exceeded time-wait socket is immediately destroyed
and warning is printed. This limit exists only to prevent
simple DoS attacks, you _must_ not lower the limit artificially,
but rather increase it (probably, after increasing installed memory),
if network conditions require more than default value.

tcp_tw_recycle - BOOLEAN
Enable fast recycling TIME-WAIT sockets. Default value is 0.
It should not be changed without advice/request of technical
experts.

tcp_tw_reuse - BOOLEAN
Allow to reuse TIME-WAIT sockets for new connections when it is
safe from protocol viewpoint. Default value is 0.
It should not be changed without advice/request of technical
experts.

tcp_max_orphans - INTEGER
Maximal number of TCP sockets not attached to any user file handle,
held by system. If this number is exceeded orphaned connections are
reset immediately and warning is printed. This limit exists
only to prevent simple DoS attacks, you _must_ not rely on this
or lower the limit artificially, but rather increase it
(probably, after increasing installed memory),
if network conditions require more than default value,
and tune network services to linger and kill such states
more aggressively. Let me to remind again: each orphan eats
up to ~64K of unswappable memory.

tcp_abort_on_overflow - BOOLEAN
If listening service is too slow to accept new connections,
reset them. Default state is FALSE. It means that if overflow
occurred due to a burst, connection will recover. Enable this
option _only_ if you are really sure that listening daemon
cannot be tuned to accept connections faster. Enabling this
option can harm clients of your server.

tcp_syncookies - BOOLEAN
Only valid when the kernel was compiled with CONFIG_SYNCOOKIES
Send out syncookies when the syn backlog queue of a socket
overflows. This is to prevent against the common 'syn flood attack'
Default: FALSE

Note, that syncookies is fallback facility.
It MUST NOT be used to help highly loaded servers to stand
against legal connection rate. If you see synflood warnings
in your logs, but investigation shows that they occur
because of overload with legal connections, you should tune
another parameters until this warning disappear.
See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.

syncookies seriously violate TCP protocol, do not allow
to use TCP extensions, can result in serious degradation
of some services (f.e. SMTP relaying), visible not by you,
but your clients and relays, contacting you. While you see
synflood warnings in logs not being really flooded, your server
is seriously misconfigured.

tcp_stdurg - BOOLEAN
Use the Host requirements interpretation of the TCP urg pointer field.
Most hosts use the older BSD interpretation, so if you turn this on
Linux might not communicate correctly with them.
Default: FALSE

tcp_max_syn_backlog - INTEGER
Maximal number of remembered connection requests, which are
still did not receive an acknowledgment from connecting client.
Default value is 1024 for systems with more than 128Mb of memory,
and 128 for low memory machines. If server suffers of overload,
try to increase this number.

tcp_window_scaling - BOOLEAN
Enable window scaling as defined in RFC1323.

tcp_timestamps - BOOLEAN
Enable timestamps as defined in RFC1323.

tcp_sack - BOOLEAN
Enable select acknowledgments (SACKS).

tcp_fack - BOOLEAN
Enable FACK congestion avoidance and fast retransmission.
The value is not used, if tcp_sack is not enabled.

tcp_dsack - BOOLEAN
Allows TCP to send "duplicate" SACKs.

tcp_ecn - BOOLEAN
Enable Explicit Congestion Notification in TCP.

tcp_reordering - INTEGER
Maximal reordering of packets in a TCP stream.
Default: 3

tcp_retrans_collapse - BOOLEAN
Bug-to-bug compatibility with some broken printers.
On retransmit try to send bigger packets to work around bugs in
certain TCP stacks.

tcp_wmem - vector of 3 INTEGERs: min, default, max
min: Amount of memory reserved for send buffers for TCP socket.
Each TCP socket has rights to use it due to fact of its birth.
Default: 4K

default: Amount of memory allowed for send buffers for TCP socket
by default. This value overrides net.core.wmem_default used
by other protocols, it is usually lower than net.core.wmem_default.
Default: 16K

max: Maximal amount of memory allowed for automatically selected
send buffers for TCP socket. This value does not override
net.core.wmem_max, "static" selection via SO_SNDBUF does not use this.
Default: 128K

tcp_rmem - vector of 3 INTEGERs: min, default, max
min: Minimal size of receive buffer used by TCP sockets.
It is guaranteed to each TCP socket, even under moderate memory
pressure.
Default: 8K

default: default size of receive buffer used by TCP sockets.
This value overrides net.core.rmem_default used by other protocols.
Default: 87380 bytes. This value results in window of 65535 with
default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
less for default tcp_app_win. See below about these variables.

max: maximal size of receive buffer allowed for automatically
selected receiver buffers for TCP socket. This value does not override
net.core.rmem_max, "static" selection via SO_RCVBUF does not use this.
Default: 87380*2 bytes.

tcp_mem - vector of 3 INTEGERs: min, pressure, max
low: below this number of pages TCP is not bothered about its
memory appetite.

pressure: when amount of memory allocated by TCP exceeds this number
of pages, TCP moderates its memory consumption and enters memory
pressure mode, which is exited when memory consumption falls
under "low".

high: number of pages allowed for queueing by all TCP sockets.

Defaults are calculated at boot time from amount of available
memory.

tcp_app_win - INTEGER
Reserve max(window/2^tcp_app_win, mss) of window for application
buffer. Value 0 is special, it means that nothing is reserved.
Default: 31

tcp_adv_win_scale - INTEGER
Count buffering overhead as bytes/2^tcp_adv_win_scale
(if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
if it is <= 0.
Default: 2

tcp_rfc1337 - BOOLEAN
If set, the TCP stack behaves conforming to RFC1337. If unset,
we are not conforming to RFC, but prevent TCP TIME_WAIT
assassination.
Default: 0

tcp_low_latency - BOOLEAN
If set, the TCP stack makes decisions that prefer lower
latency as opposed to higher throughput. By default, this
option is not set meaning that higher throughput is preferred.
An example of an application where this default should be
changed would be a Beowulf compute cluster.
Default: 0

ip_local_port_range - 2 INTEGERS
Defines the local port range that is used by TCP and UDP to
choose the local port. The first number is the first, the
second the last local port number. Default value depends on
amount of memory available on the system:
> 128Mb 32768-61000
< 128Mb 1024-4999 or even less.
This number defines number of active connections, which this
system can issue simultaneously to systems not supporting
TCP extensions (timestamps). With tcp_tw_recycle enabled
(i.e. by default) range 1024-4999 is enough to issue up to
2000 connections per second to systems supporting timestamps.

ip_nonlocal_bind - BOOLEAN
If set, allows processes to bind() to non-local IP addresses,
which can be quite useful - but may break some applications.
Default: 0

ip_dynaddr - BOOLEAN
If set non-zero, enables support for dynamic addresses.
If set to a non-zero value larger than 1, a kernel log
message will be printed when dynamic address rewriting
occurs.
Default: 0

icmp_echo_ignore_all - BOOLEAN
icmp_echo_ignore_broadcasts - BOOLEAN
If either is set to true, then the kernel will ignore either all
ICMP ECHO requests sent to it or just those to broadcast/multicast
addresses, respectively.

icmp_ratelimit - INTEGER
Limit the maximal rates for sending ICMP packets whose type matches
icmp_ratemask (see below) to specific targets.
0 to disable any limiting, otherwise the maximal rate in jiffies(1)
Default: 100

icmp_ratemask - INTEGER
Mask made of ICMP types for which rates are being limited.
Significant bits: IHGFEDCBA9876543210
Default mask: 0000001100000011000 (6168)

Bit definitions (see include/linux/icmp.h):
0 Echo Reply
3 Destination Unreachable *
4 Source Quench *
5 Redirect
8 Echo Request
B Time Exceeded *
C Parameter Problem *
D Timestamp Request
E Timestamp Reply
F Info Request
G Info Reply
H Address Mask Request
I Address Mask Reply

* These are rate limited by default (see default mask above)

icmp_ignore_bogus_error_responses - BOOLEAN
Some routers violate RFC1122 by sending bogus responses to broadcast
frames. Such violations are normally logged via a kernel warning.
If this is set to TRUE, the kernel will not give such warnings, which
will avoid log file clutter.
Default: FALSE

igmp_max_memberships - INTEGER
Change the maximum number of multicast groups we can subscribe to.
Default: 20

conf/interface/* changes special settings per interface (where "interface" is
the name of your network interface)
conf/all/* is special, changes the settings for all interfaces


log_martians - BOOLEAN
Log packets with impossible addresses to kernel log.
log_martians for the interface will be enabled if at least one of
conf/{all,interface}/log_martians is set to TRUE,
it will be disabled otherwise

accept_redirects - BOOLEAN
Accept ICMP redirect messages.
accept_redirects for the interface will be enabled if:
- both conf/{all,interface}/accept_redirects are TRUE in the case forwarding
for the interface is enabled
or
- at least one of conf/{all,interface}/accept_redirects is TRUE in the case
forwarding for the interface is disabled
accept_redirects for the interface will be disabled otherwise
default TRUE (host)
FALSE (router)

forwarding - BOOLEAN
Enable IP forwarding on this interface.

mc_forwarding - BOOLEAN
Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE
and a multicast routing daemon is required.
conf/all/mc_forwarding must also be set to TRUE to enable multicast routing
for the interface

medium_id - INTEGER
Integer value used to differentiate the devices by the medium they
are attached to. Two devices can have different id values when
the broadcast packets are received only on one of them.
The default value 0 means that the device is the only interface
to its medium, value of -1 means that medium is not known.

Currently, it is used to change the proxy_arp behavior:
the proxy_arp feature is enabled for packets forwarded between
two devices attached to different media.

proxy_arp - BOOLEAN
Do proxy arp.
proxy_arp for the interface will be enabled if at least one of
conf/{all,interface}/proxy_arp is set to TRUE,
it will be disabled otherwise

shared_media - BOOLEAN
Send(router) or accept(host) RFC1620 shared media redirects.
Overrides ip_secure_redirects.
shared_media for the interface will be enabled if at least one of
conf/{all,interface}/shared_media is set to TRUE,
it will be disabled otherwise
default TRUE

secure_redirects - BOOLEAN
Accept ICMP redirect messages only for gateways,
listed in default gateway list.
secure_redirects for the interface will be enabled if at least one of
conf/{all,interface}/secure_redirects is set to TRUE,
it will be disabled otherwise
default TRUE

send_redirects - BOOLEAN
Send redirects, if router.
send_redirects for the interface will be enabled if at least one of
conf/{all,interface}/send_redirects is set to TRUE,
it will be disabled otherwise
Default: TRUE

bootp_relay - BOOLEAN
Accept packets with source address 0.b.c.d destined
not to this host as local ones. It is supposed, that
BOOTP relay daemon will catch and forward such packets.
conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay
for the interface
default FALSE
Not Implemented Yet.

accept_source_route - BOOLEAN
Accept packets with SRR option.
conf/all/accept_source_route must also be set to TRUE to accept packets
with SRR option on the interface
default TRUE (router)
FALSE (host)

rp_filter - BOOLEAN
1 - do source validation by reversed path, as specified in RFC1812
Recommended option for single homed hosts and stub network
routers. Could cause troubles for complicated (not loop free)
networks running a slow unreliable protocol (sort of RIP),
or using static routes.

0 - No source validation.

conf/all/rp_filter must also be set to TRUE to do source validation
on the interface

Default value is 0. Note that some distributions enable it
in startup scripts.

arp_filter - BOOLEAN
1 - Allows you to have multiple network interfaces on the same
subnet, and have the ARPs for each interface be answered
based on whether or not the kernel would route a packet from
the ARP'd IP out that interface (therefore you must use source
based routing for this to work). In other words it allows control
of which cards (usually 1) will respond to an arp request.

0 - (default) The kernel can respond to arp requests with addresses
from other interfaces. This may seem wrong but it usually makes
sense, because it increases the chance of successful communication.
IP addresses are owned by the complete host on Linux, not by
particular interfaces. Only for more complex setups like load-
balancing, does this behaviour cause problems.

arp_filter for the interface will be enabled if at least one of
conf/{all,interface}/arp_filter is set to TRUE,
it will be disabled otherwise

tag - INTEGER
Allows you to write a number, which can be used as required.
Default value is 0.

(1) Jiffie: internal timeunit for the kernel. On the i386 1/100s, on the
Alpha 1/1024s. See the HZ define in /usr/include/asm/param.h for the exact
value on your system.

Alexey Kuznetsov.
kuznet-AT-ms2.inr.ac-DOT-ru

Updated by:
Andi Kleen
ak-AT-muc-DOT-de
Nicolas Delon
delon.nicolas-AT-wanadoo-DOT-fr




/proc/sys/net/ipv6/* Variables:

IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also
apply to IPv6 [XXX?].

bindv6only - BOOLEAN
Default value for IPV6_V6ONLY socket option,
which restricts use of the IPv6 socket to IPv6 communication
only.
TRUE: disable IPv4-mapped address feature
FALSE: enable IPv4-mapped address feature

Default: FALSE (as specified in RFC2553bis)

IPv6 Fragmentation:

ip6frag_high_thresh - INTEGER
Maximum memory used to reassemble IPv6 fragments. When
ip6frag_high_thresh bytes of memory is allocated for this purpose,
the fragment handler will toss packets until ip6frag_low_thresh
is reached.

ip6frag_low_thresh - INTEGER
See ip6frag_high_thresh

ip6frag_time - INTEGER
Time in seconds to keep an IPv6 fragment in memory.

ip6frag_secret_interval - INTEGER
Regeneration interval (in seconds) of the hash secret (or lifetime
for the hash secret) for IPv6 fragments.
Default: 600

conf/default/*:
Change the interface-specific default settings.


conf/all/*:
Change all the interface-specific settings.

[XXX: Other special features than forwarding?]

conf/all/forwarding - BOOLEAN
Enable global IPv6 forwarding between all interfaces.

IPv4 and IPv6 work differently here; e.g. netfilter must be used
to control which interfaces may forward packets and which not.

This also sets all interfaces' Host/Router setting
'forwarding' to the specified value. See below for details.

This referred to as global forwarding.

conf/interface/*:
Change special settings per interface.

The functional behaviour for certain settings is different
depending on whether local forwarding is enabled or not.

accept_ra - BOOLEAN
Accept Router Advertisements; autoconfigure using them.

Functional default: enabled if local forwarding is disabled.
disabled if local forwarding is enabled.

accept_redirects - BOOLEAN
Accept Redirects.

Functional default: enabled if local forwarding is disabled.
disabled if local forwarding is enabled.

autoconf - BOOLEAN
Configure link-local addresses using L2 hardware addresses.

Default: TRUE

dad_transmits - INTEGER
The amount of Duplicate Address Detection probes to send.
Default: 1

forwarding - BOOLEAN
Configure interface-specific Host/Router behaviour.

Note: It is recommended to have the same setting on all
interfaces; mixed router/host scenarios are rather uncommon.

FALSE:

By default, Host behaviour is assumed. This means:

1. IsRouter flag is not set in Neighbour Advertisements.
2. Router Solicitations are being sent when necessary.
3. If accept_ra is TRUE (default), accept Router
Advertisements (and do autoconfiguration).
4. If accept_redirects is TRUE (default), accept Redirects.

TRUE:

If local forwarding is enabled, Router behaviour is assumed.
This means exactly the reverse from the above:

1. IsRouter flag is set in Neighbour Advertisements.
2. Router Solicitations are not sent.
3. Router Advertisements are ignored.
4. Redirects are ignored.

Default: FALSE if global forwarding is disabled (default),
otherwise TRUE.

hop_limit - INTEGER
Default Hop Limit to set.
Default: 64

mtu - INTEGER
Default Maximum Transfer Unit
Default: 1280 (IPv6 required minimum)

router_solicitation_delay - INTEGER
Number of seconds to wait after interface is brought up
before sending Router Solicitations.
Default: 1

router_solicitation_interval - INTEGER
Number of seconds to wait between Router Solicitations.
Default: 4

router_solicitations - INTEGER
Number of Router Solicitations to send until assuming no
routers are present.
Default: 3

use_tempaddr - INTEGER
Preference for Privacy Extensions (RFC3041).
<= 0 : disable Privacy Extensions
== 1 : enable Privacy Extensions, but prefer public
addresses over temporary addresses.
> 1 : enable Privacy Extensions and prefer temporary
addresses over public addresses.
Default: 0 (for most devices)
-1 (for point-to-point devices and loopback devices)

temp_valid_lft - INTEGER
valid lifetime (in seconds) for temporary addresses.
Default: 604800 (7 days)

temp_prefered_lft - INTEGER
Preferred lifetime (in seconds) for temorary addresses.
Default: 86400 (1 day)

max_desync_factor - INTEGER
Maximum value for DESYNC_FACTOR, which is a random value
that ensures that clients don't synchronize with each
other and generage new addresses at exactly the same time.
value is in seconds.
Default: 600

regen_max_retry - INTEGER
Number of attempts before give up attempting to generate
valid temporary addresses.
Default: 5

icmp/*:
ratelimit - INTEGER
Limit the maximal rates for sending ICMPv6 packets.
0 to disable any limiting, otherwise the maximal rate in jiffies(1)
Default: 100


IPv6 Update by:
Pekka Savola <pekkas-AT-netcore-DOT-fi>
YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org>

$Id: ip-sysctl.txt,v 1.20 2001/12/13 09:00:18 davem Exp $

如何使linux系统对ping不反应

  在linux里,如果要想使ping 没反应也就是用来忽略icmp包。可以用:
  echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_all
  若想恢复就用:
  echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_all

Linux下SYN的设置

参考文章为:SYN攻击的基本原理、工具及检测方法以及防范技术

LINUX相关的内容摘录如下:

  1. 激活SYN cookies:echo 1 > /proc/sys/net/ipv4/tcp_syncookies
  2. 增加最大半连接数:sysctl -w net.ipv4.tcp_max_syn_backlog=”2048″
  3. 缩短超时时间:sysctl -w net.ipv4.tcp_synack_retries=”1″

其实第一个也应该可以使用sysctl设置的,因为sysctl也是设置/proc/sys/net/ipv4目录下的对应文件的值。

另外这个设置都是一次性的,系统启动后就丢失了,要一直有效需要写入启动脚本,例如/etc/rc.d/rc.local

有点奇怪LINUX系统下为什么要用这种方式设置这些值,每个变量用一个文件设置。

分页策略的选择

在设计开发一个系统时分页是基本的功能之一,但是如何选择分页策略却是一个比较困难的问题,如果选择不对可能适得其反。
选择分页策略需要考虑的几个因素:

  1. 系统的数据的成长性,特别是时间敏感的成长性。
  2. 数据的更新频率,数据内容是否经常更新。
  3. 数据的大小,特别是常用数据的大小。
  4. 系统的用户的要求,例如用户对系统的反应速度要求比较高。
  5. 系统的硬件设施,例如最关键的数据库服务器的负载能力,应用服务器的负载能力,内存大小。

常见的两种分页,一个是基于缓存的,一个是基于实时查询的,而且这两者没有一个是具有绝对优势的,根据系统的特点采用不同的策略才能达到比较好的效果。根据系统的特点,还可以采用混合模式,也就是查询的时候每次查询的是比每页数据多的数据,例如每次查十页的数据。

对于具有高成长性的系统而言,特别是短时间具有高成长性,而且用户要求实时的结果,那么就不能采用缓存式的方案。
对于数据的更新频率比较大的系统而言,同样不适合采用缓存的方案。
系统的数据量比较大,而系统的内存不是非常的充裕,那么使用缓存方案也是不太现实的。

其实最重要的一个因素就是用户的要求,有的用户更关心系统的反应速度,数据旧一点点没有太大的关系,而有的用户要求实时性高,要求看到的永远是最新的数据。
至于系统的硬件限制就很简单了,但是现在这个一般不是关键的因素。

最终,策略的选择就是这些因素的综合考虑,而且可能也不限定选择一种策略,两种策略都可以提供,用户可以自己在这两种策略间方便的切换,但是在应用缓存方案的时候可以设置一个系统内定的最大记录数防止少数极端情况下导致系统崩溃。

需要根据Spring的要求重新省视自己的设计

利用周末的时间把中文版的spring参考手册中的现在需要关注的内容通读了一遍,原来我对自己的系统中考虑到的几个方面的内容spring已经提供了,
因此有必要完整的学习spring提供的内容,可能这次我有有点浮躁了,看来我要花一段时间把spring in
action也看一遍,可惜没有中文版的。现在也越来越懒了,不喜欢看英文原版了,可能是spring参考手册和hibernate参考手册翻译得不错的
缘故吧。

Spring中的多配置文件原来如此简单

一直都在找spring如何指定多个配置文件,因为一个系统一旦比较大以后所有的配置都放在一个文件中是非常不好的,不光是维护的问题,多人开发出现冲突
的可能性也就很大了,一直在搜索,但是没有什么结果,结果今天看了spring的参考手册(中文的那个1.1PR版)才发现非常的简单,在web.xml
中配置的时候直接指定多个文件就可以了,用空格、逗号或者分号分隔都可以,例如:
   <listener>
     
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
   </listener>
   <context-param>
      <param-name>contextConfigLocation</param-name>
     
<param-value>/WEB-INF/configs/spring-config.xml
/WEB-INF/configs/db-config.xml</param-value>
   </context-param>

Google推出了Firefox工具栏

Google推出了Firefox工具栏,马上安装了一个,感觉不错,而且一般情况下可以不打开金山词霸了,因为这个工具栏也带单词翻译功能,将鼠标移到英文单词上就会翻译为中文了。

错误的选择了Xstream

今天突然发现我在做页面生成特别是进行Bean到xml的映射的时候错误的选择了Xstream,而我恰恰应该使用的是spring本身提供的功能,因为其实spring的XmlBeanFactory也可以达到相同的目的,所不同的是用spring稍微要复杂一些,但是这个复杂性是可以接受的,而且spring的子Bean功能是Xstream所没有的,避免了我再进行编码的工作。我对spring还是太不了解了,也许应该把spring参考手册完整的看一遍了。

使用XStream自动生成页面

找到XStream后我的页面自动生成的功能就完成一半了,思路基本上确定下来了:
主要是两个文件对页面的生成进行配置,一个就是配置系统中的Element,通常的表单中的一个输入项,例如用户名提示加后面的输入框以及有效性校验,这个在elements.xsl文件中定义一下就行了,然后另外有一个Form,对应一个完整的表单,同时也有一个forms.xsl配置文件,每个form有一个名字,form通过Element的ID进行引用,而且可以额外对引用的Element的缺省配置进行修改,然后JSP就可以根据配置从标准的FORM库里面取出配置好的Form生成页面的Form部分了,当然也可以用比较原始的方式从Elements库里面取出最小的单元手工拼装,然后这个Form可以和一个Bean绑定,完成Element的赋值。
当然这个只是一个思路,真正要完成这个还有很多的代码要写呢,不过有了这个已经比较好做了,剩下的就是生成页面的体力活了。

更早的文章

© 2024 解惑

本主题由Anders Noren提供向上 ↑