Thanx for the suggestion, I went through the directory which provides very 
very minimal information its like hardly 20 lines written there that does 
not suffice for my query.

kindly suggest some more ways to get that understanding. What I actually 
wana know is the all protocol information is displayed uding a tree so 
somewhere that tree is made by taking some kinda buffer. where are these 
maintained,i will go through the code more once i get the initial point.




"Gilbert Ramirez" <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
06/03/2008 11:33 AM
Please respond to
Developer support list for Wireshark <[email protected]>


To
"Developer support list for Wireshark" <[email protected]>
cc

Subject
Re: [Wireshark-dev] regarding packet capture






The "doc" directory in the wireshark distribution has lots of good
info. Look at README.design, for example.

--gilbert

On 6/3/08, Amit Paliwal <[EMAIL PROTECTED]> wrote:
>
>
>  Hi,
>
> I frequently use Wireshark for my work, I just want to know how does
> wireshark constructs a tree kind of data structure from the raw buffer 
which
> it gets from network card. Could you plz let me know where in code i can 
see
> more so that i can get a clear understanding of code architecture for 
packet
> flow in wireshark including its ability to use and display it in tree
> format.
>
> Looking forward for your response.
>
> Best Regards,
> ______________________________________________________________________
>
> _______________________________________________
>  Wireshark-dev mailing list
>  [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>
_______________________________________________
Wireshark-dev mailing list
[email protected]
http://www.wireshark.org/mailman/listinfo/wireshark-dev

______________________________________________________________________



______________________________________________________________________
_______________________________________________
Wireshark-dev mailing list
[email protected]
http://www.wireshark.org/mailman/listinfo/wireshark-dev

Reply via email to