Re: [twsocket] Setting additional Header fields depending on the mimetype in th

2011-12-13 Thread Angus Robertson - Magenta Systems Ltd
Persistant headers are not usefull cause only certain Mimetype need special headers And I believe this is not just a special scenario for our apps. According to Pagespeed and feedback from our users this relative simple change (Date and Expire headers) improved the response times I'm

Re: [twsocket] Trouble with ICS v7

2011-12-13 Thread Arno Garrels
Denis Gottardello wrote: I use ICS components in a my application. I have a problem with TWSocket and ServerWSocketDataAvailable. Sometimes, when the ServerWSocketDataAvailable event is called and in action, the same event is called again, before the previous instance is terminated. I use

[twsocket] TWSocket in a tread contest without events

2011-12-13 Thread Denis Gottardello
Is possible to use TWSocket object without events contest? I want to use a familiar way for me. I like to create a thread for each connection. -- Denis Gottardello Sintesi S.r.l. 049.9301135 -- To unsubscribe or change your settings for TWSocket mailing list please goto

Re: [twsocket] Trouble with ICS v7

2011-12-13 Thread Denis Gottardello
Il 13/12/2011 15.52, Arno Garrels ha scritto: Denis Gottardello wrote: I use ICS components in a my application. I have a problem with TWSocket and ServerWSocketDataAvailable. Sometimes, when the ServerWSocketDataAvailable event is called and in action, the same event is called again, before

Re: [twsocket] Setting additional Header fields depending on the mimetype in th

2011-12-13 Thread RTT
On 13-12-2011 08:31, Angus Robertson - Magenta Systems Ltd wrote: I'm just about to change to HttpServer MIME handling again, to use a look-up list read from the Windows classes registry or a text file) when the server starts, to replace the current hard coded MIME list. If filling from the

Re: [twsocket] Setting additional Header fields depending on themimetype in th

2011-12-13 Thread RTT
On 13-12-2011 14:43, Arno Garrels wrote: I would not link headers with MIME types (in the same list) but rather keep it clear and simple. This new class should also be usable from other components such as the SMTP client. Totally agree with that. Associating header elements to the content-type

Re: [twsocket] TWSocket in a tread contest without events

2011-12-13 Thread François Piette
Is possible to use TWSocket object without events contest? I want to use a familiar way for me. I like to create a thread for each connection. Not sure I understand your question! Facts: a) you cannot use TWSocket without using events. b) you can use TWSocket in a thread. There are samples

Re: [twsocket] Trouble with ICS v7

2011-12-13 Thread François Piette
I use ICS components in a my application. I have a problem with TWSocket and ServerWSocketDataAvailable. Sometimes, when the ServerWSocketDataAvailable event is called and in action, the same event is called again, before the previous instance is terminated. I use line mode, #13#10 as

Re: [twsocket] TWSocket in a tread contest without events

2011-12-13 Thread Arno Garrels
Denis Gottardello wrote: Is possible to use TWSocket object without events contest? I want to use a familiar way for me. I like to create a thread for each connection. Some higher level protocols provide synchronous methods, however the base TWSocket has to be used async. -- Arno Garrels

Re: [twsocket] Trouble with ICS v7

2011-12-13 Thread Arno Garrels
Denis Gottardello wrote: Il 13/12/2011 15.52, Arno Garrels ha scritto: Denis Gottardello wrote: I use ICS components in a my application. I have a problem with TWSocket and ServerWSocketDataAvailable. Sometimes, when the ServerWSocketDataAvailable event is called and in action, the same

Re: [twsocket] Setting additional Header fields depending on the mimetype in th

2011-12-13 Thread Angus Robertson - Magenta Systems Ltd
If filling from the registry, better if the list is filled dynamically when a not yet resolved file extension is requested. Except that scanning a single registry node or file, allocating memory for those nodes, and building indexes for them may be more efficient in one function. We don't

Re: [twsocket] Setting additional Header fields depending on themimetype in th

2011-12-13 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: If filling from the registry, better if the list is filled dynamically when a not yet resolved file extension is requested. Except that scanning a single registry node or file, allocating memory for those nodes, and building indexes for them may

Re: [twsocket] Setting additional Header fields depending on themimetype in th

2011-12-13 Thread Angus Robertson - Magenta Systems Ltd
We don't want to open and load a text file each time a new type is found. True, that would be dog-slow. We need to think about Linux/OSX, this will be first use of registry access in ICS, I've already done some stuff to help decoding MIME email content. I agree that memory is needed for

Re: [twsocket] Setting additional Header fields depending on the mimetype in th

2011-12-13 Thread François Piette
I'm just about to change to HttpServer MIME handling again, to use a look-up list read from the Windows classes registry or a text file) when the server starts, to replace the current hard coded MIME list. It will be editable by the application. The implementation should be delegated to a

Re: [twsocket] Setting additional Header fields depending onthemimetype in th

2011-12-13 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote: We don't want to open and load a text file each time a new type is found. True, that would be dog-slow. We need to think about Linux/OSX, this will be first use of registry access in ICS, I've already done some stuff to help decoding MIME email

Re: [twsocket] Setting additional Header fields depending on themimetype in th

2011-12-13 Thread RTT
On 13-12-2011 19:21, Arno Garrels wrote: We don't want to open and load a text file each time a new type is found. True, that would be dog-slow. For the generality of the HTTP server applications, other than the 10 or 15 most common MIME types (that should always be in the list) and the