Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>> | Lars Gullik Bjønnes wrote:
>>>> | No it's not. If the data is passed as a string then we allow the
>>>> | outside world to receive the data, modify it and post it back
>>>> | with no addditional effort to us.
>>>>
>>>> this is the exception (external data), for all internal stuff
>>>> serialization _and_ the mailer stuff are really overkill.
>>>
>> | Shrug. There was a simple scheme that worked in 1.3.x where the
>> | frontends stored the inset. Which you didn't like. Now you have a
>> | safe scheme that you think is too complex. Yet I would argue it is
>> | clean and simple and extensible.
>>>
>> | Come up with a working alternative and we'll discuss that ;-)
>>
>> Simple: forget about the externals for a second.
>
| No.
>
>> Pass the whole InsetParamsXXX in a boost::any to where it is used.
>> The sender and the receiver knows the type so now prob. Now all the
>> mailer code can go.
>
| You replace 20 lines of code per inset with 20 lines of code per
| inset.
I do not think so... last time I tried this it was more like replacing
20 lines with 2.
| (Happy New Year by the way ;-)
and to you as well :-)
--
Lgb
